Red Hat Bugzilla – Bug 443409
ypbind always fails to bind at boot for me
Last modified: 2009-07-14 13:51:59 EDT
ypbind-1.20.4-4.fc9.x86_64, up to date F9 preview/rawhide system.
I have a single server specified by ip address, I have the firewall set to
disabled although by default, it has some iptables rules anyway (I'm
bugzilla'ing that since it makes broadcast ypbind not work), I have selinux in
permissive mode. Everytime I boot, ypbind fails to bind. I've had to add a
'service ypbind restart; sleep 15; service autofs reload' to my rc.local file
and then even after that, the automounts never get loaded until I log in as root
and reload them essentially a third time.
Are you using NetworkManager or the traditional network service?
I'm using NM with a static IP address. I've been testing with that as I thought
it was going to be the default.
It is -- I think that for some cases like this where the link takes a few
seconds to come up, the thought is to add NETWORKWAIT or NETWORKDELAY in
/etc/sysconfing/network. Adding notting and dcbw to the cc as I know I saw them
talking about it last week.
Adding NETWORKWAIT=yes to /etc/sysconfig/network should cause it to wait for the
network to be available.
I'll try that. Another bug that causes problems for ypbind is
https://bugzilla.redhat.com/show_bug.cgi?id=443411 where disabling the firewall
with system-config-firewall doesn't really disable it. It makes broadcast
When Bill says 'should cause it to wait for the network', which 'it' is he
referring to? ypbind? I added NETWORKWAIT=yes to /etc/sysconfig/network and
rebooted but the only change I saw was when NetworkManager started; it printed
something like 'waiting for network'. ypbind started (and failed) way before NM
started, 10 to 15 services earlier.
If you have a system that has/was installed from an earlier rawhide, you may
need to run, once updating:
/sbin/chkconfig haldaemon resetpriorities
/sbin/chkconfig NetworkManager resetpriorities
This system was installed last Friday with the preview release. I ran the resets
anyway and will try booting again after lunch.
Resetting the priorities fixed it for me. YP now starts after NM and everything
works as expected.
With NM and DHCP to get nis domain and nis servers it doesn't work : there is no
/etc/yp.conf created like /sbin/dhclient-script made
NB: same pb with hostname. Our machines get their hostname from DCHP; with NM
that doesn't work anymore
Must I open new cases for these pbs ?
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
I solved this pb using the script directive in /etc/dhclient-XXX.conf:
with /sbin/dhclient+nm-script :
But it would be fine if nm-dhcp-client.action make all the work...
NM doesn't recognize my wired network (e100 - intel 81801 BA/BAM/CA/CAM Rev 1).
nevertheless i get an ip from dhcp but ypbind refuses to connect. if i kill NM
and restart ypbind everything works fine.
Does anybody care about this bug or should it be closed as "wontfix, because I don't want to"?
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 '9'.
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 9'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 9 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.