Haproxy signal 10
-
We are running pfsense:
2.2.6-RELEASE (amd64)
built on Mon Dec 21 14:48:53 CST 2015
FreeBSD 10.1-RELEASE-p25haproxy is haproxy-devel v 0.35
We have over 100mb/s of traffic flowing over haproxy and we see far to many signal 10's
grep "signal 10" syslog.log |grep "Jan" |wc -l
18
grep "signal 10" syslog.log |grep "Feb" |wc -l
92
Any thoughts
-
I have not seen that with haproxy here, though we have occasionally seen that happen with lighttpd. I believe it may be related to something in OpenSSL since it only appears to happen with daemons handling SSL traffic, but it's tough to say. It does not happen at all on 2.3 with nginx.
It may not be feasible to try but you might give a 2.3 snapshot a test. HAProxy is there and working, with a newer version of the base OS and HAProxy it's less likely to hit that.
There are some 2.2.7 snapshots on our snapshot server as well (not linked) but those do not see as much testing as the 2.3 snapshots at the moment, we're still not sure if there will be another 2.2.x release officially.
-
Also if the service itself is dying completely and not just a thread, the service watchdog package can help keep it running by restarting it when it's down.
-
Haproxy does not use threads. Its a single thread event driven process.. Other than that the 1.6.2 haproxy version as far as i know does not have crash issues..
@Jimp, would it perhaps be possible to compile a new version of haproxy+openssl for pfSense 2.2.6 ?
-
Compiling any new packages for 2.2.x at this point is unlikely to happen (or succeed).
I'd suggest 2.3 but due to some changes made this past week in CARP handling haproxy is broken there as well, though it's not haproxy's fault.
-
I have a problem with HaProxy exiting on signal 10… since few days...
PfSense 2.2.5 and the latest haproxy-develI don't have any clue on this issue.
Dying 1..2...or 3 times a day... I have to restart by hand each time.
Was working well for months before.
