Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The init script of ypbind starts before ypserv. If the same host is
the only available NIS server, ypbind is killed again, before
ypserv is started, what works without problem. This problem arises,
when for instance
* the host itself is the only available NIS server e.g. because
others are not available e.g. not (yet) up e.g. when all NIS
servers are booting at the same time
* the host should be the only NIS server for itself (standalone
configuration while nameservice data updates)
Version-Release number of selected component (if applicable):
ypbind-1.20.4-30.el6.x86_64
ypserv-2.19-26.el6.x86_64
How reproducible:
On a NIS server, only add the same host or localhost in
/etc/yp.conf and reboot. ypbind will fail to start (the init
script checks, whether the NIS service is bound and timeouts
after several attempts and kills ypbind), because ypserv is
not yet available. ypserv will happily start later.
Steps to Reproduce:
1. Set up a working NIS server, assume domain name "localdomain"
2. make this the first line in /etc/yp.conf: domain localdomain server localhost
3. reboot
Actual results:
NIS not bound, no nameservice data from NIS available
Expected results:
NIS is bound, the local ypserv is queried, nameservice data from NIS available
Additional info:
ypbind is started in /etc/rc5.d/S24ypbind ,
ypserv in /etc/rc5.d/S26ypserv . I changed that to
/etc/rc5.d/S25ypbind and /etc/rc5.d/S24ypserv and
it works for me, though i do not consider this a
clean solution. ypserv should start after network
i.e. S24 . ypbind should start after ypserv i.e. S25
but other programs started in S24 and S25 might already
need nameservice data from NIS, so everything in S24
should move up at least by 2 and all stuff above likewise.
Thanks for reporting, this bug is actually fixed by build ypserv-2.19-26.el6_4.1, which is already shipped in RHEL-6.4.z.
*** This bug has been marked as a duplicate of bug 1011507 ***