Cron Job Been Excuting For Over 60 Minutes Warning?

[SOH Owner]

Hi I am getting a warning on my Blesta that a cron job been excuting for over 60 minutes, however there is no cron job currenting going nor error logs. What should I do about this? 

 

http://i.imgur.com/cyiTsMz.png the warning thing

 

And possibly the cron that is being excuted but not sure.. 

http://i.imgur.com/9m1LCYH.png 

 

The weirdest thing that nothing even happened today (no orders, tickets, and etc) so why is a cron job even stuck and it is really something wrong or just a "false" alarm?

[Michael]

A daily cron job is getting stuck, or it's a false alarm  best to check: https://licensecart.com/billing/plugin/support_manager/knowledgebase/view/24/cron-job-has-been-running-for-over-60-minutes-/10/

 

False alarm does happen we've had it a bit if you search the forum.

[Tyson]

Typically, a cron task that has been executing for over 60 minutes has actually stalled. This may be because an error occurred when attempting to process the task. As Licensecart mentioned in his link, a button will appear after some time that will allow you to reset the task. Otherwise, the task will be attempted again 6 hours later, automatically.

 

I would recommend updating your config setting to enable error reporting by updating /config/blesta.php and changing error reporting at the top of the page to:

Configure::errorReporting(-1);

Then clear the cronk task when the button appears next to it. Immediately afterward, run the cron manually from [settings] -> [system] -> [Automation]. The output of the cron should be displayed, along with any errors that may be encountered.

[SOH Owner]

Typically, a cron task that has been executing for over 60 minutes has actually stalled. This may be because an error occurred when attempting to process the task. As Licensecart mentioned in his link, a button will appear after some time that will allow you to reset the task. Otherwise, the task will be attempted again 6 hours later, automatically.

 

I would recommend updating your config setting to enable error reporting by updating /config/blesta.php and changing error reporting at the top of the page to:

Configure::errorReporting(-1);

Then clear the cronk task when the button appears next to it. Immediately afterward, run the cron manually from [settings] -> [system] -> [Automation]. The output of the cron should be displayed, along with any errors that may be encountered.

 

Thank you it was just had to be "reconfigured" in the end. For anyone with the problem, just un enable the setting save it, then re enable it and save that setting then it should "refresh" it thus stopping the "false" alarm.  

[Blesta Addons]

i have the same issue with cron , the stacked cron is the suspend cron . i have enabled the error login , deleted the task , re-run the cron manually , but the cron hs not been run again .

Attempting to run all tasks for XXXXX.
All tasks have been completed.
Attempting to run all system tasks.
All system tasks have been completed.

the cron setting show last run for Suspend Services 12:00:21 AM . is the same time i have set it to run !!!

 

now we have two days of services that has not suspended .

 

any road to go with it ?

[Paul]

i have the same issue with cron , the stacked cron is the suspend cron . i have enabled the error login , deleted the task , re-run the cron manually , but the cron hs not been run again .

Attempting to run all tasks for XXXXX.
All tasks have been completed.
Attempting to run all system tasks.
All system tasks have been completed.

the cron setting show last run for Suspend Services 12:00:21 AM . is the same time i have set it to run !!!

 

now we have two days of services that has not suspended .

 

any road to go with it ?

 

Most likely it is failing while making an API call through one of your modules for a service it is trying to suspend. You can check Tools > Logs > Module or Cron log to see if you can get additional information.

 

It may also be a good idea to try manually suspending some of those in Blesta. If you have trouble suspending them, then the cron would have trouble also. I would check the API URLs for each module, and make sure that the firewall is open for egress on those ports.

[Blesta Addons]

Most likely it is failing while making an API call through one of your modules for a service it is trying to suspend. You can check Tools > Logs > Module or Cron log to see if you can get additional information.

 

It may also be a good idea to try manually suspending some of those in Blesta. If you have trouble suspending them, then the cron would have trouble also. I would check the API URLs for each module, and make sure that the firewall is open for egress on those ports.

 

where i find wich services to try suspending them manually ?

[serge]

I think you should delete all log in db & apply a manual cron from blesta interface, this should make all restart fine.

 

As per the service question, I think Paul was meaning, it's about blesta service not being in the status they should (not yet updated from cron), like invoice paid but service not activated yet, etc.