Return
-
Title
How to troubleshoot cron and crontab failures. -
Description
How to troubleshoot cron and crontab failures. -
Resolution
1 - Crontab command will fail if it is run as user whose password is expired. PAM will not allow to run cronjob as user if the password of that user is expired.Run the following commands to check the AD user account:
/opt/quest/bin/vastool list user/opt/quest/bin/vastool user checkaccessThe account should be listed and the checkaccess should say allowed. If it says denied, check the access rules and check the account is not locked and the password is not expired.
2 - Check /var/log/cron for message3 - Crontab should have the sticky bit set. ls -l /usr/bin/crontab to check.
If it does not set the sticky bit on the crontab binary:chmod +s /usr/bin/crontab4 - Check the cron.allow file and the cron.deny file if they exist and ensure the rules are configured properly allowing access.
5 - Check the access.conf file if exist and ensure that the rules are configured correctly for access.
6 - Restart the crond daemon and then test again
If you are still having problems, open up a Service Request with support and include the above troubleshooting data along with the vas_snapshot.sh data and the error, cronjob information may be helpful as well.