Hey, Can you let me know why you're using a minconn parameter on SSH protocol? Also, do you have a patch for the proxy protocol on your SSH server? If yes, I'm interested to get it :)
Saying that, I can't see anything weird in you conf, unless you have reach the maxconn allowed. What does the logs says? What does the stats socket reports (if you have enabled it)? regards On Wed, Jul 11, 2012 at 2:52 PM, Ben Timby <[email protected]> wrote: > I use haproxy for HTTP(S) and SSH. > > I am running version: haproxy-1.5-dev11 > > My pool of backend servers are different for each protocol. > > I am having a problem with SSH, periodically (every day) haproxy stops > accepting connections. My Nagios check (tcp port 22) receives: > > CRITICAL - Socket timeout after 10 seconds > > This condition persists until I restart haproxy. At the same time, my > HTTP(S) virtual servers are unaffected. Also, the backends are just > fine, I can open a connection directly to them without issue. I don't > have access to the haproxy status page just now, but when I do, I can > provide information from it. > > Here is my configuration for the SSH load balancer: > > listen ssh-vip0 > bind ??.??.??.??:22 > mode tcp > option tcplog > balance leastconn > server ssh0 ssh0:22 minconn 10 maxconn 256 send-proxy > server ssh1 ssh1:22 minconn 10 maxconn 256 send-proxy > > I don't see anything in the haproxy log about this virtual server, > just traffic from the other working ones. > > Any ideas? What other information would be useful. >
