Apache displaying massive Reading request

Discussion in 'Apache' started by softtech, Aug 11, 2012.

  1. #1
    hi:
    one vps server is busy these days, webpage opening very slow, sometimes can not open at all, but ping speed has not changed, online visitors about the same, 100-200 online.
    From WHM, i can see a lot "?" Reading request, maybe this is the reason making the busy server, I don't know what is it and how do I terminate it??

    attached a screen cap. , thanks for your help

    ea39d41f22bd87b7794004e6ff7130ba.jpg
     
    softtech, Aug 11, 2012 IP
  2. shindig

    shindig Peon

    Messages:
    34
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    The '?' means that Apache can't process the request. Most likely cause is too many requests to one of your sites and Apache's ServerLimit or MaxClients total was reached. Restarting Apache should clear this up. If it doesn't, do the following:

    Log into your VPS's root account via SSH. Then:

    
    /etc/rc.d/init.d/httpd stop
    fuser -k 80/tcp
    /etc/rc.d/init.d/httpd start
    
    Code (markup):
    What this will do is

    * stop Apache
    * kill any stale Apache processes
    * start Apache


    After that, I'd advise checking all of your sites traffic logs (especially the error logs) to see if you can see anything abnormal.
     
    shindig, Aug 11, 2012 IP
  3. softtech

    softtech Member

    Messages:
    4
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    36
    #3
    i am already doing this way
    but this is not perment solution, because in the evenning time 8 to 11 pm getting this error high and server sites dam slow some time off.
    pls advice if there is any permenent solution.

    regards
     
    softtech, Aug 11, 2012 IP
  4. shindig

    shindig Peon

    Messages:
    34
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #4
    A permanent solution would be to find the issue and fix it. It could be a rogue spider or something like that. As I suggested, you should check the Apache logs to find anything abnormal :)
     
    shindig, Aug 11, 2012 IP