Too many CLOSE_WAIT connections about relayd HOT 2 OPEN

I have seen similar behavior while testing, where the number of active sessions (HTTPS) exceeds 500 (once it hits 501) causes the service to stop responding to requests. Waiting a little while will hard timeout some of the sessions, and the service becomes responsive again, but additional page loads will bring the active session count back to 501 and it becomes non-responsive again.

The session expiration appears to be broken from what I can tell - where sessions are expired extremely slow (1 per minute or more?) regardless of what the "session timeout" option is set to (I have it set to 15 seconds for testing).

My test configuration is pretty simple, with a single site running on httpd on the same server as relayd. Browsing a single test page (HTTPS page) with the word "Testing" copied a bunch of times appears to work fine. Holding down the F5 key to repeat load the page will cause the active session count to rise, up to 501, and then relayd stops responding to requests.

Note that relayctl works while this is happening, This is an example after it becomes non-responsive to additional HTTPS requests:

# relayctl show relay
Id      Type            Name                            Avlblty Status
1       relay           httpsproxy                              active
                        total: 4344 sessions
                        last: 0/60s 4344/h 4344/d sessions
                        average: 0/60s 0/h 0/d sessions

I'd love to get this resolved since I would love to use relayd for all of our Layer 7 balancing, but we're stuck. Reyk - if you need any help testing, let me know. I'll be happy to help.

Eric

from relayd.

I forgot to mention that my testing was done with OpenBSD 5.7 (fresh install from ISO).

Also, it looks like relayd hung last night, causing 100% CPU utilization on all 4 processors.

Eric

from relayd.