Support Center > Search Results > SecureKnowledge Details
Cron Jobs stop running
Symptoms
  • after a while the cron job stops running
  • Get the following error in the /var/log/messages or /var/log/cron:
  • crond[4035]: Authentication token is no longer valid^ new one required
  • CRON (admin) ERROR: failed to open PAM security session: Success
  • CRON (admin) ERROR: cannot set security context
Cause

- running the command :  "chage -l admin"

Last password change : Nov 29, 2012
Password expires : Feb 27, 2013
Password inactive : never
Account expires : never
Minimum number of days between password change : 0
Maximum number of days between password change : 90
Number of days of warning before password expires : 7

- running ps -aux|grep crond, shows that the crond daemon runs under the admin account :

admin 2898 0.0 0.0 3192 1132 ? Ss Apr06 0:00 crond


Solution
Note: To view this solution you need to Sign In .