How to figure out why Apache stops responding
I'm proxying to apache with nginx, and checking the nginx access logs on each of those occasions, nginx just shows 499 errors for a while, then 504 errors for the rest of the time. That seems like what I would expect if Apache stops responding for some reason.
So where can I go from here to figure out what happened? I'm using django+postgres but I don't know how to investigate with no useful apache logs.
4 Replies
Looking at the logs, it didn't appear that there was a deadlock. Using worker mpm there were three wsgi daemon processes and each were serving requests normally up to the time when the server went dead. Would you expect to see something in error.log if apache ran out of children?
Are your Apache logs being rotated properly? An oversized log can cause strange issues. Do you have any RLimits configured?