linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Adam T. Bowen" <adam.bowen@connectinternetsolutions.com>
To: Matthew Metzger <news@thinkdeeper.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: cron script won't run
Date: Tue, 26 Sep 2006 09:30:08 +0100	[thread overview]
Message-ID: <4518E510.2060201@connectinternetsolutions.com> (raw)
In-Reply-To: <efalsp$3oj$1@sea.gmane.org>

Hi,

Matthew Metzger wrote:
> I have a script that works great when I run it from the command line,
> but doesn't work at all when added to crontab. 

# cat /dev/sysadm/mantra
The environment from within cron is not necessarily the same as that of
an interactive shell.

> The strange part is that
> /var/log/cron shows the job running:
> 
> Sep 26 03:39:01 cono crond[25241]: (root) CMD
> (/etc/cron.3min/mail-restart.sh)
> 
> However, the log shows some other errors that may have something to do
> with it.
> 
> PAM adding faulty module: /lib/security/pam_krb5.so
> (root) CMD (/etc/cron.3min/mail-restart.sh)
> PAM unable to dlopen(/lib/security/pam_krb5.so)
> PAM [dlerror: /lib/security/pam_krb5.so: cannot open shared object file:
> No such file or directory]

Is the PAM Kerberos package installed on your system?  Does the file
/lib/security/pam_krb5.so actually exist?  Perhaps something in your
script is triggering authentication through Kerberos.  You could:

grep /etc/pam.d/* krb

to reveal any specific pam configurations that are trying to use
Kerberos.  I can't be of much more help I'm afraid.  Sticking a load of
echo statements into the mail-restart.sh script could reveal what line
in your script is causing the error.

Cheers

Adam

  parent reply	other threads:[~2006-09-26  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26  7:46 cron script won't run Matthew Metzger
2006-09-26  8:25 ` Matthew Metzger
2006-09-27 13:29   ` Matthew Metzger
2006-09-26  8:30 ` Adam T. Bowen [this message]
2006-09-26  9:05   ` Luca Ferrari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4518E510.2060201@connectinternetsolutions.com \
    --to=adam.bowen@connectinternetsolutions.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=news@thinkdeeper.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).