Hi Gabriele, There have been some fixes to the APR library since 1.5.2, notably on the Solaris apr_pollset_poll() implementation, though I can only think of a bug [1] pertaining to MPM event (not MPM worker which you seem to be using). It could be worth upgrading to a more recent APR-1.6.5 or APR-1.7.0 still. Regards; Yann. [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=61786 On Tue, Feb 9, 2021 at 11:07 AM Gabriele Bulfon <gbulfon@xxxxxxxxxxx.invalid> wrote: > > Hi, I finally could produce the httpd blocked problem and ran a script to dump stack of all running processes/threads. > They strangely look all quite the same! I attach here all the httpd threads dumps, maybe you can help us see why it was blocked? > > Thanks! > Gabriele > > > Sonicle S.r.l. : http://www.sonicle.com > Music: http://www.gabrielebulfon.com > eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets > > > > > ---------------------------------------------------------------------------------- > > Da: Rainer Canavan <rainer.canavan@xxxxxxxxxx> > A: users@xxxxxxxxxxxxxxxx > Data: 2 novembre 2020 17.19.27 CET > Oggetto: Re: Self built httpd 2.4.43 problems > > On Mon, Nov 2, 2020 at 4:17 PM Gabriele Bulfon > <gbulfon@xxxxxxxxxxx.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-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|