The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Apache high load

Discussion in 'EasyApache' started by Lizard, Mar 17, 2008.

  1. Lizard

    Lizard Member

    Joined:
    Aug 21, 2005
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    I have some problem with apache.

    Code:
    Srv	PID	Acc	M	CPU	SS	Req	Conn	Child	Slot	Host	VHost	Request
    0-0	12801	0/428/1033	R 	4.84	275	1	0.0	2.79	6.97 	?	?	..reading..
    1-0	13296	0/160/969	R 	1.56	278	1	0.0	1.58	6.71 	?	?	..reading..
    2-0	13483	0/132/677	R 	1.36	269	1	0.0	0.79	4.99 	?	?	..reading..
    3-0	12856	0/192/823	R 	1.85	275	1	0.0	1.26	7.56 	?	?	..reading..
    4-0	12766	0/283/641	R 	2.54	281	1	0.0	1.37	4.60 	?	?	..reading..
    5-0	12970	0/353/1055	R 	4.32	274	1	0.0	2.66	7.72 	?	?	..reading..
    6-0	11400	0/962/962	R 	9.79	280	1	0.0	7.53	7.53 	?	?	..reading..
    7-0	13568	0/74/992	R 	0.67	272	1438	0.0	0.28	7.43 	?	?	..reading..
    8-0	13728	0/5/984	R 	0.00	276	1	0.0	0.01	6.84 	?	?	..reading..
    It`s causing high load but I don`t know what is it.

    Any ideas ?
     
  2. mm1250

    mm1250 Well-Known Member

    Joined:
    Nov 10, 2006
    Messages:
    108
    Likes Received:
    0
    Trophy Points:
    16
    Hello,

    I am getting this also. I have over 100 of those show up at once and I have no idea what site it is considering i have over 120 sites on the server. It's quite fustrating considering I have a server admin company that I keep telling about it and they are telling me it is normal.

    I also notice that it takes 300 seconds before it goes away.

    It would be great if someone or cPanel can please help with this.
     
  3. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    Without you doing more investigating it could be any number of attacks. If you see them come in a group and then go away it could be a http attack that was done by at bot and likely IP targetted so it might not come back again. But like I said you would have to pinpoint the attack time and then scan your logs for more hints.

    As to the 300, that sounds like you have a default TimeOut directive in httpd.conf which should be lower anyway. If you can edit the httpd.conf (dont do it if you are not comfortable with it). Lower it to something like 45 and see if anyone complains about timeouts.

    Also see this from the apache docs:

    "TimeOut directive
    Syntax: TimeOut number
    Default: TimeOut 300
    Context: server config
    Status: core
    The TimeOut directive currently defines the amount of time Apache will wait for three things:

    The total amount of time it takes to receive a GET request.
    The amount of time between receipt of TCP packets on a POST or PUT request.
    The amount of time between ACKs on transmissions of TCP packets in responses.
    We plan on making these separately configurable at some point down the road. The timer used to default to 1200 before 1.2, but has been lowered to 300 which is still far more than necessary in most situations. It is not set any lower by default because there may still be odd places in the code where the timer is not reset when a packet is sent. "
     
Loading...

Share This Page