Activity

From 2021-01-21 to 2021-01-27

19:46 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: Issue persists with:
@server.feature-flags += ("server.h2c" => "disable")@ and @server.feature-flags += ("server.h2p... mitd
18:47 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: Looks like it still occurs with both flags disabled. Will try it with h2c @disabled@ and h2proto @enabled@ once this ... mitd
17:24 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: In an effort to bound where the problem is, does the problem occur if you (temporarily) disable those feature flags a... gstrauss
16:03 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: Unfortunately yes, it sends tons of requests.
Here are the flags:
@
server.feature-flags += ("server.h2proto... mitd
06:41 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: 14561 lines of requests is, ... um ..., a lot.
Would you share your @server.feature-flags@ settings, if you have set... gstrauss

22:49 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: Seems like the issue still happens with wolfssl.
I've also attached a (very long) log file with the calls from the q... mitd
22:17 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: Great. Thanks. If you reproduce the @CLOSE_WAIT@, you may have to attach with @gdb@ and issue @call (int)close(xxxx... gstrauss
20:54 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: Sorry about the delay, had things come up. Still looking into it.
What I've tried so far.
I've installed wolfssl an... mitd
01:17 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: @mitd: I am interested in helping to track this down. Do you have an estimate when you might have time to come back ... gstrauss

20:05 Bug #3056: OCSP Stapling reload seems not to work: Thanks for the update.
I think the issue had to do with somehow incorrectly walking the configuration, not that th... gstrauss
18:59 Bug #3056: OCSP Stapling reload seems not to work: The update of @ssl.stapling-file@ succeeded now, about 5min before the end of "Next update" I see a log message readi... flynn

06:28 Bug #3056: OCSP Stapling reload seems not to work: After spending quite a bit of time trying to reproduce this, I think that the stapling file refresh code is pretty so... gstrauss

19:44 Bug #3056: OCSP Stapling reload seems not to work: No yet, next "Next Update" is on Jan, 24th. I did not manage to create ocsp responses with less than 7 days. flynn
18:05 Bug #3056: OCSP Stapling reload seems not to work: Anything interesting in your logs now that the original stapling file has expired and a new one should have been read? gstrauss
06:31 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: What version of the openssl libraries are installed on your system?
@openssl version@ gstrauss
06:00 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: Only because I haven't yet asked: is there any trace in the lighttpd error log? gstrauss
05:55 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: The most recent trace that you shared shows @BIO_write()@ and @write()@ along with SIGPIPE, which is blocked, but the... gstrauss
04:29 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: It does not look like lighttpd was built with full debugging symbols, or maybe lighttpd has not been deployed with de... gstrauss
04:03 Bug #3059: Connections stuck in Close_Wait causing 100% cpu usage: I attempted to step through using gdb today and generated the following:
https://pastebin.com/niNTr7Ja
I'm unsure i... mitd

Also available in: Atom

Lighttpd