Attachment 606359 Details for Bug 846767 – Using broadcast with 90s timeout specified in /etc/sysconfig/ypbind

Using broadcast with 90s timeout specified in /etc/sysconfig/ypbind

ypbind2.log (text/plain), 8.50 KB, created by Ray Mikkelson on 2012-08-22 18:00:37 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ray Mikkelson

Created: 2012-08-22 18:00:37 UTC

Size: 8.50 KB

patch

obsolete

>#
># REM: Boot started here...
># Using broadcast with 90s timeout specified in /etc/sysconfig/ypbind
>#
>Aug 21 18:19:14 myserver kernel: imklog 5.8.10, log source = /proc/kmsg started.
>Aug 21 18:19:14 myserver rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1478" x-info="http://www.rsyslog.com"] start
>Aug 21 18:19:14 myserver ypbind: Binding NIS service
>Aug 21 18:19:14 myserver kernel: [   32.796175] bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.2.1 (Dec 18, 2011)
>Aug 21 18:19:14 myserver kernel: [   32.796719] bnx2 0000:01:00.0: eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d6000000, IRQ 36, node addr d4:ae:52:67:ac:e6
>Aug 21 18:19:14 myserver kernel: [   32.797514] bnx2 0000:01:00.1: eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d8000000, IRQ 48, node addr d4:ae:52:67:ac:e8
>Aug 21 18:19:14 myserver kernel: [   32.798544] bnx2 0000:02:00.0: eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem da000000, IRQ 32, node addr d4:ae:52:67:ac:ea
>Aug 21 18:19:14 myserver kernel: [   32.799059] bnx2 0000:02:00.1: eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem dc000000, IRQ 42, node addr d4:ae:52:67:ac:ec
>Aug 21 18:19:14 myserver kernel: [   37.252892] bnx2 0000:01:00.0: em1: using MSIX
>Aug 21 18:19:14 myserver kernel: [   37.253836] ADDRCONF(NETDEV_UP): em1: link is not ready
>Aug 21 18:19:14 myserver kernel: [   37.360360] bnx2 0000:01:00.1: em2: using MSIX
>Aug 21 18:19:14 myserver kernel: [   37.361379] ADDRCONF(NETDEV_UP): em2: link is not ready
>Aug 21 18:19:14 myserver kernel: [   37.462163] bnx2 0000:02:00.0: em3: using MSIX
>Aug 21 18:19:14 myserver kernel: [   37.463078] ADDRCONF(NETDEV_UP): em3: link is not ready
>Aug 21 18:19:14 myserver kernel: [   37.564951] bnx2 0000:02:00.1: em4: using MSIX
>Aug 21 18:19:14 myserver kernel: [   37.565882] ADDRCONF(NETDEV_UP): em4: link is not ready
>Aug 21 18:19:16 myserver kernel: [   40.456102] bnx2 0000:01:00.0: em1: NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> (em1): carrier now ON (device state 20)
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> (em1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Auto-activating connection 'System em1'.
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) starting connection 'System em1'
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> (em1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
>Aug 21 18:19:16 myserver kernel: [   40.457081] ADDRCONF(NETDEV_CHANGE): em1: link becomes ready
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) scheduled...
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) started...
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 2 of 5 (Device Configure) scheduled...
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) complete.
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 2 of 5 (Device Configure) starting...
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> (em1): device state change: prepare -> config (reason 'none') [40 50 0]
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 2 of 5 (Device Configure) successful.
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) scheduled.
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 2 of 5 (Device Configure) complete.
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) started...
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> (em1): device state change: config -> ip-config (reason 'none') [50 70 0]
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Beginning DHCPv4 transaction (timeout in 45 seconds)
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> dhclient started with pid 1532
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) complete.
>Aug 21 18:19:16 myserver dhclient[1532]: Internet Systems Consortium DHCP Client 4.2.3-P2
>Aug 21 18:19:16 myserver dhclient[1532]: Copyright 2004-2012 Internet Systems Consortium.
>Aug 21 18:19:16 myserver dhclient[1532]: All rights reserved.
>Aug 21 18:19:16 myserver dhclient[1532]: For info, please visit https://www.isc.org/software/dhcp/
>Aug 21 18:19:16 myserver dhclient[1532]: 
>Aug 21 18:19:16 myserver NetworkManager[1125]: <info> (em1): DHCPv4 state changed nbi -> preinit
>Aug 21 18:19:16 myserver dhclient[1532]: Listening on LPF/em1/d4:ae:52:67:ac:e6
>Aug 21 18:19:16 myserver dhclient[1532]: Sending on   LPF/em1/d4:ae:52:67:ac:e6
>Aug 21 18:19:16 myserver dhclient[1532]: Sending on   Socket/fallback
>Aug 21 18:19:16 myserver dhclient[1532]: DHCPREQUEST on em1 to 255.255.255.255 port 67
>Aug 21 18:19:18 myserver avahi-daemon[1161]: Registering new address record for fe80::d6ae:52ff:fe67:ace6 on em1.*.
>Aug 21 18:19:21 myserver dhclient[1532]: DHCPREQUEST on em1 to 255.255.255.255 port 67
>Aug 21 18:19:32 myserver dhclient[1532]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 8
>Aug 21 18:19:40 myserver dhclient[1532]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 14
>Aug 21 18:19:54 myserver dhclient[1532]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 14
>Aug 21 18:19:54 myserver dhclient[1532]: DHCPREQUEST on em1 to 255.255.255.255 port 67
>Aug 21 18:19:54 myserver dhclient[1532]: DHCPOFFER from 192.168.1.12
>Aug 21 18:19:54 myserver dhclient[1532]: DHCPACK from 192.168.1.12
>Aug 21 18:19:54 myserver dhclient[1532]: bound to 192.168.1.66 -- renewal in 42285 seconds.
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info> (em1): DHCPv4 state changed preinit -> bound
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   address 192.168.1.66
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   prefix 24 (255.255.255.0)
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   gateway 192.168.1.234
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   hostname 'myserver.mydomain.com'
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   nameserver '192.168.1.12'
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   nameserver '192.168.1.36'
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   domain name 'mydomain.com'
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info>   NIS domain 'hs.domain'
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info> Activation (em1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
>Aug 21 18:19:54 myserver NetworkManager[1125]: <info> Activation (em1) Stage 5 of 5 (IPv4 Commit) started...
>Aug 21 18:19:54 myserver avahi-daemon[1161]: Joining mDNS multicast group on interface em1.IPv4 with address 192.168.1.66.
>Aug 21 18:19:54 myserver avahi-daemon[1161]: New relevant interface em1.IPv4 for mDNS.
>Aug 21 18:19:54 myserver avahi-daemon[1161]: Registering new address record for 192.168.1.66 on em1.IPv4.
>Aug 21 18:19:55 myserver NetworkManager[1125]: <info> (em1): device state change: ip-config -> activated (reason 'none') [70 100 0]
>Aug 21 18:19:55 myserver NetworkManager[1125]: <info> Policy set 'System em1' (em1) as default for IPv4 routing and DNS.
>Aug 21 18:19:55 myserver NetworkManager[1125]: <info> Activation (em1) successful, device activated.
>Aug 21 18:19:55 myserver NetworkManager[1125]: <info> Activation (em1) Stage 5 of 5 (IPv4 Commit) complete.
>Aug 21 18:19:55 myserver dbus[1176]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
>Aug 21 18:19:55 myserver dbus-daemon[1176]: dbus[1176]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
>Aug 21 18:20:08 myserver ypbind[1459]: broadcast: RPC: Timed out.
># 
># REM: NetworkManager fails activation
>#
>Aug 21 18:20:20 myserver dbus[1176]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
>Aug 21 18:20:20 myserver dbus-daemon[1176]: dbus[1176]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
>#
># REM: ypbind 90s timer expires
>#
>Aug 21 18:20:44 myserver systemd[1]: ypbind.service operation timed out. Stopping.
>Aug 21 18:20:44 myserver kernel: [  128.013233] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
>Aug 21 18:20:44 myserver systemd[1]: Unit ypbind.service entered failed state.

Actions: View

Attachments on bug 846767: 603065 | 603259 | 603410 | 605265 | 606358 | 606359 | 606394 | 606641 | 607346