Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

One of my dedicated servers had some network issue today and the data center has to replace some router. Since then the sites on that server returns "The connection was reset" error most of the time.

I tried installing nginx and it opens better, but it still shows the error sometimes.

Everything in the config seems normal, what could be causing this error?


Just noticed that in whm > apache status there are always only 1 requests currently being processed, 8 idle workers. I know for sure the server received thousands of requests per minute. What could be limiting this to such a low number?

share|improve this question
Post your apache confs, specifically the ones surrounding, Min/MaxServers, ServerLimit, MaxClients, etc. – KM. May 30 '12 at 21:50

You seem to be running both apache2 and nginx, I imagine that they would both compete for port 80. Hence you would have to provide more details of your setup.

To show which process has port 80;

netstat -lntp

see which services are running;

ps -ef | egrep "(httpd|nginx)"

show which server is listening locally;

 $ perl -MLWP::Simple -e 'print [LWP::Simple::head("")]->[-1]';

show apache configuration;

 # apachectl -S
share|improve this answer
Thanks for the tip, file is empty. But check the updated question, any idea about that workers limit? – usjes May 30 '12 at 18:31
If nginx or apache is already running when you start the other they cannot bind to port 80 so they fail start (address already in use) – Iain May 30 '12 at 21:51
why the downvote? – Tom H May 30 '12 at 21:56

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.