Red Hat Bugzilla – Bug 64379
user cron job not running for users in LDAP directory
Last modified: 2007-04-18 12:42:24 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)
Description of problem:
User exists in LDAP directory. PAM/NSS_LDAP is installed and authconfig is
used to specify authentication/NSS via local LDAP server. User is not in
local /etc/passwd, but $ getent user <uid> shows users exists. Cron job for
user is added but cron fails to run job.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. crontab -u <uid> -e, create job to run every minute
2. write crontab
3. tail -f /var/log/cron
Actual Results: 1. observe the following messages in /var/log/cron
May 3 14:22:27 lattice crontab: (root) BEGIN EDIT (dtv)
May 3 14:22:47 lattice crontab: (root) REPLACE (dtv)
May 3 14:22:47 lattice crontab: (root) END EDIT (dtv)
May 3 14:23:00 lattice crond: (dtv) ORPHAN (no passwd entry)
2. job does not get run and is ignored.
Expected Results: May 3 14:24:00 lattice CROND: (dtv) CMD
The problem only manifests itself if nscd is run or restarted after crond. If
both crond and nscd are stopped, then nscd is started followed by crond, the
problem is not present.
ie. work-around: stop crond, start nscd if not already running, start crond.
It appears that crond wants to check the userpassword and can't find the
password field for the user, and nscd caches and supplies this information for
users in the LDAP directory.
Just clearing out old bugs here.
This bug is now fixed with current versions of cron and nss_ldap.
clearly it is _not_ yet fixed -- a change in the initscippts with a condrestart
might -- but manual intervention, and a deferral, still existing after four
years is not a fix
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
Please check if this issue is still present in a current Fedora Core
release. If so, please open a new issue against Fedora Core, and the correct
version. Thanks again for your help.