Hide Forgot
Description of problem: When booting a system whose DHCP server assigns a NIS domain and NIS server, ypbind does not come up correctly at boot time. This is possibly networkmanager related, possibly something else but I have to file it somewhere. There are similar bugs about, for example Version-Release number of selected component (if applicable): NetworkManager-0.9.4.0-1.git20120328.fc17.x86_64 ypbind-1.35-1.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. Set up a DHCP server to supply NIS information e.g. option nis-domain "electronghost.co.uk"; option nis-servers 172.31.66.254; 2. Set up a shiny new F17 alpha system, install ypbind, "systemctl enable ypbind.service". Reboot 3. Log in as root on a terminal and type "ypwhich" Actual results: ypwhich: Can't communicate with ypbind Expected results: ypserver.electronghost.co.uk Additional info: Restarting ypbind using "systemctl try-restart ypbind.service" brings up ypbind successfully. At which point "systemctl try-restart autofs.service" is necessary to get home directories but the problem is really with ypbind. After a while, when the DHCP lease renews, ypbind is broken again. I'll attach what looks like a relevant section of /var/log/messages
Created attachment 574932 [details] Section of /var/log/messages
Argh. Interrupted by giggling urchins while writing description. Meant to say that Bug 753586 seems similar but not convinced it's the same.
I'm seeing the exact same problem without DHCP. I have a NetworkManager managed static IP and my /var/log/messages is pretty much identical to Tim's. This is with Fedora 16 and I don't know if it was the latest NetworkManager updates or ypbind that did it. NetworkManager-gtk-0.9.4-2.git20120403.fc16.x86_64 NetworkManager-openvpn-0.9.0-1.fc16.x86_64 ypbind-1.35-1.fc16.x86_64 NetworkManager-pptp-0.9.0-1.fc16.x86_64 NetworkManager-gnome-0.9.4-2.git20120403.fc16.x86_64 NetworkManager-vpnc-0.9.0-1.fc16.x86_64 NetworkManager-0.9.4-2.git20120403.fc16.x86_64 NetworkManager-glib-0.9.4-2.git20120403.fc16.x86_64
Created attachment 580266 [details] /var/log/messages ypbind/NetworkManager entries for a static IP interface I'm attaching my /var/log/messages that looks alot like the original reporter's.
I've been using DHCP supplied NIS configuration for many years in every fresh Fedora release with no problems. After new system install, during firstboot, create NIS authentication, provide required information such as NIS domain name and server address just to make firstboot happy. DHCP client overrides /etc/yp.conf anyway. The only problem is that autofs is not included in default desktop set so it needs to be install manually and started (first time only).
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.