Cron and PAM Issues: Difference between revisions

From Leo's Notes
This page was last edited on 24 February 2017, at 19:14.
m Text replacement - "<code>" to "{{code|"
m Text replacement - "</code>" to "}}"
Line 6: Line 6:
  You (root) are not allowed to access to (crontab) because of pam configuration.
  You (root) are not allowed to access to (crontab) because of pam configuration.


{{code|/var/log/secure</code> shows messages similar to:
{{code|/var/log/secure}} shows messages similar to:
  Jul 25 14:07:17 ws1 crontab: pam_access(crond:account): access denied for user `root' from `cron'
  Jul 25 14:07:17 ws1 crontab: pam_access(crond:account): access denied for user `root' from `cron'




To fix this issue, ensure that cron can be accessed by the user. In the case above, 'root' to 'cron'. Do this by editing {{code|/etc/security/access.conf</code> with the following line <em>at the top of the file:</em>
To fix this issue, ensure that cron can be accessed by the user. In the case above, 'root' to 'cron'. Do this by editing {{code|/etc/security/access.conf}} with the following line <em>at the top of the file:</em>
  + : root : cron crond
  + : root : cron crond



Revision as of 19:14, 24 February 2017

When you try editing cron, you get a message similar to:

root@ws1:/etc/pam.d# crontab -e

Permission denied
You (root) are not allowed to access to (crontab) because of pam configuration.

/var/log/secure shows messages similar to:

Jul 25 14:07:17 ws1 crontab: pam_access(crond:account): access denied for user `root' from `cron'


To fix this issue, ensure that cron can be accessed by the user. In the case above, 'root' to 'cron'. Do this by editing /etc/security/access.conf with the following line at the top of the file:

+ : root : cron crond

See Also