Red Hat Bugzilla – Bug 1027016
User's cron entry error out with CROND ORPHAN (no passwd entry)
Last modified: 2013-11-06 06:46:43 EST
Description of problem:
When switching from one NIS domain to another the NIS user cronjobs become ophaned saying that there is (no passwd entry). The getent and id commands both accurately produce the user's information. A restart of the crond service is required to get the cronjobs working again.
Both NIS domains have the same information, the user was just moving the NIS master to a different datacenter.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Switching NIS domain binding from one NIS domain to another NIS domain
Steps to Reproduce:
1. Prepare two NIS servers in your test lab for a NIS client to switch in between.
2. Change the NIS domain binding
NIS user cronjobs do not run and produce the following errors for the NIS users
Oct 31 11:51:01 servername crond[####]: (username1) ORPHAN (no passwd entry)
Oct 31 11:51:01 servername crond[####]: (username2) ORPHAN (no passwd entry)
The cronjobs for the users keep working
*** This bug has been marked as a duplicate of bug 738232 ***