Fedora Linux Support Community & Resources Center

Home Forums Posting Rules Linux Help Fedora Set-Up Guides Ask Fedora Fedora Project
Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
Reload this Page NetworkManager: dhcp_watch_cb(): dhcp client died abnormally
FedoraForum Search
Forgot Password? Join Us!
Register All Albums FAQ Search Today's Posts Mark Forums Read

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 3rd December 2009, 03:22 AM
Dichi Al Faridi Offline
Registered User
  
Join Date: Mar 2009
Posts: 4
linuxsafari
NetworkManager: dhcp_watch_cb(): dhcp client died abnormally
Hello, I have some trouble with my NetworkManager. I use wireless connection on my laptop. Yes, NetworkManager can detect all available wireless connection. NetworkManager can make connection to them. But, I don't know why, NM looks like drop the IP. I do 'ifconfig', my wireless don't have IP at all.

This is my log :
Code:
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  (eth1): device state change: 4 -> 5 (reason 0)
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1/wireless): access point 'Auto WRC_OK' has security, but secrets are required.
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  (eth1): device state change: 5 -> 6 (reason 0)
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  (eth1): device state change: 6 -> 4 (reason 0)
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  (eth1): device state change: 4 -> 5 (reason 0)
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1/wireless): connection 'Auto WRC_OK' has security, and secrets exist.  No new secrets needed.
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Config: added 'ssid' value 'WRC_OK'
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE'
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN'
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Config: added 'wep_key0' value '<omitted>'
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Config: added 'wep_tx_keyidx' value '0'
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  Config: set interface ap_scan to 1
Dec  3 10:02:52 as-mbl01 NetworkManager: <info>  (eth1): supplicant connection state:  inactive -> scanning
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  (eth1): supplicant connection state:  scanning -> associating
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  (eth1): supplicant connection state:  associating -> associated
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  (eth1): supplicant connection state:  associated -> completed
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'WRC_OK'.
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  (eth1): device state change: 5 -> 7 (reason 0)
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1) Beginning DHCP transaction (timeout in 45 seconds)
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  dhclient started with pid 2941
Dec  3 10:02:57 as-mbl01 dhclient: Internet Systems Consortium DHCP Client 4.1.0p1
Dec  3 10:02:57 as-mbl01 dhclient: Copyright 2004-2009 Internet Systems Consortium.
Dec  3 10:02:57 as-mbl01 dhclient: All rights reserved.
Dec  3 10:02:57 as-mbl01 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Dec  3 10:02:57 as-mbl01 dhclient: 
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP6 Configure Get) scheduled...
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP6 Configure Get) started...
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP6 Configure Get) complete.
Dec  3 10:02:57 as-mbl01 NetworkManager: <info>  DHCP: device eth1 state changed (null) -> preinit
Dec  3 10:02:57 as-mbl01 dhclient: Listening on LPF/eth1/00:21:00:bc:5d:e7
Dec  3 10:02:57 as-mbl01 dhclient: Sending on   LPF/eth1/00:21:00:bc:5d:e7
Dec  3 10:02:57 as-mbl01 dhclient: Sending on   Socket/fallback
Dec  3 10:03:01 as-mbl01 dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Dec  3 10:03:05 as-mbl01 dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Dec  3 10:03:05 as-mbl01 dhclient: DHCPACK from 192.168.0.1
Dec  3 10:03:05 as-mbl01 dhclient: bound to 192.168.0.113 -- renewal in 337250 seconds.
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>  DHCP: device eth1 state changed preinit -> reboot
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP4 Configure Get) scheduled...
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP4 Configure Get) started...
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>    address 192.168.0.113
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>    prefix 24 (255.255.255.0)
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>    gateway 192.168.0.1
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>    nameserver '192.168.0.1'
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP4 Configure Get) complete.
Dec  3 10:03:05 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Dec  3 10:03:05 as-mbl01 avahi-daemon[1325]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.113.
Dec  3 10:03:05 as-mbl01 avahi-daemon[1325]: New relevant interface eth1.IPv4 for mDNS.
Dec  3 10:03:05 as-mbl01 avahi-daemon[1325]: Registering new address record for 192.168.0.113 on eth1.IPv4.
Dec  3 10:03:06 as-mbl01 NetworkManager: <WARN>  nm_named_manager_add_ip4_config(): Could not commit DNS changes.  Error: 'Could not replace /etc/resolv.conf: Operation not permitted#012'
Dec  3 10:03:06 as-mbl01 NetworkManager: <info>  (eth1): device state change: 7 -> 8 (reason 0)
Dec  3 10:03:06 as-mbl01 NetworkManager: <WARN>  nm_named_manager_add_ip4_config(): Could not commit DNS changes.  Error: 'Could not replace /etc/resolv.conf: Operation not permitted#012'
Dec  3 10:03:06 as-mbl01 NetworkManager: <info>  Policy set 'Auto WRC_OK' (eth1) as default for routing and DNS.
Dec  3 10:03:06 as-mbl01 NetworkManager: <info>  Activation (eth1) successful, device activated.
Dec  3 10:03:06 as-mbl01 NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Dec  3 10:03:06 as-mbl01 ntpd[1615]: Listening on interface #5 eth1, 192.168.0.113#123 Enabled
Dec  3 10:03:24 as-mbl01 dhclient: Internet Systems Consortium DHCP Client 4.1.0p1
Dec  3 10:03:24 as-mbl01 dhclient: Copyright 2004-2009 Internet Systems Consortium.
Dec  3 10:03:24 as-mbl01 dhclient: All rights reserved.
Dec  3 10:03:24 as-mbl01 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Dec  3 10:03:24 as-mbl01 dhclient: 
Dec  3 10:03:24 as-mbl01 NetworkManager: <WARN>  dhcp_watch_cb(): dhcp client died abnormally
Dec  3 10:03:24 as-mbl01 NetworkManager: <info>  (eth1): device state change: 8 -> 9 (reason 6)
Dec  3 10:03:24 as-mbl01 NetworkManager: <info>  Activation (eth1) failed for access point (WRC_OK)
Dec  3 10:03:24 as-mbl01 NetworkManager: <info>  Activation (eth1) failed.
Dec  3 10:03:24 as-mbl01 NetworkManager: <info>  (eth1): device state change: 9 -> 3 (reason 0)
Dec  3 10:03:24 as-mbl01 NetworkManager: <info>  (eth1): deactivating device (reason: 0).
Dec  3 10:03:24 as-mbl01 NetworkManager: <WARN>  check_one_route(): (eth1) error -34 returned from rtnl_route_del(): Sucess#012
Dec  3 10:03:24 as-mbl01 avahi-daemon[1325]: Withdrawing address record for 192.168.0.113 on eth1.
Dec  3 10:03:24 as-mbl01 avahi-daemon[1325]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.113.
Dec  3 10:03:24 as-mbl01 avahi-daemon[1325]: Interface eth1.IPv4 no longer relevant for mDNS.
Dec  3 10:03:24 as-mbl01 NetworkManager: <WARN>  nm_named_manager_remove_ip4_config(): Could not commit DNS changes.  Error: 'Could not replace /etc/resolv.conf: Operation not permitted#012'
Dec  3 10:03:24 as-mbl01 dhclient: Listening on LPF/eth1/00:21:00:bc:5d:e7
Dec  3 10:03:24 as-mbl01 dhclient: Sending on   LPF/eth1/00:21:00:bc:5d:e7
Dec  3 10:03:24 as-mbl01 dhclient: Sending on   Socket/fallback
Dec  3 10:03:24 as-mbl01 avahi-daemon[1325]: Withdrawing address record for fe80::221:ff:febc:5de7 on eth1.
Dec  3 10:03:25 as-mbl01 avahi-daemon[1325]: Registering new address record for fe80::221:ff:febc:5de7 on eth1.*.
Dec  3 10:03:26 as-mbl01 ntpd[1615]: Deleting interface #5 eth1, 192.168.0.113#123, interface stats: received=0, sent=0, dropped=0, active_time=20 secs
Note:
I was protect /etc/resolv.conf with chattr.

