Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 606358 Details for
Bug 846767
ypbind fails on boot
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Log of ypbind failing at boot using broadcast
ypbind.log (text/plain), 8.13 KB, created by
Ray Mikkelson
on 2012-08-22 17:57:37 UTC
(
hide
)
Description:
Log of ypbind failing at boot using broadcast
Filename:
MIME Type:
Creator:
Ray Mikkelson
Created:
2012-08-22 17:57:37 UTC
Size:
8.13 KB
patch
obsolete
># ># REM: Boot starts here... ># Using broadcast with no /etc/sysconfig/ypbind file ># >Aug 20 17:42:55 myserver kernel: imklog 5.8.10, log source = /proc/kmsg started. >Aug 20 17:42:55 myserver rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1610" x-info="http://www.rsyslog.com"] start >Aug 20 17:42:55 myserver kernel: [ 32.506064] bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.2.1 (Dec 18, 2011) >Aug 20 17:42:55 myserver kernel: [ 32.509643] 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 20 17:42:55 myserver kernel: [ 32.513433] 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 20 17:42:55 myserver kernel: [ 32.522966] 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 20 17:42:55 myserver kernel: [ 32.533077] 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 20 17:42:55 myserver kernel: [ 32.783894] EDAC MC: Ver: 2.1.0 >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> (em1): carrier now ON (device state 20) >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> (em1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Auto-activating connection 'System em1'. >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) starting connection 'System em1' >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> (em1): device state change: disconnected -> prepare (reason 'none') [30 40 0] >Aug 20 17:42:57 myserver kernel: [ 40.383115] ADDRCONF(NETDEV_CHANGE): em1: link becomes ready >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) scheduled... >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) started... >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 2 of 5 (Device Configure) scheduled... >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) complete. >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 2 of 5 (Device Configure) starting... >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> (em1): device state change: prepare -> config (reason 'none') [40 50 0] >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 2 of 5 (Device Configure) successful. >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) scheduled. >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 2 of 5 (Device Configure) complete. >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) started... >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> (em1): device state change: config -> ip-config (reason 'none') [50 70 0] >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Beginning DHCPv4 transaction (timeout in 45 seconds) >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> dhclient started with pid 1665 >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) complete. >Aug 20 17:42:57 myserver dhclient[1665]: Internet Systems Consortium DHCP Client 4.2.3-P2 >Aug 20 17:42:57 myserver dhclient[1665]: Copyright 2004-2012 Internet Systems Consortium. >Aug 20 17:42:57 myserver dhclient[1665]: All rights reserved. >Aug 20 17:42:57 myserver dhclient[1665]: For info, please visit https://www.isc.org/software/dhcp/ >Aug 20 17:42:57 myserver dhclient[1665]: >Aug 20 17:42:57 myserver NetworkManager[1243]: <info> (em1): DHCPv4 state changed nbi -> preinit >Aug 20 17:42:57 myserver dhclient[1665]: Listening on LPF/em1/d4:ae:52:67:ac:e6 >Aug 20 17:42:57 myserver dhclient[1665]: Sending on LPF/em1/d4:ae:52:67:ac:e6 >Aug 20 17:42:57 myserver dhclient[1665]: Sending on Socket/fallback >Aug 20 17:42:57 myserver dhclient[1665]: DHCPREQUEST on em1 to 255.255.255.255 port 67 >Aug 20 17:42:59 myserver avahi-daemon[1279]: Registering new address record for fe80::d6ae:52ff:fe67:ace6 on em1.*. >Aug 20 17:43:02 myserver dhclient[1665]: DHCPREQUEST on em1 to 255.255.255.255 port 67 >Aug 20 17:43:16 myserver dhclient[1665]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 3 >Aug 20 17:43:19 myserver dhclient[1665]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 7 >Aug 20 17:43:27 myserver dhclient[1665]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 10 >Aug 20 17:43:37 myserver dhclient[1665]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 12 >Aug 20 17:43:37 myserver dhclient[1665]: DHCPREQUEST on em1 to 255.255.255.255 port 67 >Aug 20 17:43:37 myserver dhclient[1665]: DHCPOFFER from 192.168.1.12 >Aug 20 17:43:37 myserver dhclient[1665]: DHCPACK from 192.168.1.12 >Aug 20 17:43:37 myserver dhclient[1665]: bound to 192.168.1.66 -- renewal in 36952 seconds. >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> (em1): DHCPv4 state changed preinit -> bound >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> address 192.168.1.66 >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> prefix 24 (255.255.255.0) >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> gateway 192.168.1.234 >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> hostname 'myserver.mydomain.com' >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> nameserver '192.168.1.12' >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> nameserver '192.168.1.36' >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> domain name 'mydomain.com' >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> NIS domain 'hs.domain' >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> Activation (em1) Stage 5 of 5 (IPv4 Configure Commit) scheduled... >Aug 20 17:43:37 myserver NetworkManager[1243]: <info> Activation (em1) Stage 5 of 5 (IPv4 Commit) started... >Aug 20 17:43:37 myserver avahi-daemon[1279]: Joining mDNS multicast group on interface em1.IPv4 with address 192.168.1.66. >Aug 20 17:43:37 myserver avahi-daemon[1279]: New relevant interface em1.IPv4 for mDNS. >Aug 20 17:43:37 myserver avahi-daemon[1279]: Registering new address record for 192.168.1.66 on em1.IPv4. >Aug 20 17:43:38 myserver NetworkManager[1243]: <info> (em1): device state change: ip-config -> activated (reason 'none') [70 100 0] >Aug 20 17:43:38 myserver NetworkManager[1243]: <info> Policy set 'System em1' (em1) as default for IPv4 routing and DNS. >Aug 20 17:43:38 myserver NetworkManager[1243]: <info> Activation (em1) successful, device activated. >Aug 20 17:43:38 myserver NetworkManager[1243]: <info> Activation (em1) Stage 5 of 5 (IPv4 Commit) complete. >Aug 20 17:43:38 myserver dbus[1294]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) >Aug 20 17:43:38 myserver dbus-daemon[1294]: dbus[1294]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) ># ># REM: ypbind about to kill itself... ># >Aug 20 17:43:46 myserver ypbind: Binding took 51 seconds >Aug 20 17:43:46 myserver ypbind: NIS server for domain hs.domain is not responding. >Aug 20 17:43:46 myserver ypbind: Killing ypbind with PID 1586. >Aug 20 17:43:46 myserver ypbind-post-waitbind[1595]: /usr/lib/ypbind/ypbind-post-waitbind: line 51: kill: SIGTERM: invalid signal specification >Aug 20 17:43:46 myserver systemd[1]: ypbind.service: control process exited, code=exited status=1 >Aug 20 17:43:46 myserver dbus[1294]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' >Aug 20 17:43:46 myserver dbus-daemon[1294]: dbus[1294]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' ># ># REM: NetworkManager is finally up... ># >Aug 20 17:43:46 myserver kernel: [ 89.355014] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory >Aug 20 17:43:46 myserver kernel: [ 89.356210] NFSD: starting 90-second grace period >Aug 20 17:43:46 myserver systemd[1]: Unit ypbind.service entered failed state.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 846767
:
603065
|
603259
|
603410
|
605265
| 606358 |
606359
|
606394
|
606641
|
607346