On Tue, Apr 14, 2009 at 4:51 AM, Miha Verlic <ml@xxxxxxxxxx> wrote: > Hello, > > lately I noticed that our web servers don't answer to a request from time to > time. I created a dummy http checking script every few seconds to debug a > problem. It seems that server does not even respond with SYNACK packet. Here > is the excerpt from wireshark/tcpdump log: > > # failed request > 10629 12:56:23.642861 10.9.0.14 10.9.1.33 TCP 57400 > http > [SYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=663117245 TSER=0 WS=7 > 10632 12:56:26.642216 10.9.0.14 10.9.1.33 TCP 57400 > http > [SYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=663117545 TSER=0 WS=7 > - tweaked ListenBackLog + /proc/sys/net/core/somaxconn IMO especially with non-zero listen backlog, it doesn't matter how Apache screws as the host OS should be driving things that early on. I'd start looking at your OS network config / equipment. -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|