Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

I also got the problem with Apache 2.0.35 not starting up when having the PHP module activated.

I compiled PHP 4.2.0 with the following options:
--enable-safe-mode --enable-gd-native-ttf --enable-inline-optimization --with-apxs2=/usr/apache2/bin/apxs --with-bz2 --with-zlib --with-cyrus --with-dom --with-dom-xslt --with-gd=/usr/src/gd-2.0.1 --without-mysql --with-pgsql=/opt/pgsql --prefix=/usr --with-openssl --enable-calendar --enable-ftp --enable-gettext=shared --with-jpeg-dir=/usr --with-png-dir=/usr --with-freetype-dir=/usr

The strange thing is, that there isn't any error message. Neither on the console nor in the logfiles.

When I deactivate the PHP module the error_log says:
[Wed Apr 24 19:44:55 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/apache2/bin/suexec)
[Wed Apr 24 19:44:55 2002] [notice] Apache/2.0.35 (Unix) DAV/2 configured -- resuming normal operations

When I activate the PHP module the error_log says:
[Wed Apr 24 19:51:51 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/apache2/bin/suexec)

The Apache server just doesn't start.
Why? :-)

I've just compiled PHP with --enable-debug and PHP worked except the cookies (mentioned in another bugreport).

Apache 2.0.35 + PHP 4.2.0 on Debian linux produced the same effect. Apache+php module won't start without the 'restart' trick.

apache configuration: ./configure --enable-module=so
php configuration: ./configure --with-apxs2=/usr/local/apache2 --without-pear