NetworkManager fails to bring up wired interface after resume

[Mark Reitblatt]

Binary package hint: network-manager

This seems to be different from the other n-m resume bugs (bug 45696 and bug 42257). n-m recognizes both of my interfaces, but fails on DHCP for the wired network. I suspend/resume the laptop w/ the cable in, and n-m tries frantically to get an address. The applet keeps stopping and restarting constantly. Killing and restarting NetworkManager seems to have no effect. If I just kill n-m and use dhclient, everything works fine.

[Mark Reitblatt (mark-reitblatt)]

The relevant section in syslog seems to be (repeats ad nauseaum) as follows (eth0 = wired interface):

Apr 3 22:36:33 mercury NetworkManager: <information>^IDeactivating device eth0.
Apr 3 22:36:33 mercury NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Apr 3 22:36:33 mercury NetworkManager: <information>^IWill activate connection 'eth0'.
Apr 3 22:36:33 mercury NetworkManager: <information>^IDevice eth0 activation scheduled...
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) started...
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Apr 3 22:36:34 mercury NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Apr 3 22:36:35 mercury NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Apr 3 22:36:35 mercury NetworkManager: <information>^ICouldn't send DHCP 'up' message because: name 'com.redhat.dhcp.OperationInProgress', message 'interface eth0 is being released. Please try again later.'.
Apr 3 22:36:35 mercury NetworkManager: <information>^IActivation (eth0) failure scheduled...
Apr 3 22:36:35 mercury NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Apr 3 22:36:35 mercury NetworkManager: <information>^IActivation (eth0) failed.

[Paulus (donmatteo)]

I have exactly the same symptoms (wired via-rhine based)

[Mark Reitblatt (mark-reitblatt)]

This seems to have been fixed in the latest update of NetworkManager. Be sure that you are fully updated at this point.

[Paulus (donmatteo)]

This is not fixed. I still get:

Apr 18 10:28:41 psyche NetworkManager: <information>^IActivation (eth0)
Beginning DHCP transaction.
Apr 18 10:28:41 psyche NetworkManager: <information>^ICouldn't send DHCP
'up' message because: name 'com.redhat.dhcp.OperationInProgress',
message 'interface eth0 is being released. Please try again later.'.
Apr 18 10:28:41 psyche NetworkManager: <information>^IActivation (eth0)
failure scheduled...

[Some Guy (liblambhome)]

I also continue to get this message. Exactly the same as given above.

[Erik Meitner (e.meitner)]

This has happened to me about 3 times in the last month.
ii network-manager 0.6.4-6ubuntu7 network management framework daemon
ii network-manager-gnome 0.6.4-6ubuntu7 network management framework (GNOME frontend

I've noticed that there are some defunct dhcp processes when this happens:
29020 ? 00:00:00 dhclient <defunct>
29927 ? 00:00:00 dhclient3
31366 ? 00:00:00 dhclient <defunct>

This usually helps:
  killall nm-applet
  sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher stop
  sudo /etc/dbus-1/event.d/25NetworkManager stop
  sudo /etc/dbus-1/event.d/25NetworkManager start
  sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher start
  nm-applet &

[Erik Meitner (e.meitner)]

I left something out in the fix above:

  killall nm-applet
  sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher stop
  sudo /etc/dbus-1/event.d/25NetworkManager stop
  sudo /etc/dbus-1/event.d/22dhcdbd restart
  sudo /etc/dbus-1/event.d/25NetworkManager start
  sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher start
  nm-applet &

[su99 (samsonsu)]

I see this too today with my ethernet connection eth0. I had to remove network manager and use the ubuntu network applet to configure the network (and it works well).

NetworkManager is a nice tool in terms of providing easy-to-use network management especially for WiFi roaming mode. But it is really unstable.