You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2022. It is now read-only.
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is extremely strange, but with "--syslog" on, I got a serious amount of dropped connections. Around 50% of curls looked like this:
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:
Here is more evidence:
The text was updated successfully, but these errors were encountered: