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.
Cause:
localhost not defined in domains causing need of the network when using it.
Consequence:
ypbind does not bind to ypserv on localhost when network is off
Fix:
Added check for localhost
Result:
ypbind works even if network is off
DescriptionKonstantin Olchanski
2012-06-06 21:22:07 UTC
ypbind does not bind to ypserv on localhost (same machine) if NetworkManager thinks that the network is off. This is surprising behaviour. One solution is use "ypbind -no-dbus", then ypbind binds to local ypserv correctly and NIS works as expected. Perhaps this should be the default configuration, matching the traditional UNIX behaviour of NIS tools.
ypbind-1.20.4-29.el6.x86_64
K.O.
Created attachment 597046[details]
patch consulted with upstream
With this patch ypbind won't go offline when one of the servers is localhost.
Comment 3Konstantin Olchanski
2012-07-09 17:48:42 UTC
I happened to look at the patch. The check is for IP address 127.0.0.1, correct for typical use, but remember than all 127.x.y.z IP addresses are localhost. K.O.
Created attachment 597245[details]
patch consulted with upstream
(In reply to comment #3)
> I happened to look at the patch. The check is for IP address 127.0.0.1,
> correct for typical use, but remember than all 127.x.y.z IP addresses are
> localhost. K.O.
Thanks for pointing to that, enhanced patch is attached.
Comment 5RHEL Program Management
2013-10-14 00:37:20 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
How to reproduce:
1. configure ypbind to bind to localhost
2. turn off all networks in NetworkManager except localhost
3. service ypbind start
4. echo $?
Actual results:
1
ypbind doesn't work
Expected results:
0
ypbind works
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-1332.html