Hello Luca,
i need to wait until a machine is crashing again. What looks strange
from a first view is that async connections closing has very high and
strange values:
4294967211
Even a not yet crashed system has those:
Slot PID Stopping Connections Threads Async connections
total accepting busy idle writing keep-alive closing
0 25157 no 12 yes 4 196 0 9
4294967231 <== HERE ==
1 25159 no 22 yes 8 192 0 13
4294967211 <== HERE ==
Sum 2 0 34 12 388 0 22 -150
Greets,
Stefan
Am 19.07.2017 um 17:48 schrieb Luca Toscano:
> Hello Stefan,
>
> 2017-07-19 17:05 GMT+02:00 Stefan Priebe - Profihost AG
> <[email protected] <mailto:[email protected]>>:
>
>
> Am 19.07.2017 um 16:59 schrieb Stefan Priebe - Profihost AG:
> > Hello Yann,
> >
> > i'm observing some deadlocks again.
> >
> > I'm using
> > httpd 2.4.27
> > + mod_h2
> > + httpd-2.4.x-mpm_event-wakeup-v7.1.patch
> > + your ssl linger fix patch from this thread
> >
> > What kind of information do you need? If you need a full stack backtrace
> > - from which pid? Or from all httpd pids?
>
> Something i forgot to tell:
>
> it seems httpd is running at max threads:
> awk '{print $10 $11}' lsof.txt | sort | uniq -c | grep LISTEN
> 25050 *:http(LISTEN)
> 25050 *:https(LISTEN)
>
>
> First of all let me tell you how awesome is your regular testing, thank
> you! It is helping a ton to deliver stable code :)
>
> From my point of view I think that you can attach gdb to one or more
> httpd processes and do the usual "thread apply all", IIUC your httpd
> ends up having all of its processes in more or less the same state right?
>
> Let's use https://apaste.info/ or similar though otherwise we'll need to
> exchange super long emails.
>
> Thanks again!
>
> Luca
