LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 08-23-2012, 04:16 AM   #1
Pizzicato
LQ Newbie
 
Registered: Aug 2012
Distribution: Scientific Linux 6 (RHEL6)
Posts: 9

Rep: Reputation: Disabled
Angry NetworkManager wierd beahaviour communicating with DHCP server


Hi!
I'm getting a little crazy with NetworkManager in one of my servers, Scientific Linux 6, by the way.

When I boot the server it logs many messages which are quite confusing to me, it looks like it's trying to configure my network interfaces, but sometimes it fails, maybe due to the DHCP server-clint communication (I configured the DHCP server in another machine and might have something wrong).

Because of the network errors I don't get the NFS shares mounted, and the NIS client exits with an error message. After the system is up, if I start manually ypbind, and mount the NFS shares, everything works correctly.

Please take a look at the boot time log messages:

Code:
Aug 21 13:12:52 node1 dbus: avc:  netlink poll: error 4
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)
Aug 21 13:17:35 node1 ntpd[1924]: synchronized to 192.168.1.1, stratum 2
Aug 21 13:17:34 node1 ntpd[1924]: time reset -0.365251 s
Aug 21 13:17:34 node1 ntpd[1924]: kernel time sync status change 2001
thanks!
 
Old 08-23-2012, 04:18 AM   #2
Pizzicato
LQ Newbie
 
Registered: Aug 2012
Distribution: Scientific Linux 6 (RHEL6)
Posts: 9

Original Poster
Rep: Reputation: Disabled
I'm trying to change the thread title, because I mispelled "weird", but i don't know how to do it, any help?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
dnsmasq as dhcp server on eth0 and networkmanager R03L Linux - Networking 31 04-13-2013 08:57 AM
NetworkManager connects to DHCP AP but dhclient doesn't krkhan Linux - Wireless Networking 1 01-08-2008 03:49 PM
config DNS w/NetworkManager, DHCP otoomet Linux - Networking 2 09-30-2007 07:58 AM
DHCP + VPN + XDM not communicating on FC2... so irritating! Matthematician Linux - Networking 0 10-05-2004 12:59 AM
Communicating to a proxy server biosx Linux - Networking 3 08-01-2002 05:05 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 03:55 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration