I checked, none of the accounts have expired, and their shells are correct. I think its safe to rule out expired accounts, root's cron jobs are failing to execute too.
On Sun, Jul 17, 2011 at 12:14 PM, Procaccini, Tony J. <[email protected]> wrote: > On Sat, 16 Jul 2011, Alexander Dalloz wrote: > >> Am 16.07.2011 21:05, schrieb David D: >>> Hello, >>> Our Oracle environment is running on a cluster of redhat boxes. Each >>> node is running Redhat 5, x86_64. We are having a problem with our >>> crontab tasks. No job seems to be running. Even root?s crontab jobs >>> fail to execute. When I look at /var/log/cron the following lines are >>> listed over and over: >>> >>> Jul 16 13:01:01 server1 crond[1632]: Bad item passed to pam_*_item() >>> Jul 16 13:01:01 server1 crond[1632]: CRON (root) ERROR: failed to >>> open PAM security session: Success >>> Jul 16 13:01:01 server1 crond[1632]: CRON (root) ERROR: cannot >>> set security context >> >> Did someone play with /etc/security/access.conf or is that still default? >> >> rpm -V pam >> >>> Any insight is appreciated! Thank you for your assistance. > > Check the user(s) you are running the crons as dont have either expired login > or incorrect shell also. > > Tony > > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list > _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
