Hi,

I received the message below:

IMPORTANT: Do not ignore this email.
This is cPanel stats runner on server.myhosting company.com!
While processing the log files for user root, the cpu has been
maxed out for more then a 6 hour period. The current load/uptime line on the server at the time of
this email is
5:30am up 5 days, 7:35, 0 users, load average: 1.22, 0.58, 0.25

What do you think I should do ?

Thank you for your help.

Catalin

SSH in run "top" see what is running if everything looks OK and you are happy with that load go to Tweak Settings in WHM and up the number where it suspends Log Rotation.

Catalin,

I have not experience that before but yesterday when stats was ran on my server, the CPU utilization went up to 112% or something but that was only for 10 minutes (at most).

I am not sure but it could be that either your log files are too large or it was processing at one of your server's busiest time.

Under WHM/Tweak Settings, you might want to set the 'Delete Each Domain Access Log after Stats is run' on so that you keep your log files small and probably run the stats manually in shell once through.

In SHELL, you can run /scripts/runweblogs and either the user name and have it process one at a time or manually run /scripts/runlogsnow , this will process all the log files.

By the way, how many clients are there on that machine ? and how old were the access log files kept to.

Hope that helps.

Thank you very much for the information.

I have app. 130 accounts on that server and frankly speaking I don't know how old my log files are (I'll check this). I think that I will have to delete the log files.

Thanks again.

Catalin

?? Why delete them.. Some customers might not like that too much.

Find out what is driving the loads up, it is not the log files doing it, the message is telling you it has suspended rotating log files because the load is at a higher point than you have told it to run logs at.

Either raise the point it can run logs at or find out why the load is staying above 1 and fix that, deleting logs is not going to solve the problem.