> No warnings is syslog or dmesg Can you issue a "show errors" [1] on the control socket?
> To recover I switched away from the haproxy server to > an older Apache-based web server. So haproxy is still in a broken condition on that server? If thats the case, you could attach strace to the process and see what haproxy is doing: sudo strace -p<pid> > Load was high, around 1.5 How many CPUs do you have? You need to check where that load is coming from. Is haproxy spending cpu cycles in user space or where is the load coming from? > which is better to use - httpclose or http-server-close? "option http-server-close" enables keepalive on the client side, which is generally a good thing. I suggest you configure it along with "timeout http-keep-alive" [2]. But this has nothing to do with your problem and wont fix the issue. Regards, Lukas [1] http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#show%20errors [2] http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20http-server-close [3] http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#timeout%20http-keep-alive
