Knowledge Base | Centova Cast v2 | Troubleshooting
Diagnosing cron job problems
My cron job is not running, or does not appear to be completing successfully. How can I diagnose this problem?
Please check the following in order:
Has your Centova Cast cron job been removed or altered? Login to your server via SSH as root and check /etc/crontab for the Centova Cast cron job. It should look something like the following:
*/5 * * * * centovacast /home/centovacast/system/runascc/runascc exec ccmanage cronjob all >/dev/null
The cron job is automatically set up by the installer, so if it does not exist then someone or something has removed it and you'll need to replace it.
Is your cron daemon actually running the cron job? Even if the Centova Cast cron job is correctly configured in /etc/crontab, other mistakes in your /etc/crontab file may cause the cron daemon to fail to run the cron job.
Check your cron log (usually /var/log/cron on Red Hat-based Linuxes) and search for the word "centovacast". Find the most recent entry (near the bottom), check the date stamp and make sure it has been running within the past hour.
Is your Centova Cast cron job working correctly? Try running the following command:
/home/centovacast/system/runascc/runascc exec ccmanage cronjob all --debug
Note that this may appear wordwrapped above, but should all be entered on one line. If any of the lines begin with "ERR", then there is a problem with your cron job which will need to be resolved.
If you see errors regarding cronjob.lck, this likely indicates that your setuid binaries in /home/centovacast/system/runascc/ have lost their setuid bits and/or are owned by the wrong account.
If you see an "Another cron job instance is already running" error, wait a few minutes and try again. If the problem persists, it's likely that a past cron job has frozen up for some reason. This can usually be fixed by logging in via SSH as root and running "killall -9 runascc". If the problem still persists, try deleting /home/centovacast/vhosts/cronjob.lck and try again.
If you have run all of the above tests and cannot determine the problem, please contact the support department and provide the output from the above two steps, and we will be pleased to assist.