On Tue, 29 Jan 2013, l d wrote: > I've already analysed the haproxy log, captured and analysed packets > with tcpdump and wireshark, but I can't see any obvious reason why > it's happening. I tried to raise the client and server timeouts but it > didn't help and I can't keep it too high.
Hello I too spent countless nights debugging haproxy failures with various degrees of success. When I loose all hope I turn to network engineers who blame the software, then software developers blame the network, and you get stuck in the middle with 50,000 408 or 503 responses a day. > 2) Why can't I see all errors in the log file ? Even in debug mode, I > only get a small percentage (around 20%) of all the frontend errors > counted in the stats page. I noticed those discrepancies as well. Often also the failures of all backends individually are 20 times lower than the combined column in the stats. Someone once told me that number can include failed health checks and some other non obvious failures. > 3) Do you have any tip about how I could continue to troubleshoot this > ? One of the better threads recently was "Help with cleaning up our error log output and request error counts" (Message-ID: [email protected]). -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
