Take a look at the command that actually invokes the server by doing this: bash -x /etc/rc.d/init.d/apache
If it includes a "-D PHP4" parameter, that could be the problem. If it does not, then invoke the server manually using the same parameters and see what, if any, errors come out. Startup scripts are nice when they work. When they don't, and they hide any error messages that come out, they're a pain. Mark Post -----Original Message----- From: Mullen, Patrick [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: Apache 1.3 on SuSE 7.0 I seem to be using PHP3 already, this snippet from error_log after doing the restart: Apache/1.3.12 (Unix) (SuSE/Linux) mod_perl/1.24 PHP/3.0.17-dev > -----Original Message----- > From: Post, Mark K [mailto:[EMAIL PROTECTED]] > > There was a problem with PHP4 causing Apache to fail during > startup. If you > remove PHP4 and only use PHP3 (or re-compile PHP4 from the > source RPM), you > should be ok. > > Mark Post > > -----Original Message----- > From: Mullen, Patrick [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 15, 2002 1:14 PM > To: [EMAIL PROTECTED] > Subject: Apache 1.3 on SuSE 7.0 > > > Can anyone help me with an Apache related issue? Everything > looks like it's > configured right, but after booting httpd does not start. A > "status" command > returns "No process" and the httpd error_log file is > completely empty. If I > do a "restart" command it seems to activate, but I still > can't connect - it > returns an "Internal Server Error 500" message, but still > nothing appears in > error_log. >
