Hi Ben, On Mon, Oct 18, 2010 at 12:38:13PM -0700, Ben wrote: > hello -- > > i am using haproxy 1.4.8 to load balance between four read-only postgresql > databases. the databases are identical, the hardware is not. my > configuration is included below. the connections can be short, like a few > seconds, to long running (days or more.) the loads on the connections can > also be varied. > > it appears to work fine but after some random amount of time it starts taking > a very long time to make connections through the proxy, even though > connecting directly to one of the backends takes no time at all. if i look > at the stats webpage it tells me that a small number of connections appear to > be queued and not moving towards being fully connected, even though there are > open connections available on the backends. i am at a loss for how to > diagnose this further or fix this -- typically i do a restart > > haproxy -f /usr/local/etc/pg_haproxy.cfg -sf $(cat > /var/run/haproxy/pg_haproxy.pid) > > and it usually fixes the problem.
Clearly this is not expected. Do you have a copy of the stats page that shows the queued connections at the same time of the server status, an possibly the related logs ? We had issues in that area a long time ago (around 1.3.15) but not since then. However, there could be a remaining corner case exhibiting an issue. Your config looks clean enough, it should not cause any failure. > i'm not sure if this is unrelated but i'm having trouble getting logging > messages on my rsyslogd log. on startup i get something on > /var/log/localmessages but nothing else. I'm not used to rsyslogd, but most often when you don't get anything in your logs, it's because the syslog daemon does not listen to the UDP port (514). Regards, Willy
