Bug 738000
Summary: | NISDOMAIN key in /etc/sysconfig/network is not taken into account at boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Erwan ADAM <erwan.adam> |
Component: | ypbind | Assignee: | Honza Horak <hhorak> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | hhorak, kklic |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-09-19 06:52:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Erwan ADAM
2011-09-13 15:35:54 UTC
I'm not able to reproduce this failure. Can you, please, tell me what version of ypbind you have? (simply run "rpm -q ypbind") (Sorry for the delay. For other problems, I restarted on a fedora 15 updated.) My ypbind version is [adam@is210376 utils]$ rpm -q ypbind ypbind-1.32-8.fc15.1.x86_64 Concerning the bug I encounter, first of all, I apologize but I realized the ypbind service was not started at boot but was appearing as "dead" (I'm not very familiar with systemctl yet). Well, after enabling ypbind.service at boot, the bug remains. But it seems to be related to some other bugs in bugzilla (for instance https://bugzilla.redhat.com/show_bug.cgi?id=696629). It is like the network is not "fully" started when entering startup of ypbind. It leads to "Host name lookup failure" in /var/log/messages always followed by "Lost connection to D-Bus" errors. I solved my problems with the declaration of the ip address of the nis server in the /etc/hosts file ... and now everything works as expected (ypbind and autofs are ok). I think this bug can be marked as duplicate of 696629 which seems not solved for the moment. Best regards, E.A. Closing as a duplicate on reporter's suggestion. *** This bug has been marked as a duplicate of bug 696629 *** |