Hi Mark, On Wed, May 01, 2019 at 12:21:25PM +0200, Mark Janssen wrote: > Looks like it's running with a high cpu-level again.... it's currently not > impacting the site performance it seems, so I'll leave it running for a bit > if that might help trace where the problem might be. > > thread_id: 3 > date_now: 1556706076.018998 > loops: 246336607 172211047 246343444 300853502 230819619 195445612 263889138 > 194968394 > wake_tasks: 75086490 25141922 102567287 131951431 67591528 47537756 108661002 > 45316125 > empty_rq: 44638490 67387609 37452856 50370558 55838595 59929139 57700911 > 34436393 > long_rq: 66107108 17951324 177726917 127643664 59754161 40347246 103056053 > 36018697
This looks like you're dealing with some unhandled events again. We've fixed several of these in 1.9.7 and a last one just after this release to fix an issue in H2 with some fragmented HEADERS frames. Thus depending on the version you're running on, you may possibly be facing one of these issues that are now fixed. Otherwise another useful output could be "show fd" and "show sess all". Please be aware that this will reveal some possibly private info so you may want to double-check and edit it by hand first. In the "show sess all" output, those exhibiting a large values of "calls" or "age" can be very useful. Thanks, Willy
