Excessive cron time causing 100% cpu and system hang

[MDHMatt]

For some reason the cron process is getting stuck and causing excessive usage warnings in cpanel

 

Time:         Mon Jul 24 09:01:52 2017 +0100
Account:      ****
Resource:     Process Time
Exceeded:     82008 > 1800 (seconds)
Executable:   /usr/local/cpanel/bin/jailshell
Command Line: jailshell (*****) [init] ell -c /usr/local/bin/php /home/******/public_html/*****/index.php cron >/dev/null 2>&1
PID:          27082 (Parent PID:27072)
Killed:       No

 

username  and site URL removed

 

running on proxmox kvm if it makes any difference 

[Blesta Addons]

this is the first time?

from screen it appear the cron is take more than 10h !!!!!! kill the proccess and watch the cpu again .

 

[MDHMatt]

It's happening over and over. This is since I've moved to version 4

once it happens it then stops other system tasks from running i.e. Backups do t start till it's finished. I've tried redoing the cron setup and if I force run from web it's fine. Just at some point it gets stuck?

[Paul]

Enable error reporting and debugging. Disable your cron, and try running it manually. Hopefully you'll be able to see where it's getting hung up. Do you have any custom or 3rd party extensions that register automation tasks?

[MDHMatt]

stupid question wheres the option to switch it on?

Other than it being hosted on a cPanel server (i have 'g'root) and couple of the blesta modules 

[Paul]

3 minutes ago, ginner159 said:

stupid question wheres the option to switch it on?

Other than it being hosted on a cPanel server (i have 'g'root) and couple of the blesta modules 

To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); You may also wish to enable System Debug. To do so, change Configure::set("System.debug", false); to Configure::set("System.debug", true);

If you are not running 4.0+, there is no System.debug. Switch both options back when done testing.