Patrol found that the job on a Linux server did not send the message as scheduled, after logging on to the server to find that the job did not execute, so check the crontab settings. The result is the following error:
[Email protected] ~]# crontab-l
Authentication token is no longer valid; New one required
you (Root) is not allowed to Access to (crontab) because of Pam configuration.
[Email protected] ~]#
Look at the/etc/pam.d/crond, after careful examination found that we set the password expiration policy, when the password expires, the job due to authorization is not enforced, this can refer to the Linux account password expiration will cause the crontab job can not be executed and Linux account password expiration security policy setting
[Email protected] ~]# More/etc/pam.d/crond
#
# The PAM configuration file for the cron daemon
#
#
# No PAM authentication called, Auth modules not needed
account required
account include    Password-auth
session required
session include    Password-auth
auth    &NBSP, include password-auth
You is required to change your password immediately (password aged)
last login:wed June 28 15:42:13 From xxx.xxx.xxx.xxx
changing password for root.
(current) UNIX Password:
You (root) is not allowed to access to (crontab) because of Pam configuration