Red Hat Bugzilla – Bug 206140
crond dies shortly after an ldap-user edited his crontab
Last modified: 2007-11-30 17:07:10 EST
Description of problem:
crond dies silently after an ldap-user edited his crontab-file with the "crontab
-e" command and the job is executed for the first time.
Excerpt from the logfile /var/log/cron:
Sep 12 09:33:15 de-edit2 crontab: (tinfot) BEGIN EDIT (tinfot)
Sep 12 09:33:18 de-edit2 crontab: (tinfot) REPLACE (tinfot)
Sep 12 09:33:18 de-edit2 crontab: (tinfot) END EDIT (tinfot)
Sep 12 09:34:01 de-edit2 crond: nss_ldap: reconnecting to LDAP server...
Sep 12 09:34:02 de-edit2 crond: nss_ldap: reconnected to LDAP server after
Sep 12 09:34:02 de-edit2 crond: (tinfot) CMD
Sep 12 10:06:38 de-edit2 crond: (CRON) STARTUP (V5.0)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. setup ldap-login
2. login to your server
3. edit your cronjobs
4. wait, cron dies after first execution of the job
crond lives happily and executes the jobs as we tell him
Should be OK in RHEL-5, I'll propose it for next release RHEL-3.
Is there a workaround for this?
ie. work-around: stop crond, start nscd if not already running, start crond.
will there be an update in the near future? we don't want to use the nscd here.
This problem will be resolved in a future major release of Red Hat Enterprise
Linux. Red Hat does not currently plan to provide a resolution for this in a
Red Hat Enterprise Linux update for currently deployed systems.
So the issue exists, we know how to fix it but Red Hat is refusing to fix it for
a current, supported OS (RHEL-3)?
No problem. Given the recent news, I'm certain that if RH doesn't fix this
fairly major bug that Oracle would be happy to step up and provide support.
could you at least provide an SRPM and version where you fixed this so that
others can try to roll the fix into older versions?
It's already fixed in higher version.
SRPMs are on mirrors of RHEL-5/FC-5/FC-6.
I recommend you to use higher version of vixie-cron with new features (4:4.1-58+).
and please could you explain why you don't release an update for an supported OS