why my apache always refuse new connection even if the loads is very low

Discussion in 'Apache' started by Greyhound, Feb 9, 2011.

0
  1. #1
    hey guys, i need your help. i have a vps that running apache as its http daemon. but i found apache always refuse new connections (means i can't open my websites hosted there) in sometime. when it happened, i logged into ssh and checked the memory usage and server loads but both of them were low. and, i checked the connections and only found 10~20 connections and also a very few syn_wait signal. the problem is, i don't know when it will happen again. seems it is randomly happened.

    here's my config file:

    <IfModule prefork.c>
    StartServers 5
    MinSpareServers 8
    MaxSpareServers 15
    ServerLimit 512
    MaxClients 512
    MaxRequestsPerChild 500
    </IfModule>

    please help me. thanks.
     
    Greyhound, Feb 9, 2011 IP
  2. nixproxy

    nixproxy Peon

    Messages:
    83
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    There can be various reasons for that. I would check with your provider is that physical server overloaded with connections that hosts your VPS. I have various VPS´s myself but im not hosting apaches on them, other similar services and haven´t expired anything similar.
     
    nixproxy, Feb 9, 2011 IP
  3. Greyhound

    Greyhound Banned

    Messages:
    1,637
    Likes Received:
    12
    Best Answers:
    0
    Trophy Points:
    78
    #3
    but if it's caused by the main node, why it will be ok after i restart httpd in my vps?
     
    Greyhound, Feb 10, 2011 IP
  4. Usershare

    Usershare Peon

    Messages:
    36
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #4
    look at the server logs and see...or do service httpd status and you will see how many connections running.If you maxed, just increase those values.
     
    Usershare, Feb 13, 2011 IP
  5. srisen2

    srisen2 Peon

    Messages:
    359
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #5
    you could have a script that is looping or a internal system request that keeps processing due to an setting you need to adjust.

    I have seen something similar happen when a system keep contacting itself due to a configuration error which caused an overload and crashed apache until it was set correctly
     
    srisen2, Feb 14, 2011 IP