RE: crontab jobs not running




Hi all,
Please have a look at following threads, if they can solve your problem.

http://ubuntuforums.org/showthread.php?t=1054283
http://forums.opensuse.org/forums/english/get-technical-help-here/applications/448620-cron-job-not-running-because-pam.html


-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of David D
Sent: Monday, July 18, 2011 12:21 AM
To: General Red Hat Linux discussion list
Subject: Re: crontab jobs not running

I checked /etc/shadow, none of the accounts trying to run cron jobs
are disabled. Also, root's crontab's defined jobs are not running,
so I do not think the problem is an expired account.

David

On Sat, Jul 16, 2011 at 6:47 PM, Sanjay Chakraborty
<sanjaychakrab@xxxxxxxxx> wrote:
Most probably account expired.

On Sat, Jul 16, 2011 at 3:04 PM, David D <mystupidquestion@xxxxxxxxx> wrote:
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

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list




--
Regards.
Sanjay Chakraborty

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended
for the named recipient(s) only.
It shall not attach any liability on the originator or NECHCL or its
affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the
opinions of NECHCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of
this message without the prior written consent of the author of this e-mail is
strictly prohibited. If you have
received this email in error please delete it and notify the sender
immediately. .
-----------------------------------------------------------------------------------------------------------------------

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • Re: crontab jobs not running
    ... none of the accounts trying to run cron jobs ... open PAM security session: Success ...
    (RedHat)
  • Re: System mail (Fedora 20)
    ... as I tripped up on this once I got my old cron jobs transfered over to this install. ... Some cron config file is set to use sendmail for the MAILTO= option. ... Lars has pointed out that logwatch config is coded to use sendmail. ...
    (Fedora)
  • Re: daily cron jobs: setting time of day, how?
    ... > Which cron daemon are you running? ... > Vixie cron - this runs jobs at the scheduled hour. ... > anacron - runs jobs within a period ...
    (alt.os.linux.suse)
  • Re: centralized cron
    ... >>hundreds of servers, each with their own cron jobs set up, and would ... Using ssh to run crontab ... You're talking about a "job scheduling" software package. ...
    (comp.unix.admin)
  • Re: centralized cron
    ... >>hundreds of servers, each with their own cron jobs set up, and would ... Using ssh to run crontab ... You're talking about a "job scheduling" software package. ...
    (comp.unix.questions)