Hi,

today, as usual on Saturdays, I ran "emerge -aNDuv @world" which succeeded
without any errors.  As I noticed, there was an Apache upgrade from 2.4.38-r1
to 2.4.39, and a glibc upgrade from 2.27-r6 to 2.28-r5 (among others).

After upgrading, Apache won't start any more. "/etc/init.d/apache2 start" waits
(as long as I put "--wait 60000", for example, into the init script), and then
says "Apache failed to start".  In /var/log/apache2/error_log, there is nothing.

Of course, I already asked Google and found some issues with /dev/random and
/proc/sys/kernel/random/entropy_avail - I installed "rngd" then, to avoid those
problems.  I even disabled the "auth_digest" module.  Doesn't help.

Starting Apache with "-e debug" shows loading a lot of Apache modules, and then
.... nothing happens any more.  "ps -ef" shows just a single Apache process 
(where
there should be some more as usual.  "netstat -lnp | grep -w 80" shows no 
listening
ports.

Downgrading to Apache 2.4.38 doesn't help either, and downgrading glibc seems
to be forbidden as "this will clearly break your system" (emerge says).

Now "admin-panic" is heavily arising.  HELP!  What can I do??

Thanks a lot,

-Matt

Reply via email to