Network problems (wired and wireless) after upgrading to Feisty

Asked by Suraj Acharya

After upgrading to Feisty I've run into this problem where the network manager applet is constantly rotating with one green light. It does this even when trying to connect to my wired network. However I can still connect to the internet. Network-manager seems to reset the connection very frequently though, this is not an issue when connected to the wired network, but it asks me for the wireless password every minute or so.

Here's a snippet from my /var/log/syslog:

Apr 25 14:18:30 sacharya-laptop NetworkManager: <information>^IDevice 'eth0' DHCP transaction took too long (>99s), stopping it.
Apr 25 14:18:30 sacharya-laptop dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 11048
Apr 25 14:18:30 sacharya-laptop dhclient: killed old client process, removed PID file
Apr 25 14:18:30 sacharya-laptop dhclient: DHCPRELEASE on eth0 to 192.168.42.1 port 67
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IDHCP daemon state is now 14 (normal exit) for interface eth0
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IDHCP daemon state is now 14 (normal exit) for interface eth0
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) started...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^INo DHCP reply received. Automatically obtaining IP via Zeroconf.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) failure scheduled...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) failed.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IDeactivating device eth0.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Apr 25 14:18:31 sacharya-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IWill activate connection 'eth0'.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IDevice eth0 activation scheduled...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) started...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Apr 25 14:18:31 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Apr 25 14:18:32 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Apr 25 14:18:32 sacharya-laptop dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134993440
Apr 25 14:18:32 sacharya-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Apr 25 14:18:32 sacharya-laptop NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0
Apr 25 14:18:34 sacharya-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Apr 25 14:18:34 sacharya-laptop dhclient: DHCPOFFER from 192.168.42.1
Apr 25 14:18:34 sacharya-laptop dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Apr 25 14:18:35 sacharya-laptop dhclient: DHCPACK from 192.168.42.1
Apr 25 14:18:35 sacharya-laptop dhclient: bound to 192.168.42.104 -- renewal in 39006 seconds.
Apr 25 14:18:58 sacharya-laptop NetworkManager: <information>^IOld device 'eth0' activating, won't change.
Apr 25 14:20:11 sacharya-laptop NetworkManager: <information>^IDevice 'eth0' DHCP transaction took too long (>99s), stopping it.
Apr 25 14:20:11 sacharya-laptop dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 11140
Apr 25 14:20:11 sacharya-laptop dhclient: killed old client process, removed PID file
Apr 25 14:20:11 sacharya-laptop dhclient: DHCPRELEASE on eth0 to 192.168.42.1 port 67

This cycle of the the dhcp transaction timeing out continues forever. However, as I said earlier, I can connect to the network while this is happening.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Suraj Acharya
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Ralph Janke (txwikinger) said :
#1

Thanks for your question.

Could you please run

ps -edf | grep dhclient

and post the output here.

Thanks

Revision history for this message
Suraj Acharya (sacharya) said :
#2

sacharya@sacharya-laptop:~$ ps -edf | grep dhclient
dhcp 8736 1 0 13:38 ? 00:00:00 dhclient3 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1
dhcp 8794 4468 0 13:38 ? 00:00:00 /sbin/dhclient -1 -lf /var/lib/dhcp3/dhclient.eth0.leases -pf /var/run/dhclient.eth0.pid -q -e dhc_dbus=31 -d eth0
dhcp 20450 4468 0 17:05 ? 00:00:00 /sbin/dhclient -1 -lf /var/lib/dhcp3/dhclient.eth0.leases -pf /var/run/dhclient.eth0.pid -q -e dhc_dbus=31 -d eth0
sacharya 20486 10173 0 17:05 pts/1 00:00:00 grep dhclient

Revision history for this message
Ralph Janke (txwikinger) said :
#3

You have somehow multiple dhcp processes on the eth0 interface running. I would kill all of them and then restart the network with

sudo /etc/init.d/networking restart.

I hope this helps.

Revision history for this message
Suraj Acharya (sacharya) said :
#4

I tried killing the processes, but network manager seemed to spawn a dhclient process right away. So I killed NetworkManagerDispatcher and NetworkManager, then the dhclient processes. and then ran "sudo /etc/init.d/networking restart" and started the networkmanager processes. Still no luck, the behaviour looks the same to me.

Revision history for this message
Ralph Janke (txwikinger) said :
#5

Could you please run this command

dpkg-query -l 'dhcp*'

and post the output that we can see which dhcp package is installed.

Thanks

Revision history for this message
Suraj Acharya (sacharya) said :
#6

$ dpkg-query -l 'dhcp*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version
 Description
+++-=================================-=================================-==================================================================================
un dhcp-client <none>
 (no description available)
ii dhcp3-client 3.0.4-12ubuntu4
 DHCP Client
ii dhcp3-common 3.0.4-12ubuntu4
 Common files used by all the dhcp3* packages

On 4/26/07, txwikinger <email address hidden> wrote:
> Your question #5663 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/5663
>
> Status: Open => Needs information
>
> txwikinger requested for more information:
> Could you please run this command
>
> dpkg-query -l 'dhcp*'
>
> and post the output that we can see which dhcp package is installed.
>
> Thanks
>
> _______________________________________________________________________
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/5663
>

Revision history for this message
Suraj Acharya (sacharya) said :
#7

$ dpkg-query -l "dbus*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================-=================================-==================================================================================
ii dbus 1.0.2-1ubuntu3 simple interprocess messaging system
un dbus-1 <none> (no description available)
ii dbus-1-utils 1.0.2-1ubuntu3 simple interprocess messaging system (utilities)

$ dpkg-query -l "dbus*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================-=================================-==================================================================================
ii dbus 1.0.2-1ubuntu3 simple interprocess messaging system
un dbus-1 <none> (no description available)
ii dbus-1-utils 1.0.2-1ubuntu3 simple interprocess messaging system (utilities)

Synaptic doesn't seem to think that there are older versions of these packages around, or I'd try to go back to an earlier version to see if that fixes anything.

Revision history for this message
Suraj Acharya (sacharya) said :
#8

$ dpkg-query -l "dbus*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================-=================================-==================================================================================
ii dbus 1.0.2-1ubuntu3 simple interprocess messaging system
un dbus-1 <none> (no description available)
ii dbus-1-utils 1.0.2-1ubuntu3 simple interprocess messaging system (utilities)

$ dpkg-query -l "dbus*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================-=================================-==================================================================================
ii dbus 1.0.2-1ubuntu3 simple interprocess messaging system
un dbus-1 <none> (no description available)
ii dbus-1-utils 1.0.2-1ubuntu3 simple interprocess messaging system (utilities)

Synaptic doesn't seem to think that there are older versions of these packages around, or I'd try to go back to an earlier version to see if that fixes anything.

Revision history for this message
Best Suraj Acharya (sacharya) said :
#9

Turned out to be some scripts in the whereami package that were still around after its uninstalltion. Here's what fixed my problem:

sudo dpkg --purge whereami

This page helped me resolve the issue:
http://ubuntuforums.org/archive/index.php/t-259435.html