Results 1 to 6 of 6

Thread: Apache

  1. #1
    Join Date
    Dec 2007
    Posts
    35

    Apache

    Current Time: Wednesday, 07-May-2008 22:48:23 BRT
    Restart Time: Wednesday, 07-May-2008 22:40:30 BRT
    Parent Server Generation: 0
    Server uptime: 7 minutes 53 seconds
    Total accesses: 780 - Total Traffic: 14.6 MB
    CPU Usage: u5.17 s.98 cu0 cs0 - 1.3% CPU load
    1.65 requests/sec - 31.5 kB/second - 19.1 kB/request
    6 requests currently being processed, 94 idle workers


    [email protected] [~]# netstat -plan|grep :80 | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -n
    1 0.0.0.0
    1 127.0.0.1
    1 201.19.39.1
    1 201.40.7.190
    1 64.74.148.60
    1 74.6.9.170
    2 189.51.154.139
    2 201.3.38.184
    2 84.36.150.176
    3 76.25.178.120


    I do not understand this because of this.

  2. #2
    Join Date
    Apr 2005
    Location
    Cochin
    Posts
    2,446
    What is the exact issue you are currently facing ?
    Sam
    Supportlobby.com - Expertise in Windows/Linux server support, IaaS and PaaS Management
    Spiralbean.com - Custom Software Development
    Email: exec @ activelobby.net | Skype: unni_active

  3. #3
    Join Date
    Dec 2007
    Posts
    35
    In my other is well

    Current Time: Thursday, 08-May-2008 12:40:02 BRT
    Restart Time: Tuesday, 06-May-2008 16:14:13 BRT
    Parent Server Generation: 2
    Server uptime: 1 day 20 hours 25 minutes 48 seconds
    Total accesses: 295648 - Total Traffic: 5.8 GB
    CPU Usage: u57.13 s7.37 cu0 cs0 - .0403% CPU load
    1.85 requests/sec - 38.0 kB/second - 20.5 kB/request
    2 requests currently being processed, 8 idle workers


    6 requests currently being processed, 94 idle workers
    Because this is in 100?

  4. #4
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    8,910
    It's possible that there was a sudden surge of traffic to one of the websites on your server, maybe an aggressive web crawler, that spawned a lot of Apache processes which is why you now see a high number of idle workers. The netstat output will not always show a surge of traffic, especially if the connections are already closed and long gone.

    If you want to get rid of the high number of idle workers, just gracefully restart Apache:

    /usr/local/apache/bin/apachectl graceful
    Patrick William | RACK911 Labs | Software Security Auditing
    400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com

    www.HostingSecList.com - Security notices for the hosting community.

  5. #5
    Join Date
    Dec 2007
    Posts
    35
    Traffic is the same as always.
    This site was the former vps and never rose from 30 idle workers

  6. #6
    Join Date
    Dec 2007
    Posts
    35
    Now this:
    17 requests currently being processed, 133 idle workers

    Looking apaches other is on average of 30.
    As with just these idle workers the most?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •