Re: Retr Warnings and Socket Issues

On Mon, Jun 23, 2008 at 06:33:50PM -0400, James wrote:
> I have a few questions I would like to pose to the HAProxy list.
>
> First, is there a listing in the documentation as to what exactly
> triggers the various Warnings and Errors that come up in the stats
> output? When one of these conditions occur, does it come up in the
> haproxy logs? I am seeing a lot of retry warnings on 3 out of 5 servers
> defined in one of my backends (the numbers tend to keep increasing on
> every reload).

The retries indicate that haproxy failed to establish a connection to a server within the "contimeout". It might be because the server is already overflowed and does not respond, because there is a poorly configured ip_conntrack somewhere, because you don't have enough source ports on your haproxy machine. There are many reasons for this to happen. You should check with tcpdump that the packets are correrctly going out of the machine, and observe if the other end responds.

> Also, I've noticed that at times of high usage, the number of active
> connections between the backend servers is uneven by a large margin. The
> servers that run linux seem to end up with hgher numbers than machines
> with freebsd installed on it. Could this have something to due with
> socket issues on the backend servers? Anyway to go about debugging this?

Possibly, or also network packet losses between the linux servers. Wouldn't you be running gigabit ethernet ports connected to forced-100 Mbps switches ? In this case, you would most likely end up with a 100-half machine. Check with ethtool.

Willy Received on 2008/06/25 07:09