[quote:7c03fa594a][i:7c03fa594a]Originally posted by joana[/i:7c03fa594a]
yeb, DarkORB support..
They say the fix was to increase number of cpus in the config file and he did increase it to 5 but kept getting those emails even though the load mentioned in the email is 1.*
[/quote:7c03fa594a]
I had already tried that on one box, and that is a horrible 'fix' as if something legitimate really does cause the load to jump to 4-5, then you wouldn't get necessary notifications to address the situation. That's like applying a band-aid to a wet wound.
Personally I think it would be best to have statscheck look at the 5 minute average load, not the 1 minute load as the stats are taking the CPU over the limit for that particular moment.
My BIGGEST question remains - why is it running stats for ROOT?!?!?
Jaz
yeb, DarkORB support..
They say the fix was to increase number of cpus in the config file and he did increase it to 5 but kept getting those emails even though the load mentioned in the email is 1.*
[/quote:7c03fa594a]
I had already tried that on one box, and that is a horrible 'fix' as if something legitimate really does cause the load to jump to 4-5, then you wouldn't get necessary notifications to address the situation. That's like applying a band-aid to a wet wound.
Personally I think it would be best to have statscheck look at the 5 minute average load, not the 1 minute load as the stats are taking the CPU over the limit for that particular moment.
My BIGGEST question remains - why is it running stats for ROOT?!?!?
Jaz
They went in to my servers and found an issue with cpuwatch. However, I've still been getting alerts since that time, but they feel it is just remnants from earlier log processing. We'll see what happens tomorrow after things kick off fresh tonight.
Jaz
Jaz
B
bdraco
Guest
stats are not running as root. If cpuwatch is not installed it falls back and uses logrunner. Just copy cpuwatch into /usr/local/cpanel/bin and the problem will go away.
[i:e9f3d618e5]Originally posted by bdraco[/i:e9f3d618e5]
stats are not running as root. If cpuwatch is not installed it falls back and uses logrunner. Just copy cpuwatch into /usr/local/cpanel/bin and the problem will go away.
[/quote
Where do you get the cpuwatch from?
I have searched for it on all servers and it's not there but this issue only happens on 1 server though..
It was indeed the cpuwatch issue. Oddly enough it wasn't installed on any of my servers (more than half a dozen), with some of my servers dating back to last September (and yes, I too was only having problems on about half of them). It appears one of the WHM/CP upgrades deleted that file (assuming it should have been there to begin with).
I'd recommend opening a ticket with support asking them to fix one of your servers. Once they do that, you can copy the cpuwatch file out to your others. It does take about 12-24 hours to flush itself, so you may still get a few of those odd statscheck alerts during that timeframe.
The file needs to go into these two locations:
/usr/local/cpanel/bin
/usr/local/cpanel/src/wrap
Jaz
I'd recommend opening a ticket with support asking them to fix one of your servers. Once they do that, you can copy the cpuwatch file out to your others. It does take about 12-24 hours to flush itself, so you may still get a few of those odd statscheck alerts during that timeframe.
The file needs to go into these two locations:
/usr/local/cpanel/bin
/usr/local/cpanel/src/wrap
Jaz
[quote:9ceffe0863][i:9ceffe0863]Originally posted by jsteel[/i:9ceffe0863]
It was indeed the cpuwatch issue. Oddly enough it wasn't installed on any of my servers (more than half a dozen), with some of my servers dating back to last September (and yes, I too was only having problems on about half of them). It appears one of the WHM/CP upgrades deleted that file (assuming it should have been there to begin with).
I'd recommend opening a ticket with support asking them to fix one of your servers. Once they do that, you can copy the cpuwatch file out to your others. It does take about 12-24 hours to flush itself, so you may still get a few of those odd statscheck alerts during that timeframe.
The file needs to go into these two locations:
/usr/local/cpanel/bin
/usr/local/cpanel/src/wrap
Jaz[/quote:9ceffe0863]
Hi there,
I'm having similar problems
I found a copy of cpuwatch in my beta Cpanel test server and I've uploaded the file in my production server. I found the file under /usr/local/cpanel/src/wrap so I've uploaded the file to the same location in my production box. If it does not work, I will try Jaz's suggestion.
If someone can confirm, the file size is 5408, about 6k. Is this correct ?
I'll keep you guys posted, thanks for all the info.
Raymond
It was indeed the cpuwatch issue. Oddly enough it wasn't installed on any of my servers (more than half a dozen), with some of my servers dating back to last September (and yes, I too was only having problems on about half of them). It appears one of the WHM/CP upgrades deleted that file (assuming it should have been there to begin with).
I'd recommend opening a ticket with support asking them to fix one of your servers. Once they do that, you can copy the cpuwatch file out to your others. It does take about 12-24 hours to flush itself, so you may still get a few of those odd statscheck alerts during that timeframe.
The file needs to go into these two locations:
/usr/local/cpanel/bin
/usr/local/cpanel/src/wrap
Jaz[/quote:9ceffe0863]
Hi there,
I'm having similar problems
I found a copy of cpuwatch in my beta Cpanel test server and I've uploaded the file in my production server. I found the file under /usr/local/cpanel/src/wrap so I've uploaded the file to the same location in my production box. If it does not work, I will try Jaz's suggestion.
If someone can confirm, the file size is 5408, about 6k. Is this correct ?
I'll keep you guys posted, thanks for all the info.
Raymond
Raymond, yes it is very small in size. Just drop it into the two locations I noted and wait 12-24 hours. The strange alerts should stop.
Jaz
Jaz
jsteel, is the problem gone from your servers even after upgrading to Cpanel6?
After upgrading to Cpanel6, we started recieving those emails again (double emails) for the last few days even though the Cpuwatch is there, Cpu=3 and did the cpanel start comamand..
any ideas?
After upgrading to Cpanel6, we started recieving those emails again (double emails) for the last few days even though the Cpuwatch is there, Cpu=3 and did the cpanel start comamand..
any ideas?
Same problem here.. I solved that problem just like before upgrade to cp6.
I removed this two files.
/usr/local/cpanel/bin/dispatchcpustats
/usr/local/cpanel/bin/dispatchstats
I dont recomed to anyone to do this, I do this just becouse I have my own non cpanel related software to track loadaverage on server and bandwith hogs.
If you are not intrested in geting alert when your server is overloaded you can remove this two files (you will get them again when you update cpanel).
BTW when someone get's 10 false alerts daily with message that server is overloaded, he will for sure ignore 11 alert wich maybe real.
Think about it.
I removed this two files.
/usr/local/cpanel/bin/dispatchcpustats
/usr/local/cpanel/bin/dispatchstats
I dont recomed to anyone to do this, I do this just becouse I have my own non cpanel related software to track loadaverage on server and bandwith hogs.
If you are not intrested in geting alert when your server is overloaded you can remove this two files (you will get them again when you update cpanel).
BTW when someone get's 10 false alerts daily with message that server is overloaded, he will for sure ignore 11 alert wich maybe real.
Think about it.
Is there a solution which is not to copy cpuwatch to /usr/local/cpanel/bin as this file already exists on all of our machines.
They appear to be constantly running stats in a loop all day long, meaning that the machine becomes overloaded and we receieve repeated warnings about such things as bandwidth usage on accounts.
It's causing some serious performance issues, only started happening with cpanel 6.
Anyone?
They appear to be constantly running stats in a loop all day long, meaning that the machine becomes overloaded and we receieve repeated warnings about such things as bandwidth usage on accounts.
It's causing some serious performance issues, only started happening with cpanel 6.
Anyone?
Crap, the problem just crept back on one of my servers yesterday (5.3b117). I just went to look at the files again, and found that cpuwatch was once again missing from the /usr/local/cpanel/bin directory.
I'd love to know how it got DELETED again! The file was still in the /src/wrap directory though, so I've just copied it from there. We'll see how long this sticks (we're planning on upgrading everything to 6.0 tonight).
Come on Nick, this is getting to be hassle.
Jaz
I'd love to know how it got DELETED again! The file was still in the /src/wrap directory though, so I've just copied it from there. We'll see how long this sticks (we're planning on upgrading everything to 6.0 tonight).
Come on Nick, this is getting to be hassle.
Jaz
This CPUWATCH bogus warning issue is way past getting old ... it's a major pain in the you-know-what.
None of the suggestions posted here have any effect of this problem.
WHM 6.0.0
Cpanel 6.0.0-S97
RedHat 7.3
... and multiple false warnings throughout the day.
I'm really pleased that cPanel is under active development and improvement ... just wish upgrades didn't break as many features as they fix, sigh.
None of the suggestions posted here have any effect of this problem.
WHM 6.0.0
Cpanel 6.0.0-S97
RedHat 7.3
... and multiple false warnings throughout the day.
I'm really pleased that cPanel is under active development and improvement ... just wish upgrades didn't break as many features as they fix, sigh.
