I was looking to start a Drupal project and spend almost 4 hours to get Apache and Drupal talk each other. What I found out was there are lots of mismatch in documentation and snapshots. As I am using Windows I found out following two installation bundles works without any issue. Hope this would help someone. Hi guys, In my case, it work right away when I change the version to thread-safe. I spent some time trying the different things that were posted here and I was kind of lazy about downloading a different version, but once I test it with a thead-safe it started right away.
So be sure you try this. I was on Apache 2. Like someone else mentioned, on the Windows download page for PHP, ignore the warning about not downloading the VC9 compiled installers for the Apache. Whoever wrote that is guaranteeing that people install a PHP that breaks their Apache server. On Windows 7 anyway. The installer failed to write the correct path info to httpd. Ignore that dumb warning and get the newest installer anyway. Everything just plain works with no hassle and no hunting down dll files over google.
Just a note It might be important you include the absolute path to the php. This happened to me because I copied the statements from a random website. In my text editor the difference was barely noticeable, but to Apache it certainly is!
I was able to get apache up and running without any problems. Also had an exception problem when trying to use mysql with apache and php5. I wanted to install PHP5. It took me hours to solve it.
The following possible problems occur: - You should use the VC6-compiled version of php instead of VC9. The later one does not work properly with apache. This error was misinterpreted internally in the above message. The solution was NOT to use the libpq. This prevents us from using the bad version of dll. I hope I helped. After using the Windows installer for Apache 2. There were two problems with the configuration files for Apache and PHP.
The value for FcgidWrapper cannot contain spaces.. This is with Apache 2. Apache failed to start if I did not include the slash after php. But adding shebang line has a disadvantage that if you decided to install PHP as an Apache module afterwards, then the shebang line WILL appear in the web page.
For those still having problems with "You don't have permission to run php-cgi. If you want to know what they're doing just look for yourself. BTW, it's recommended by Apache to use apachectl to control httpd. Several of the init scripts are written from templates and may not necessarily take the best practices from the developer into consideration.
Your apache server is running in worker mode. Lots of php modules fail to load in worker mode. Change it to prefork mode, then service httpd start will also work. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more.
Ask Question. Asked 7 years, 8 months ago. Active 3 years, 11 months ago. Viewed 5k times. What's the difference? Can I correct the service httpd start stop restart behavior? Improve this question. In addition, it is sometimes necessary to provide the configure script with extra information about the location of your compiler, libraries, or header files.
This is done by passing either environment variables or command line options to configure. For more information, see the configure manual page. Or invoke configure using the --help option. When configure is run it will take several minutes to test for the availability of features on your system and build Makefiles which will later be used to compile the server.
Details on all the different configure options are available on the configure manual page. Now you can build the various parts which form the Apache package by simply running the command:. Please be patient here, since a base configuration takes several minutes to compile and the time will vary widely depending on your hardware and the number of modules that you have enabled.
This step will typically require root privileges, since PREFIX is usually a directory with restricted write permissions. If you are upgrading, the installation will not overwrite your configuration files or documents. Then stop the server again by running:.
The first step in upgrading is to read the release announcement and the file CHANGES in the source distribution to find any changes that may affect your site. When changing between major releases for example, from 2. All modules will also need to be upgraded to accommodate changes in the module API. Upgrading from one minor version to the next for example, from 2. The make install process will not overwrite any of your existing documents, log files, or configuration files.
In addition, the developers make every effort to avoid incompatible changes in the configure options, run-time configuration, or the module API between minor versions. In most cases you should be able to use an identical configure command line, an identical configuration file, and all of your modules should continue to work.
To upgrade across minor versions, start by finding the file config. This will contain the exact configure command line that you used to configure the source tree. Then to upgrade from one version to the next, you need only copy the config. You can pass additional arguments to config. A large number of third parties provide their own packaged distributions of the Apache HTTP Server for installation on particular platforms.
Our software license not only permits, but encourages, this kind of redistribution. However, it does result in a situation where the configuration layout and defaults on your installation of the server may differ from what is stated in the documentation.
0コメント