Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Everything works nicely if I have worker_processes=1, or I run one request at a time. If I open a browser on a fresh nginx install and holds F5 down a couple of seconds, the sockets gets lingering as CLOSE_WAIT, and nginx wont do anything (other than stuffing more sockets in CLOSE_WAIT..)

The more workers I use, the sooner it gets stuck. Just one of the workers has listed any sockets though..

Any idea what might be causing this?

share|improve this question
Stuck means it won't answer any more requests? Is this CLOSE_WAIT on the client or the upstream? Does the error_log say anything? Can you include tcpdump output of a failed request? – polynomial Oct 2 '11 at 19:36
Your talking latin.. After a request has become CLOSE_WAIT, any subsequent request also becomes CLOSE_WAIT. No errors are showing in the logs. I'm on windows - could you explain how to do an tcpdump? (Whats the tool called in windows?) – simendsjo Oct 2 '11 at 19:48
Wireshark makes a windows version: – polynomial Oct 2 '11 at 19:55
Damn wireshark seems complex. It doesn't seem like it listens on local-only sockets – simendsjo Oct 3 '11 at 18:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.