Re: F16: Broken ypbind
On 04/21/2012 08:38 AM, Terry Barnaby wrote: On 21/04/12 08:10, Terry Barnaby wrote: Some update appears to have broken the operation of ypbind recently. I have a F14 sever that serves /home and implements NIS services (ypserv) and has been running fine for over a year. The F16 clients use NetworkManager with wired Ethernet set to automatic/system connection. Everything comes up fine except for ypbind that fails. This has worked fine until a week or so ago (fails on multiple clients). The boot.log is enclosed, any ideas ? Cheers Terry Enclosed is a portion of /var/log/messages. The test.sh entries are a script executed from /lib/systemd/system/ypbind.service in the pre and post stages. It looks to me that systemd is starting a lot of network services including the NFS mounts and ypbind before the core network interface is up and running ... Is there a mechanism so that systemd will wait until the primary network is up before continuing ? I assumed that ybind waiting for network.target would have achieved that ? For information: You need to run: systemctl enable NetworkManager-wait-online.service This sets systemd to wait for the network to be up before generating network.target. Programs then need the network up, such as ypbind, now wait until the network is actually up. Why this is not the default I will never know. I guess most developers are using individual Laptops and not using servers with multiple clients :) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F16: Broken ypbind
On 21/04/12 08:10, Terry Barnaby wrote: Some update appears to have broken the operation of ypbind recently. I have a F14 sever that serves /home and implements NIS services (ypserv) and has been running fine for over a year. The F16 clients use NetworkManager with wired Ethernet set to automatic/system connection. Everything comes up fine except for ypbind that fails. This has worked fine until a week or so ago (fails on multiple clients). The boot.log is enclosed, any ideas ? Cheers Terry Enclosed is a portion of /var/log/messages. The test.sh entries are a script executed from /lib/systemd/system/ypbind.service in the pre and post stages. It looks to me that systemd is starting a lot of network services including the NFS mounts and ypbind before the core network interface is up and running ... Is there a mechanism so that systemd will wait until the primary network is up before continuing ? I assumed that ybind waiting for network.target would have achieved that ? Apr 21 09:17:55 study NetworkManager[696]:ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1 Apr 21 09:17:55 study NetworkManager[696]: info Loaded plugin ifcfg-rh: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Apr 21 09:17:55 study NetworkManager[696]: info Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Apr 21 09:17:55 study NetworkManager[696]:ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-Auto_Ethernet ... Apr 21 09:17:55 study NetworkManager[696]:ifcfg-rh: read connection 'New Wired Connection' Apr 21 09:17:55 study NetworkManager[696]:ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Apr 21 09:17:55 study NetworkManager[696]: info trying to start the modem manager... Apr 21 09:17:55 study dbus[744]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Apr 21 09:17:55 study dbus-daemon[744]: dbus[744]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Apr 21 09:17:56 study NetworkManager[696]: info monitoring kernel firmware directory '/lib/firmware'. Apr 21 09:17:56 study dbus-daemon[744]: dbus[744]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Apr 21 09:17:56 study dbus[744]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Apr 21 09:17:56 study dbus-daemon[744]: modem-manager[793]: info ModemManager (version 0.4.998-1.git20110706.fc16) starting... Apr 21 09:17:56 study modem-manager[793]: info ModemManager (version 0.4.998-1.git20110706.fc16) starting... Apr 21 09:17:56 study dbus[744]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Apr 21 09:17:56 study dbus-daemon[744]: dbus[744]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Apr 21 09:17:56 study iscsid: iSCSI logger with pid=799 started! Apr 21 09:17:56 study NetworkManager[696]: info WiFi enabled by radio killswitch; enabled by state file Apr 21 09:17:56 study NetworkManager[696]: info WWAN enabled by radio killswitch; enabled by state file Apr 21 09:17:56 study NetworkManager[696]: info WiMAX enabled by radio killswitch; enabled by state file Apr 21 09:17:56 study NetworkManager[696]: info Networking is enabled by state file Apr 21 09:17:56 study NetworkManager[696]: warn failed to allocate link cache: (-12) Netlink Error (errno = Operation not supported) Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): carrier is OFF Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): new Ethernet device (driver: 'r8169' ifindex: 2) Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): exported as /org/freedesktop/NetworkManager/Devices/0 Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): now managed Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): bringing up device. Apr 21 09:17:56 study kernel: [ 22.794871] r8169 :02:05.0: p3p1: link down Apr 21 09:17:56 study kernel: [ 22.794884] r8169 :02:05.0: p3p1: link down Apr 21 09:17:56 study dbus[744]: [system] Successfully activated service 'org.freedesktop.ModemManager' Apr 21 09:17:56 study dbus-daemon[744]: dbus[744]: [system] Successfully activated service 'org.freedesktop.ModemManager' Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): preparing device. Apr 21 09:17:56 study NetworkManager[696]: info (p3p1): deactivating device (reason 'managed') [2] Apr 21 09:17:56 study
Re: F16: Broken ypbind
Is it this bug: https://bugzilla.redhat.com/show_bug.cgi?id=812501 If yes, there is already an update in updates-testing which you could try. hth Johannes On 04/21/2012 08:10 AM, Terry Barnaby wrote: Some update appears to have broken the operation of ypbind recently. I have a F14 sever that serves /home and implements NIS services (ypserv) and has been running fine for over a year. The F16 clients use NetworkManager with wired Ethernet set to automatic/system connection. Everything comes up fine except for ypbind that fails. This has worked fine until a week or so ago (fails on multiple clients). The boot.log is enclosed, any ideas ? Cheers Terry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
