On Sun, Jul 17, 2011 at 12:00 PM,  <[email protected]> wrote:
> Send rhelv5-list mailing list submissions to
>        [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://www.redhat.com/mailman/listinfo/rhelv5-list

> 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
>
> I can?t seem to isolate this issue.   Some other interesting points
> that may be related:
>
> *  SE Linux is disabled
> *  No cron.allow file exists.
> *  The cron.deny file is empty
> *  The installed cron packages are:
>
>    anacron.x86_64                            2.3-45.0.1.el5
>    crontabs.noarch                           1.10-8
>    vixie-cron.x86_64                         4:4.1-77.el5_4.1
>
> *  The installed pam packages are:
>
>    pam.i386                                  0.99.6.2-6.el5_5.2
>     installed
>    pam.x86_64                                0.99.6.2-6.el5_5.2
>     installed
>    pam_ccreds.i386                           3-5
>     installed
>    pam_ccreds.x86_64                         3-5
>     installed
>    pam_krb5.i386                             2.2.14-18.el5
>     installed
>    pam_krb5.x86_64                           2.2.14-18.el5
>     installed
>    pam_passwdqc.i386                         1.0.2-1.2.2
>     installed
>    pam_passwdqc.x86_64                       1.0.2-1.2.2
>     installed
>    pam_pkcs11.i386                           0.5.3-23
>     installed
>    pam_pkcs11.x86_64                         0.5.3-23
>     installed
>    pam_smb.i386                              1.1.7-7.2.1
>     installed
>    pam_smb.x86_64                            1.1.7-7.2.1
>     installed
>
> *  The contents of /etc/pam.d/cron is:
>    #
>    # The PAM configuration file for the cron daemon
>    #
>    #
>
>    auth       sufficient pam_env.so
>   auth       required   pam_rootok.so
>   auth       include    system-auth
>   account    required   pam_access.so
>   account    include    system-auth
>   session    required   pam_loginuid.so
>   session    include    system-auth
>   /etc/pam.d/crond (END)
>
> *  Around the time cron stopped working the following entries started
> appearing in /var/log/secure:
>    Jul  6 20:40:01 dbtc01 crond[15916]: pam_env(crond:setcred):
> pam_putenv: delete non-existent entry; . $AW_HOME/site/sosite
>    Jul  6 20:40:01 dbtc01 crond[15916]: pam_env(crond:setcred):
> pam_putenv: delete non-existent entry; . $AW_HOME/site/sosite
>
> Any insight is appreciated!  Thank you for your assistance.
>
> David
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 16 Jul 2011 22:23:45 +0200
> From: Alexander Dalloz <[email protected]>
> To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list"
>        <[email protected]>
> Subject: Re: [rhelv5-list] crontab jobs not running
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=windows-1252
>
> 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

Take a look at /var/log/secure also. It might tell you what pam is blocking.

Cheers,
Win

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to