OK, DNS propagation has happened.
Scanning with ssllabs test: - 2.4.29-1ubuntu4.6 (all ok) - 2.4.29-1ubuntu4.7 (ok as well)
I see worker threads start while the test is running, like 32 or so. But never does the cpu consumption peak to anything high.
Nor do processes hang around in CLOSED_WAIT state.
There must be something else to it.
Next I ran: - 2.4.29-1ubuntu4.7 + giraffe config which seems to trigger the bug
And I got: ~100% CPU top: 4375 www-data 20 0 758280 7072 4944 S 88.2 1.5 4:32.91 apache2 netstat tcp6 1 0 paelzer-apache-bu:https www.ssllabs.com:43511 CLOSE_WAIT
\o/
Now this might be flaky, I'll reset and try again.
OK, DNS propagation has happened.
Scanning with ssllabs test:
- 2.4.29-1ubuntu4.6 (all ok)
- 2.4.29-1ubuntu4.7 (ok as well)
I see worker threads start while the test is running, like 32 or so.
But never does the cpu consumption peak to anything high.
Nor do processes hang around in CLOSED_WAIT state.
There must be something else to it.
Next I ran:
- 2.4.29-1ubuntu4.7 + giraffe config which seems to trigger the bug
And I got: apache- bu:https www.ssllabs. com:43511 CLOSE_WAIT
~100% CPU top:
4375 www-data 20 0 758280 7072 4944 S 88.2 1.5 4:32.91 apache2
netstat
tcp6 1 0 paelzer-
\o/
Now this might be flaky, I'll reset and try again.