今天一同事報告Linux服務器上的crontab作業沒有運行，檢查/var/log/cron日志后發現下面錯誤信息
Jan 19 16:30:01 xxxx crond[31399]: Authentication token is no longer valid; new one required
Jan 19 16:30:01 xxxx crond[31400]: Authentication token is no longer valid; new one required
Jan 19 16:30:01 xxxx crond[31401]: Authentication token is no longer valid; new one required
Jan 19 16:30:01 xxxx crond[31398]: Authentication token is no longer valid; new one required
Jan 19 16:30:01 xxxx crond[31400]: CRON (oracle) ERROR: failed to open PAM security session: Success
Jan 19 16:30:01 xxxx crond[31400]: CRON (oracle) ERROR: cannot set security context
Jan 19 16:30:01 xxxx crond[31401]: CRON (oracle) ERROR: failed to open PAM security session: Success
Jan 19 16:30:01 xxxx crond[31401]: CRON (oracle) ERROR: cannot set security context
Jan 19 16:30:01 xxxx crond[31402]: Authentication token is no longer valid; new one required
Jan 19 16:30:01 xxxx crond[31398]: CRON (root) ERROR: failed to open PAM security session: Success
Jan 19 16:30:01 xxxx crond[31399]: CRON (oracle) ERROR: failed to open PAM security session: Success
Jan 19 16:30:01 xxxx crond[31402]: CRON (oracle) ERROR: failed to open PAM security session: Success
Jan 19 16:30:01 xxxx crond[31398]: CRON (root) ERROR: cannot set security context
Jan 19 16:30:01 xxxx crond[31399]: CRON (oracle) ERROR: cannot set security context
Jan 19 16:30:01 xxxx crond[31402]: CRON (oracle) ERROR: cannot set security context
Jan 19 16:35:01 xxxx crond[31431]: Authentication token is no longer valid; new one required
Jan 19 16:35:01 xxxx crond[31431]: CRON (oracle) ERROR: failed to open PAM security session: Success
Jan 19 16:35:01 xxxx crond[31431]: CRON (oracle) ERROR: cannot set security context
恰好出現問題前，我在這台服務器上用chage命令設置了root、oracle等賬號的密碼過期策略。導致該賬號oracle密碼過期（Password expires），所以出現"Authentication token is no longer valid; new one required"等這類錯誤信息。
解決方案：
1：用SecureCRT以oracle用戶登錄系統，修改賬號密碼后，這個權限認證問題立馬解決。
2：使用chage命令讓對應賬號密碼永不過期。當然一般不建議使用該策略解決問題。