Yes, the /etc/security/limits.conf file was modified for an account named oracle. The following was added. Several entries related to the core file size, maximun # of processes, and memory address space were added:
oracle soft nofile 131072 oracle hard nofile 131072 oracle soft nproc 131072 oracle hard nproc 131072 oracle soft core unlimited oracle hard core unlimited oracle soft memlock 50000000 oracle hard memlock 50000000 On Sat, Jul 16, 2011 at 4:23 PM, Alexander Dalloz <[email protected]> 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. >> >> David > > Alexander > > _______________________________________________ > 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
