Saturday, April 21, 2018

Error: Authentication token is no longer valid

Symptom:

When we try to edit crontab via crontab -e
It was working before,however  it error  out recently.

 Authentication token is no longer valid; new one required
You (oracle) are not allowed to access to (crontab) because of pam configuration.

Solution:

 The linux user expires in OS. It prevents it to run crontab
  Use this command to check details
  chage  -l  <user>

  Use below to update the attribution of expire date
  chage <user>           ---  it is interactive

Another reason is about  /etc/security/access.conf
Need to allow user to access cron resource
i.e
+ : oracle : ALL

No comments:

Post a Comment