I actually see the same error while going to the individual servers as well and i am using apache server Server version: Apache/2.2.14 (Ubuntu)
--- On Thu, 2/3/11, carlo flores <[email protected]> wrote: From: carlo flores <[email protected]> Subject: Re: Error during Apache AB benchmarking test -- HAProxy To: "Amol" <[email protected]> Cc: [email protected] Date: Thursday, February 3, 2011, 10:54 PM I've never seen this on one of our HAProxy benchmarks. We usually use siege and our own application (also testing the HTTP applications/user behavior). For clarity, you do not see timeouts when going direct to, say, nginx serving "hi" on port 80? I ask because maybe this is really a ulimit or kernel tuning thing or a haproxy.cfg maxconn thing behind a slow application. On Thu, Feb 3, 2011 at 7:43 PM, Amol <[email protected]> wrote: i was running some simple benchmarking tests for apache webservers using HA proxy as the load balancer and i am getting this error when i increase the load on the servers ab -n 10000 -c 100 http:/xxxxx apr_socket_recv: Connection timed out (110) ab -n 10000 -c 10 http:/xxxxx Completed 1000 requests Completed 2000 requests Completed 3000 requests apr_socket_recv: Connection timed out (110) Total of 3867 requests completed any one has seen this before on the webservers? Regards....
