On Mon, Nov 2, 2020 at 4:17 PM Gabriele Bulfon <gbul...@sonicle.com.invalid> wrote: > > Thanks, I configured and ran server-status after stopping/starting apache. > Top output is: > [...]
> What should I check? > Also, when system blocks I won't be able to see server-status, as it will be > not responding. > Should I check it daily and look for a specific info that grows? "requests currently being processed" would probably increase if threads are permanently blocked. I would recommend logging this every few seconds, so that you can at least check after the fact how quickly the system filled up. You should have ExtendedStatus enabled, which should give you a complete list of all threads and their states. Any that are active (probably "W", definitively not "." or "_") processing a single request for extended periods are suspicious, especially if multiple of the same kind strat piling up. If httpd does not respond to requests anymore, and you have multiple worker childs, you can sometimes get away with killing one and try to squeeze a status request in there before it gets overrun again. Anyway, serverstatus will only provide rough hints of what's going on. If it is indeed httpd, you'll probably need gdb backtraces. rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
