#1, #2 and #3 gave me nothing in terms of "load" on the target apache server
after the actual run.
I had the expected worker threads around but those were idling.
I had no connections in CLOSE_WAIT state nor showing up as reading in
the server status module.
@Stefan - we have two obvious paths from here.
a) only the ssllabs test causes this, which will make testing of usual non
exposed debug systems much harder
b) some other part of your setup combined with the new version triggers this
behavior.
You could help tremendously if you'd have the options to set up either:
- verify (A): setup a default config like I outlined but exposed to the
internet and run the ssllabs test against it (if you have the mans to do so)
- verify (b): run the tests mentioned above (and others if you know/have them)
against your existing setup. Does and of them trigger the bad behavior for your
setup?
If it does try to drop custom config one by one until we have identified which
part is the critical one.
Marking incomplete to get this extra info, I hope our both pre-work will
help Andreas (who will show up in a bit) to get a fast start on this.
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836329
Title:
Regression running ssllabs.com/ssltest causes 2 apache process to eat
up 100% cpu, easy DoS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1836329/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
