As an update to my last comment on 2013-12-17, my Apache non-
responsiveness was actually due to mod_ssl, not this particular bug. I
haven't encountered this bug in some time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
All of a sudden, this bug has come back. The last couple weeks, Apache
goes completely unresponsive almost daily. It takes a restart to get it
going again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I haven't actually experienced this bug in a while. Graceful shutdowns
and logrotate have been working completely without issue. Unfortunately,
my syslogs only goes back to 8/30/13, but there're no segfaults at all.
I'm guessing a fix came out in some update.
--
You received this bug notification
Actually, I think I spoke too soon. It looks like reload AND graceful
cause apache2 to segfault. Only a full restart or stopping/starting
apache2 seem to get it going again.
Any time this happens, I see lines like the following in
/var/log/syslog:
kernel: apache2[11246]: segfault at ip b
I'm glad I stumbled onto this bug. My full information is available at
http://stackoverflow.com/questions/16304844/php-apc-causing-apache-to-
seg-fault.
- I am not using RequestTracker.
- This happens for me any time I issue "sudo service apache2 graceful".
Issuing reload doesn't seem to cause mi
