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.

CPUwatch really is broken.

Discussion in 'General Discussion' started by andyf, Mar 8, 2003.

  1. andyf

    andyf Well-Known Member

    Joined:
    Jan 7, 2002
    Messages:
    246
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    UK
    http://forums.cpanel.net/showthread.php?s=&threadid=5283&perpage=15&pagenumber=1

    Extended from the above thread.

    We have a new box running cpanel that for various reasons has been idle for 2 weeks now, not a single site on the box.

    We just did an apache recompile on there and as soon as the CPU hit 1.0 we got a CPUwatch warning to the admin email address warning that the CPU had been maxed out for 6 hours.

    Clearly this is not the case, until the compile the box was sitting totally idle and had been for weeks.

    Nick or whoever please can you have a look at this, its happening on every cpanel box I have access to and makes the whole idea of cpuwatch totally pointless if its warning you everytime something causes the smallest of load spikes.

    Thanks.
     
  2. andyf

    andyf Well-Known Member

    Joined:
    Jan 7, 2002
    Messages:
    246
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    UK
    *bump*

    Can anyone else confirm they are seeing similar?
     
  3. mitul

    mitul Well-Known Member

    Joined:
    Feb 8, 2003
    Messages:
    291
    Likes Received:
    0
    Trophy Points:
    16
    When we upgrade to latest apache our server would show everything running ok but would not server any sites. We had to recompile apache with option 5 and then selecting the FD_SETSIZE option from the menu.
     

Share This Page