Skip to content
This repository has been archived by the owner on May 24, 2022. It is now read-only.

Dropped connections with "--syslog" enabled #99

Open
mitchellh opened this issue May 27, 2012 · 1 comment
Open

Dropped connections with "--syslog" enabled #99

mitchellh opened this issue May 27, 2012 · 1 comment

Comments

@mitchellh
Copy link

This is extremely strange, but with "--syslog" on, I got a serious amount of dropped connections. Around 50% of curls looked like this:

→ curl -i https://domain.com
curl: (35) Unknown SSL protocol error in connection to domain.com:443 

When I removed the "--syslog" flag, these went away.

Further evidence for this is that we recently switched from Stunnel to Stud. Stunnel had reached a single-core scaling limit so we switched to Stud. Stud immediately handled about 50% of the traffic as Stunnel, which was confusing. When we removed the "--syslog" flag, it went back up to prior numbers.

We run stud as follows:

stud --backend=127.0.0.1,8443 --backlog=500 --ciphers="ALL:!aNULL:!ADH:!eNULL:!MEDIUM:!LOW:!EXP:RC4 RSA: HIGH" --frontend=0.0.0.0,443 --group=stud --keepalive=1800 --quiet --ssl --write-proxy --user=stud --workers=8 /etc/ssl/web.pem

Here is more evidence:

Graphs

@pkoper
Copy link

pkoper commented Sep 1, 2012

Looks like you have slow syslog which blocks your stud on /dev/log unix socket. Check disk I/O saturation or look for any other problem with syslog performance like e.g. DNS name resolving. Probably not a stud issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants