<!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } -->
Cron error:
“Cron run failed”
“Attempting to re-run cron while it is still running.”
“Cron run exceeded time limit and was aborted.”
“Cron has been running for an hour and is most likely stuck.”
I got these horrible messages after I upgraded to D615 and caused possibly by my cavalier attitude to re-enabling all the modules.
I checked and re-booted my server, but this was OK as my other sites were working correctly.
I searched for a solution, and there is plenty out there in the field, so I have put all the solutions I found under one roof for other poor souls who may suffer the same stress that I did!
try disabling the modules and then try and run cron manually.
Using phpMyadmin in your database, try deleting in 'variable' cron_last and cron_semaphore.
They can take a bit of finding. Clear your cache. There are reports of this working.
In /modules/common.inc change
$semaphore=variable_get('cron_semaphore',FALSE);
to
$semaphore=FALSE; hopefully run cron with success, then revert the change
could be MySQL timing out... look in /etc/my.cnf and setting it to something that allows longer runs
the solution that worked for me. Go to settings.php add or change the line
ini_set(“max_execution_time”,XX); where XX is seconds... I put in 120, setting it to 0 means 'never timeout'.
I would welcome any other solutions... you never know!
Hope this is useful,
boz
other ideas
I had a few cron issues recently. I found that these two can help as a first off idea to try and reduce cron load:
1. Remove the Update Status from modules
2. Reduce the number of pages to index from search admin/settings/search
update status
your're right, i forgot to mention this is one of the initial moves i made.