[SOLVED] ypbind not running due to NetworkManager error
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi!
I have a cluster to simulate physics experiments with and standard configuration with Scientific Linux 6 (RHEL 6):
- A master node which acts as the brain of the cluster and serves the rest of the nodes the basic services (DHCP, NIS, DNS, NTP) as well as controls the programs to execute parallelly. Its home directory is shared with the other nodes via NFS
- Some slave nodes which have the minimum config just to execute the programs provided by the master. Right now I only have one of the nodes working, until it's all set so I can clone its contents to the others.
- An storage server that shares via NFS a big partition
I have a weird problem when I boot the slave node, I think that ypbind is trying to get in contact with the NIS server in the master node before NetworkManager has set the network interfaces. This happens sometimes, but not always. I gues I'm doing something wrong, but I don't really know what.
Once the node has booted I can manually start ypbind and it works right away. After that I can mount the home directory served by the master node, as well as the data directory served by the storage server, with no problem.
Here is the output from /var/log/messages when booting, starting when NetworkManager begins configuring the network interfaces:
Code:
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> NetworkManager (version 0.8.1-9.el6_1.1) is starting...
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> trying to start the modem manager...
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> monitoring kernel firmware directory '/lib/firmware'.
Aug 21 13:12:52 node1 modem-manager: ModemManager (version 0.4.0-3.git20100628.el6) starting...
Aug 21 13:12:52 node1 NetworkManager[1523]: ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Aug 21 13:12:52 node1 NetworkManager[1523]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-Auto_em2 ...
Aug 21 13:12:52 node1 NetworkManager[1523]: ifcfg-rh: read connection 'Auto em2'
Aug 21 13:12:52 node1 NetworkManager[1523]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
Aug 21 13:12:52 node1 NetworkManager[1523]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-Auto_em1 ...
Aug 21 13:12:52 node1 NetworkManager[1523]: ifcfg-rh: read connection 'Auto em1'
Aug 21 13:12:52 node1 modem-manager: Loaded plugin MotoC
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Huawei
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Option
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Sierra
Aug 21 13:12:52 node1 modem-manager: Loaded plugin SimTech
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Longcheer
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Gobi
Aug 21 13:12:52 node1 modem-manager: Loaded plugin ZTE
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Novatel
Aug 21 13:12:52 node1 modem-manager: Loaded plugin AnyData
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Nokia
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Ericsson MBM
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Option High-Speed
Aug 21 13:12:52 node1 modem-manager: Loaded plugin Generic
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> WiFi enabled by radio killswitch; enabled by state file
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> WWAN enabled by radio killswitch; enabled by state file
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> WiMAX enabled by radio killswitch; enabled by state file
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> Networking is enabled by state file
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): carrier is OFF
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): new Ethernet device (driver: 'bnx2' ifindex: 2)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): exported as /org/freedesktop/NetworkManager/Devices/0
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): now managed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): device state change: 1 -> 2 (reason 2)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): bringing up device.
Aug 21 13:12:52 node1 kernel: bnx2 0000:01:00.0: em1: using MSIX
Aug 21 13:12:52 node1 kernel: ADDRCONF(NETDEV_UP): em1: link is not ready
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): preparing device.
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em1): deactivating device (reason: 2).
Aug 21 13:12:52 node1 lldpad[1432]: evb_ifdown:port em1 remove failed
Aug 21 13:12:52 node1 lldpad[1432]: vdp_ifdown:em1 vdp data remove failed
Aug 21 13:12:52 node1 lldpad[1432]: evb_ifdown:port em1 remove failed
Aug 21 13:12:52 node1 lldpad[1432]: vdp_ifdown:em1 vdp data remove failed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): carrier is OFF
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): new Ethernet device (driver: 'bnx2' ifindex: 3)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): exported as /org/freedesktop/NetworkManager/Devices/1
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): now managed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): device state change: 1 -> 2 (reason 2)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): bringing up device.
Aug 21 13:12:52 node1 kernel: bnx2 0000:01:00.1: em2: using MSIX
Aug 21 13:12:52 node1 kernel: ADDRCONF(NETDEV_UP): em2: link is not ready
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): preparing device.
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em2): deactivating device (reason: 2).
Aug 21 13:12:52 node1 lldpad[1432]: evb_ifdown:port em2 remove failed
Aug 21 13:12:52 node1 lldpad[1432]: vdp_ifdown:em2 vdp data remove failed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): carrier is OFF
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): new Ethernet device (driver: 'bnx2' ifindex: 4)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): exported as /org/freedesktop/NetworkManager/Devices/2
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): now managed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): device state change: 1 -> 2 (reason 2)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): bringing up device.
Aug 21 13:12:52 node1 kernel: bnx2 0000:02:00.0: em3: using MSIX
Aug 21 13:12:52 node1 kernel: ADDRCONF(NETDEV_UP): em3: link is not ready
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): preparing device.
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em3): deactivating device (reason: 2).
Aug 21 13:12:52 node1 lldpad[1432]: evb_ifdown:port em3 remove failed
Aug 21 13:12:52 node1 lldpad[1432]: vdp_ifdown:em3 vdp data remove failed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> Added default wired connection 'Auto em3' for /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0/net/em3
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): carrier is OFF
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): new Ethernet device (driver: 'bnx2' ifindex: 5)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): exported as /org/freedesktop/NetworkManager/Devices/3
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): now managed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): device state change: 1 -> 2 (reason 2)
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): bringing up device.
Aug 21 13:12:52 node1 kernel: bnx2 0000:02:00.1: em4: using MSIX
Aug 21 13:12:52 node1 kernel: ADDRCONF(NETDEV_UP): em4: link is not ready
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): preparing device.
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> (em4): deactivating device (reason: 2).
Aug 21 13:12:52 node1 lldpad[1432]: evb_ifdown:port em4 remove failed
Aug 21 13:12:52 node1 lldpad[1432]: vdp_ifdown:em4 vdp data remove failed
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> Added default wired connection 'Auto em4' for /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.1/net/em4
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> modem-manager is now available
Aug 21 13:12:52 node1 NetworkManager[1523]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Aug 21 13:12:52 node1 NetworkManager[1523]: <info> Trying to start the supplicant...
Aug 21 13:12:53 node1 lldpad[1432]: evb_ifdown:port em4 remove failed
Aug 21 13:12:53 node1 lldpad[1432]: vdp_ifdown:em4 vdp data remove failed
Aug 21 13:12:53 node1 lldpad[1432]: evb_ifdown:port em3 remove failed
Aug 21 13:12:53 node1 lldpad[1432]: vdp_ifdown:em3 vdp data remove failed
Aug 21 13:12:53 node1 lldpad[1432]: evb_ifdown:port em2 remove failed
Aug 21 13:12:53 node1 lldpad[1432]: vdp_ifdown:em2 vdp data remove failed
Aug 21 13:12:55 node1 kernel: bnx2 0000:01:00.1: em2: NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
Aug 21 13:12:55 node1 kernel: ADDRCONF(NETDEV_CHANGE): em2: link becomes ready
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em2): carrier now ON (device state 2)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em2): device state change: 2 -> 3 (reason 40)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) starting connection 'Auto em2'
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em2): device state change: 3 -> 4 (reason 0)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 1 of 5 (Device Prepare) scheduled...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 1 of 5 (Device Prepare) started...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 2 of 5 (Device Configure) scheduled...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 1 of 5 (Device Prepare) complete.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 2 of 5 (Device Configure) starting...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em2): device state change: 4 -> 5 (reason 0)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 2 of 5 (Device Configure) successful.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 2 of 5 (Device Configure) complete.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 3 of 5 (IP Configure Start) started...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em2): device state change: 5 -> 7 (reason 0)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Beginning DHCPv4 transaction (timeout in 45 seconds)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> dhclient started with pid 1530
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em2) Stage 3 of 5 (IP Configure Start) complete.
Aug 21 13:12:55 node1 dhclient[1530]: Internet Systems Consortium DHCP Client 4.1.1-P1
Aug 21 13:12:55 node1 dhclient[1530]: Copyright 2004-2010 Internet Systems Consortium.
Aug 21 13:12:55 node1 dhclient[1530]: All rights reserved.
Aug 21 13:12:55 node1 dhclient[1530]: For info, please visit https://www.isc.org/software/dhcp/
Aug 21 13:12:55 node1 dhclient[1530]:
Aug 21 13:12:55 node1 kernel: bnx2 0000:01:00.0: em1: NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em2): DHCPv4 state changed nbi -> preinit
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em1): carrier now ON (device state 2)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em1): device state change: 2 -> 3 (reason 40)
Aug 21 13:12:55 node1 lldpad[1432]: vdp_ifup(1343): port em2 not enabled for RxTx (0) !
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) starting connection 'Auto em1'
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em1): device state change: 3 -> 4 (reason 0)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) scheduled...
Aug 21 13:12:55 node1 kernel: ADDRCONF(NETDEV_CHANGE): em1: link becomes ready
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) started...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 2 of 5 (Device Configure) scheduled...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) complete.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 2 of 5 (Device Configure) starting...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em1): device state change: 4 -> 5 (reason 0)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 2 of 5 (Device Configure) successful.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 2 of 5 (Device Configure) complete.
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) started...
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em1): device state change: 5 -> 7 (reason 0)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> dhclient started with pid 1533
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) complete.
Aug 21 13:12:55 node1 dhclient[1533]: Internet Systems Consortium DHCP Client 4.1.1-P1
Aug 21 13:12:55 node1 dhclient[1533]: Copyright 2004-2010 Internet Systems Consortium.
Aug 21 13:12:55 node1 dhclient[1533]: All rights reserved.
Aug 21 13:12:55 node1 dhclient[1533]: For info, please visit https://www.isc.org/software/dhcp/
Aug 21 13:12:55 node1 dhclient[1533]:
Aug 21 13:12:55 node1 dhclient[1530]: Listening on LPF/em2/14:fe:b5:c7:1b:35
Aug 21 13:12:55 node1 dhclient[1530]: Sending on LPF/em2/14:fe:b5:c7:1b:35
Aug 21 13:12:55 node1 dhclient[1530]: Sending on Socket/fallback
Aug 21 13:12:55 node1 dhclient[1530]: DHCPREQUEST on em2 to 255.255.255.255 port 67 (xid=0x4e40893c)
Aug 21 13:12:55 node1 NetworkManager[1523]: <info> (em1): DHCPv4 state changed nbi -> preinit
Aug 21 13:12:55 node1 dhclient[1533]: Listening on LPF/em1/14:fe:b5:c7:1b:33
Aug 21 13:12:55 node1 dhclient[1533]: Sending on LPF/em1/14:fe:b5:c7:1b:33
Aug 21 13:12:55 node1 dhclient[1533]: Sending on Socket/fallback
Aug 21 13:12:55 node1 dhclient[1533]: DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x6faa06a3)
Aug 21 13:12:55 node1 lldpad[1432]: vdp_ifup(1343): port em1 not enabled for RxTx (0) !
Aug 21 13:12:56 node1 kernel: bnx2 0000:01:00.0: em1: NIC Copper Link is Down
Aug 21 13:12:56 node1 NetworkManager[1523]: <info> (em1): carrier now OFF (device state 7, deferring action for 4 seconds)
Aug 21 13:12:59 node1 kernel: bnx2 0000:01:00.0: em1: NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
Aug 21 13:12:59 node1 NetworkManager[1523]: <info> (em1): carrier now ON (device state 7)
Aug 21 13:12:59 node1 lldpad[1432]: vdp_ifup:em1 vdp data already exists !
Aug 21 13:13:01 node1 dhclient[1530]: DHCPREQUEST on em2 to 255.255.255.255 port 67 (xid=0x4e40893c)
Aug 21 13:13:02 node1 dhclient[1533]: DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x6faa06a3)
Aug 21 13:13:10 node1 dhclient[1530]: DHCPDISCOVER on em2 to 255.255.255.255 port 67 interval 8 (xid=0x7162ae8e)
Aug 21 13:13:18 node1 dhclient[1530]: DHCPDISCOVER on em2 to 255.255.255.255 port 67 interval 11 (xid=0x7162ae8e)
Aug 21 13:13:19 node1 dhclient[1533]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 3 (xid=0x67df65f5)
Aug 21 13:13:22 node1 dhclient[1533]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 5 (xid=0x67df65f5)
Aug 21 13:13:27 node1 dhclient[1533]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 12 (xid=0x67df65f5)
Aug 21 13:13:29 node1 dhclient[1530]: DHCPDISCOVER on em2 to 255.255.255.255 port 67 interval 11 (xid=0x7162ae8e)
Aug 21 13:13:29 node1 dhclient[1530]: DHCPOFFER from 192.168.2.1
Aug 21 13:13:29 node1 dhclient[1530]: DHCPREQUEST on em2 to 255.255.255.255 port 67 (xid=0x7162ae8e)
Aug 21 13:13:29 node1 dhclient[1530]: DHCPACK from 192.168.2.1 (xid=0x7162ae8e)
Aug 21 13:13:29 node1 dhclient[1530]: bound to 192.168.2.2 -- renewal in 39483 seconds.
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> (em2): DHCPv4 state changed preinit -> bound
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> Activation (em2) Stage 4 of 5 (IP4 Configure Get) scheduled...
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> Activation (em2) Stage 4 of 5 (IP4 Configure Get) started...
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> address 192.168.2.2
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> prefix 24 (255.255.255.0)
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> hostname 'node1-nfs'
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> nameserver '192.168.1.1'
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> domain name 'cluster.loc'
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> Activation (em2) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> Activation (em2) Stage 4 of 5 (IP4 Configure Get) complete.
Aug 21 13:13:29 node1 NetworkManager[1523]: <info> Activation (em2) Stage 5 of 5 (IP Configure Commit) started...
Aug 21 13:13:30 node1 NetworkManager[1523]: <info> (em2): device state change: 7 -> 8 (reason 0)
Aug 21 13:13:30 node1 NetworkManager[1523]: <info> Activation (em2) successful, device activated.
Aug 21 13:13:30 node1 NetworkManager[1523]: <info> Activation (em2) Stage 5 of 5 (IP Configure Commit) complete.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
Aug 21 13:13:30 node1 avahi-daemon[1549]: Successfully dropped root privileges.
Aug 21 13:13:30 node1 avahi-daemon[1549]: avahi-daemon 0.6.25 starting up.
Aug 21 13:13:30 node1 avahi-daemon[1549]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Aug 21 13:13:30 node1 avahi-daemon[1549]: Successfully called chroot().
Aug 21 13:13:30 node1 avahi-daemon[1549]: Successfully dropped remaining capabilities.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Loading service file /services/ssh.service.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Joining mDNS multicast group on interface em2.IPv4 with address 192.168.2.2.
Aug 21 13:13:30 node1 avahi-daemon[1549]: New relevant interface em2.IPv4 for mDNS.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Network interface enumeration completed.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Registering new address record for fe80::16fe:b5ff:fec7:1b35 on em2.*.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Registering new address record for 192.168.2.2 on em2.IPv4.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Registering new address record for fe80::16fe:b5ff:fec7:1b33 on em1.*.
Aug 21 13:13:30 node1 avahi-daemon[1549]: Registering HINFO record with values 'X86_64'/'LINUX'.
Aug 21 13:13:30 node1 rpc.statd[1581]: Version 1.2.3 starting
Aug 21 13:13:30 node1 sm-notify[1582]: Version 1.2.3 starting
Aug 21 13:13:30 node1 kernel: RPC: Registered udp transport module.
Aug 21 13:13:30 node1 kernel: RPC: Registered tcp transport module.
Aug 21 13:13:30 node1 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Aug 21 13:13:31 node1 avahi-daemon[1549]: Server startup complete. Host name is node1.local. Local service cookie is 484143104.
Aug 21 13:13:31 node1 acpid: starting up
Aug 21 13:13:31 node1 acpid: 1 rule loaded
Aug 21 13:13:31 node1 acpid: waiting for events: event logging is off
Aug 21 13:13:31 node1 acpid: client connected from 1735[68:68]
Aug 21 13:13:31 node1 acpid: 1 client rule loaded
Aug 21 13:13:31 node1 pcscd: pcscdaemon.c:506:main() pcsc-lite 1.5.2 daemon ready.
Aug 21 13:13:31 node1 setsebool: The allow_ypbind policy boolean was changed to 1 by root
Aug 21 13:13:31 node1 dbus: avc: received policyload notice (seqno=2)
Aug 21 13:13:31 node1 dbus: [system] Reloaded configuration
Aug 21 13:13:31 node1 ypbind: Host name lookup failure
Aug 21 13:13:31 node1 ypbind[1777]: Lost connection to D-Bus
Aug 21 13:13:31 node1 avahi-daemon[1549]: Service "node1" (/services/ssh.service) successfully established.
Aug 21 13:13:39 node1 dhclient[1533]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 12 (xid=0x67df65f5)
Aug 21 13:13:39 node1 dhclient[1533]: DHCPOFFER from 192.168.1.1
Aug 21 13:13:39 node1 dhclient[1533]: DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x67df65f5)
Aug 21 13:13:39 node1 dhclient[1533]: DHCPNAK from 192.168.2.1 (xid=0x67df65f5)
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> (em1): DHCPv4 state changed preinit -> expire
Aug 21 13:13:39 node1 dhclient[1533]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 5 (xid=0x67f6132f)
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> (em1): DHCPv4 state changed expire -> preinit
Aug 21 13:13:39 node1 dhclient[1533]: DHCPOFFER from 192.168.1.1
Aug 21 13:13:39 node1 dhclient[1533]: DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x67f6132f)
Aug 21 13:13:39 node1 dhclient[1533]: DHCPNAK from 192.168.2.1 (xid=0x67f6132f)
Aug 21 13:13:39 node1 dhclient[1533]: DHCPACK from 192.168.1.1 (xid=0x67f6132f)
Aug 21 13:13:39 node1 dhclient[1533]: bound to 192.168.1.2 -- renewal in 38555 seconds.
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> (em1): DHCPv4 state changed preinit -> bound
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> Activation (em1) Stage 4 of 5 (IP4 Configure Get) scheduled...
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> Activation (em1) Stage 4 of 5 (IP4 Configure Get) started...
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> address 192.168.1.2
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> prefix 24 (255.255.255.0)
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> hostname 'node1'
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> nameserver '192.168.1.1'
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> domain name 'cluster.loc'
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> Activation (em1) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> Activation (em1) Stage 4 of 5 (IP4 Configure Get) complete.
Aug 21 13:13:39 node1 NetworkManager[1523]: <info> Activation (em1) Stage 5 of 5 (IP Configure Commit) started...
Aug 21 13:13:39 node1 avahi-daemon[1549]: Joining mDNS multicast group on interface em1.IPv4 with address 192.168.1.2.
Aug 21 13:13:39 node1 avahi-daemon[1549]: New relevant interface em1.IPv4 for mDNS.
Aug 21 13:13:39 node1 avahi-daemon[1549]: Registering new address record for 192.168.1.2 on em1.IPv4.
Aug 21 13:13:40 node1 NetworkManager[1523]: <info> (em1): device state change: 7 -> 8 (reason 0)
Aug 21 13:13:40 node1 NetworkManager[1523]: <info> Activation (em1) successful, device activated.
Aug 21 13:13:40 node1 NetworkManager[1523]: <info> Activation (em1) Stage 5 of 5 (IP Configure Commit) complete.
Aug 21 13:14:17 node1 ypbind: NIS server for domain cluster.loc is not responding.
Aug 21 13:14:18 node1 ntpd[1923]: ntpd 4.2.4p8@1.1612-o Wed Nov 24 19:02:17 UTC 2010 (1)
Aug 21 13:14:18 node1 ntpd[1924]: precision = 0.142 usec
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #1 wildcard, ::#123 Disabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #2 lo, ::1#123 Enabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #3 em1, fe80::16fe:b5ff:fec7:1b33#123 Enabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #4 em2, fe80::16fe:b5ff:fec7:1b35#123 Enabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #5 lo, 127.0.0.1#123 Enabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #6 em1, 192.168.1.2#123 Enabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on interface #7 em2, 192.168.2.2#123 Enabled
Aug 21 13:14:18 node1 ntpd[1924]: Listening on routing socket on fd #24 for interface updates
Aug 21 13:14:18 node1 ntpd[1924]: kernel time sync status 2040
Aug 21 13:14:18 node1 ntpd[1924]: frequency initialized 88.333 PPM from /var/lib/ntp/drift
Aug 21 13:14:22 node1 polkitd[2244]: started daemon version 0.96 using authority implementation `local' version `0.96'
Aug 21 13:14:22 node1 rtkit-daemon[2255]: Sucessfully made thread 2253 of process 2253 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
Aug 21 13:14:22 node1 gdm-simple-greeter[2241]: Gtk-WARNING: gtkwidget.c:5460: widget not within a GtkWindow
Aug 21 13:14:22 node1 gdm-simple-greeter[2241]: WARNING: Unable to parse history: (null) 18#012
Aug 21 13:14:42 node1 NetworkManager[1523]: <error> [1345547682.483664] [nm-manager.c:1360] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Aug 21 13:14:42 node1 NetworkManager[1523]: <error> [1345547682.575622] [nm-manager.c:1360] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Aug 21 13:14:42 node1 pam: gdm-password[2281]: WARNING: unable to log session
Aug 21 13:14:43 node1 kernel: fuse init (API version 7.13)
1. you are running DHCP on cluster slave servers(!)? Why?
2. ditto modems?
3. ditto WiFi?
4. ditto gdm/gtk (ie desktop env) on slave; why?
Feel free to ignore, but that sounds just weird to me
A workaround for the moment would be to disable /etc/rc.d/rcX.d (i'd assume x=3 for a compute server) & add the startup call 'service ypbind start' (& anything else like nfs mounts) to /etc/rc.d/rc.local.
This is always the last startup file called
Hi chrism01!
Some of the messages that NetworkManager logs and I didn't understand are the ones about the modem and Wifi. I just asssumed that it was NetworkManager normal behavior, but you're right, I should disable that, do you know how to do it?
About the DHCP server, I'm not running one in the slave servers, just the client (dhclient) wich is executed by NetworkManager. Why do you think I have a DHCP server in the slave node?
About the desktop environment I'd rather have it running for console administration.
Thank you for your workaround suggestion, but before trying to fix it like that I'm going to check if increasing the ypbind timeout in its boot time script works. I'll let you know how it goes.
I've been checking the log I posted in the first entry more carefully. What I think that happens is that, for some reason, NetworManager instead of waiting until all the interfaces have had an IP assigned by the DHCP server, it lets the other boot scripts run. I set the variable NETWORKWAIT in /etc/sysconfig/network to avoid this. This is the content of /etc/sysconfig/network:
I've read somewhere that setting this variable only blocks startup for up to 10 second, but I'm not sure if this is right. Does anyone know if its possible to increase that time?
The main problem is that NetworkManager takes ages to finish, I don't know if that's related to a DHCP server or DNS server configuration problem.
What I should have said more clearly is why would you run DHCP at all on a compute cluster?
All the elements of a cluster count as servers in the conventional sense; you really need static IPs to know/control what's going on.
To be honest, a lot of people turn off NetworkManager; it just seems to cause issues generally.
I'd recommend using the normal network services instead.
Also, re other services, use the 'service' cmd http://linux.die.net/man/8/service to turn them off immediately and chkconfig http://linux.die.net/man/8/chkconfig to set them off permanently.
All the RHEL6 manuals here http://www.linuxtopia.org/online_boo...ion_index.html, inc 2 on Clusters
Hey!
I listened to chrism01 about the DHCP server, and you are quite right: It's much easier to have static IPs. The thing is that I initially configured a DNS and DHCP servers to provide dynamic DNS, so I could have network configuration (IP, DNS...) control of every slave from a single file. The thing is that this implies a pretty complicated setup, so I changed to static IP, getting rid of the DHCP and DNS servers which were giving me a bad headache, thanks!
I also disabled NetworkManager, and the network configuration at boot time is much more straightforward and fast now.
Anyways, these things didn't solve my problem, what did was changing the order of my NFS boot time scripts. I had the nfs scripts running before the ypbind scripts. Changing the order, so they where executed after the NIS scripts, solved the problem.
BTW, you can have static entries (keyed by mac addr) in a DHCP server, but you wouldn't normally for a 'static' group.
Its usually to protect a few key boxes in an otherwise desktop LAN.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
