[hardy] networking and ifplugd services not started when booting or resuming

Bug #213937 reported by Robert
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
acpi-support
New
Undecided
Unassigned
pm-utils (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

I am not using NetworkManager to manage my network. Rather, I am using /etc/network/interfaces with ifplugd and guessnet to detect my network, bring it up with the appropriate settings and run scripts associated with each network (e.g. set printer queues, default Thunderbird profile, connect to shares, etc.)

This mostly worked in Gutsy.

In Hardy, the networking and ifplugd services to not start automatically when the system boots or resumes from suspend/hibernation, etc.

I need to manually run sudo /etc/init.d/networking start and sudo /etc/init.d/ifplugd start. (Usually when I boot, but not resume, the network comes up automatically; when I resume, I need to ifdown eth0 && ifup eth0.)

This may be due to my using Gnome Power Manager. I am investigating this.

Revision history for this message
Robert (robrwo) wrote :

Note that /etc/default/acpi-support has the following line:

  STOP_SERVICES="networking ifplugd"

but these services do not appear to be stopped when I suspend, nor restarted when I resume.

Revision history for this message
Robert (robrwo) wrote :

The init scripts appear to be set up as they should be (according to comments
in /etc/init.d/{ifplugd,networking} scripts):

 rc0.d/K59ifplugd -> ../init.d/ifplugd
 rc0.d/K60networking -> ../init.d/networking
 rc1.d/K59ifplugd -> ../init.d/ifplugd
 rc2.d/K59ifplugd -> ../init.d/ifplugd
 rc3.d/S41ifplugd -> ../init.d/ifplugd
 rc5.d/S41ifplugd -> ../init.d/ifplugd
 rc6.d/K59ifplugd -> ../init.d/ifplugd
 rc6.d/K60networking -> ../init.d/networking
 rcS.d/S40networking -> ../init.d/networking

I don't understand why they are not starting.

Revision history for this message
sefs (sefsinc) wrote :

I am experiencing a similar problem with serial monkey rt73 drivers.
On boot the hardware device is not starting and cannot be detected.

I have to wait until the system is fully booted. unplug the usb adapter, plug it back in and restart the network by cli to get the network adapter started.

What is up with that?

This is with rt73-cvs-daily-apr-25-2008

the one before that does not even work any more, although it worked in gutsy.

What is going on here fellas.

Revision history for this message
Robert (robrwo) wrote :

Looking at /var/log/syslog, it appears that ifplugd is being run for my network devices, but it's failing.
Right after the kernel startup (machinename and mac addresses changed):

Apr 28 21:18:26 machinename kernel: [ 2.732334] udev: renamed network interface eth1_rename to eth0
Apr 28 21:18:26 machinename ifplugd.agent[11836]: Invoking ifplugd for eth1
Apr 28 21:18:26 machinename ifplugd(eth1)[11910]: ifplugd 0.28 initializing.
Apr 28 21:18:26 machinename ifplugd(eth1)[11910]: Warning: Could not get interface address.
Apr 28 21:18:26 machinename kernel: [ 2.901159] ADDRCONF(NETDEV_UP): eth1: link is not ready
Apr 28 21:18:27 machinename ifplugd(eth1)[11910]: Using interface eth1/01:23:45:67:89:ac with driver <ipw2200> (version: 1.2.2kmprq)
Apr 28 21:18:27 machinename ifplugd(eth1)[11910]: Initialization complete, link beat not detected.
Apr 28 21:18:27 machinename dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 11256
Apr 28 21:18:27 machinename dhclient: killed old client process, removed PID file
Apr 28 21:18:27 machinename dhclient: Internet Systems Consortium DHCP Client V3.0.6
Apr 28 21:18:27 machinename dhclient: Copyright 2004-2007 Internet Systems Consortium.
Apr 28 21:18:27 machinename dhclient: All rights reserved.
Apr 28 21:18:27 machinename dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Apr 28 21:18:27 machinename dhclient:
Apr 28 21:18:27 machinename dhclient: Listening on LPF/eth0/01:23:45:67:89:ab
Apr 28 21:18:27 machinename dhclient: Sending on LPF/eth0/01:23:45:67:89:ab
Apr 28 21:18:27 machinename dhclient: Sending on Socket/fallback
Apr 28 21:18:27 machinename dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67
Apr 28 21:18:27 machinename dhclient: send_packet: Network is unreachable
Apr 28 21:18:27 machinename dhclient: send_packet: please consult README file regarding broadcast address.
Apr 28 21:18:27 machinename kernel: [ 3.324396] ADDRCONF(NETDEV_UP): eth0: link is not ready

Could this be a udev-related problem?

Revision history for this message
andbelo (andbelo) wrote :

I'm using NetworkManager and have the same problem: The network doesn't start and the reason seems to be because eth0 doesn't get the IP address. After I run either "sudo /etc/init.d/networking restart" or "sudo ifdown -a && sudo ifup -a" everything works fine. Part of the output is:

There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072

My network setup worked before in Gutsy.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Please convert to the new pm-utils infrastructure.

Changed in linux:
importance: Undecided → Wishlist
Revision history for this message
Paul (treepata) wrote :

Hi everyone,

I am experiencing the same problem on my IBM X40 running Xubuntu 8.10. I used to be able to fix the problem (under 7.4-8.4) using the STOP_SERVICES="networking" change in the ACPI file, but this no longer works in 8.10. The only way to re-establish network connection, is to restart the computer after hibernate or suspend.

Quite frustrating.

Revision history for this message
Jan (jankap) wrote :

I'm still having EXACTLY the same problem with 8.10, pm-utils and geforce 8200 chipset. Same Error - no IP and no video (but not necessary, because of server).

Can't find any solution. This is sooo incredibly annoying.

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Is this still an issue for you? Which Ubuntu version do you use? Thank you for telling us!

Changed in pm-utils (Ubuntu):
status: New → Incomplete
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Closing this bug. If you still experience this problem again, please reopen a new bug. Ubuntu 12.04 LTS is currently the long term supported Ubuntu version, you should test or supported versions above. Thank you!

Changed in pm-utils (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.