[solved] Apache2 stopped after emerge (PHP related)

[WintermuteX]

My apache server stopped working after i ran "perl-cleaner reallyall" .. at least thats the only change i remember.
Ok, i also made an "emerge -avuDN world" after syncing with portage yesterday. Maybe it's also related to this.
Apache starts only one instance and all connections to port 80 are refused.

Any ideas? Thats somehow very urgent as it is an community page %)

[di1bert]

Did you run etc-update / dispatch-conf after upgrading world ? There were some major changes in Apache from 2.0.5x to 2.2.6 which is probably whats happened to you.

Start with that and if that doesn't help check your error_log files
and think about enabling the start up log in /etc/conf.d/apache2

HTH

-m

[WintermuteX]

Thanks for your input, i now enabled startup logging.

The migration to apache 2.2 is done a long time ago and worked very well, the server was even rebooted inbetween. As a standard measure i run "env-update && etc-update && source /etc/profile && revdep-rebuild -i" after emerges/updates.

The StartUp log only provides: "Syntax OK"

No error messages anywhere .. the only thing i see is that only one instance of apache is seen by top/htop/ps aux.

[WintermuteX]

Btw some more info:

www-servers/apache-2.2.6 USE="mpm-worker ssl threads"
dev-lang/perl-5.8.8-r2 USE="berkdb gdbm ithreads"
dev-lang/php-5.2.5 USE="apache2 bcmath berkdb bzip2 calendar cdb cgi cli crypt ctype curl curlwrappers exif filter flatfile ftp gd gdbm hash iconv imap inifile json kerberos mhash mysql mysqli ncurses nls pcntl pcre pdo posix readline reflection session sharedext simplexml soap sockets spell spl sqlite ssl sysvipc threads tidy tokenizer truetype unicode xml xmlreader xmlrpc xmlwriter xpm xsl yaz zip zlib"

Any information missing?

[di1bert]

Very strange. The next thing I'd do is try and start httpd in the foreground, although I'm not
entirely sure how to do it as I've never really had issues with an Apache installation.

Sorry I can't be of more use to you.

-m

[WintermuteX]

Thank you for trying

[WintermuteX]

Ok, the answer was simple .. and is related to two events:

1. After upgrading to apache 2.2 and merging the configs i forgot to set the error_log path correctly .. hence i had empty error_log's
2. I use PHP in conjunction with eaccelerator

After the ebuild update of PHP5 eaccelerator was broken and should have been reemerged ... i forgot about it and missed the log message as it was never written (see 1. above).