Thanks in advance.
Last edited by Dichi Al Faridi; 3rd December 2009 at 03:37 AM.
Reply With Quote
  #2  
Old 3rd December 2009, 04:28 AM
unamanic's Avatar
unamanic Offline
Registered User
  
Join Date: Apr 2006
Location: 127.0.0.1
Age: 33
Posts: 282
linuxfedorafirefox
i don't know why accept that perhaps dhcp is failing because it can't update DNS like it want to. You might try working with Network Manager instead of against it and add you DNS servers to its configuration instead of manually to resolve.conf. Essentially modify the connection using the nm-applet and change the IPv4 setting to DHCP Address only, and plug your DNS in the DNS field.

Link with screenshots:
http://unamanic.witt-family.net/2009...alternate-dns/
__________________
Currently Running: Fedora 15, openSUSE11.4
Reply With Quote
  #3  
Old 7th December 2009, 03:26 AM
lensman3 Offline
Registered User
  
Join Date: Dec 2009
Location: Centennial, Colorado USA
Posts: 128
linuxfedorafirefox
Look SELINUX is biting you. Again SELINUX is not ready for prime-time.

Dec 3 10:03:24 as-mbl01 NetworkManager: <WARN> nm_named_manager_remove_ip4_config(): Could not commit DNS changes. Error: 'Could not replace /etc/resolv.conf: Operation not permitted#012

Though this problem can be over ridden if FC11 using PEERDNS=no in /etc/sysconfig/network-scripts/ifcfg-ethx. The options is supposed to keep dhcp from slamming your providers DNS servers into resolv.conf
Reply With Quote
Reply

Tags
abnormally, client, dhcp, dhcpwatchcb, died, networkmanager

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

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 On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
NetworkManager Ad-Hoc DHCP Range picchioni Using Fedora 7 26th December 2008 08:21 AM
NetworkManager, DHCP and host-name ettlz Servers & Networking 4 29th February 2008 12:10 AM
NetworkManager and DHCP Hostname blinksilver Servers & Networking 0 23rd December 2005 09:10 AM
dhcp client not getting IP from dhcp server jkmartha Servers & Networking 2 17th June 2005 03:06 PM


Current GMT-time: 18:10 (Wednesday, 19-06-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.
Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

 FedoraForum is Powered by RedHat