[Gutsy] Loop for network-manager fills syslog

Bug #121652 reported by jerrylamos
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Gutsy 20070621 CD/Live on IBM NetVista A30p 2gHz P4, 82801DB PRO/VE (LOM) ethernet controller booted up quiet, splash got "Error starting Gnome settings ..." all that was on the brown screen was Applications, Places, System. Ctrl-Alt-F1 worked but keyboard dead. Note this system has installed 20070606 Ubuntu, Xubuntu, Kubuntu running O.K. considering some Alpha and left over Feisty problems.

Rebooted without quiet, splash came up with same "Error starting Gnome settings .... reply not recieved" but it at least filled in the rest of the desktop and runs Firefox as I type.

I will try to attach /var/log/syslog which is filled with seemingly hundreds of lines from Network Manager trying to activate "eth2" and then "deactivating eth2" then activate eth2 in a tight loop. I didn't even know I had an eth2. There isn't any place to plug one in to as far as I can see.

Cheers, Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

Trying to attach /var/log/syslog. First attempt Firefox crashed.

Revision history for this message
jerrylamos (jerrylamos) wrote :
Download full text (6.1 KiB)

Gutsy Tribe 2 same problem. On a 1.2 MHz computer, syslog is 36 KBytes. On this IBM Net Vista, it' 3.6 Mega Bytes, with over 3 megabytes of that with endless repetitions of:

Jun 28 21:32:55 ubuntu NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Jun 28 21:32:55 ubuntu NetworkManager: <WARN> nm_dhcp_manager_get_state_for_device(): dhcdbd not running!
Jun 28 21:32:55 ubuntu NetworkManager: <info> Will activate connection 'eth0'.
Jun 28 21:32:55 ubuntu NetworkManager: <info> Device eth0 activation scheduled...
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) started...
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 28 21:32:55 ubuntu NetworkManager: <WARN> nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) failure scheduled...
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 28 21:32:55 ubuntu NetworkManager: <info> Activation (eth0) failed.
Jun 28 21:32:55 ubuntu NetworkManager: <info> Deactivating device eth0.
Jun 28 21:32:55 ubuntu NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.

then loop to first line hundreds and thousands of times.

On the last loop it does:

Jun 28 21:33:16 ubuntu NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Jun 28 21:33:18 ubuntu hcid[11988]: Bluetooth HCI daemon
Jun 28 21:33:18 ubuntu kernel: [ 165.262878] Bluetooth: Core ver 2.11
Jun 28 21:33:18 ubuntu kernel: [ 165.262969] NET: Registered protocol family 31
Jun 28 21:33:18 ubuntu kernel: [ 165.262972] Bluetooth: HCI device and connection manager initialized
Jun 28 21:33:18 ubuntu kernel: [ 165.262977] Bluetooth: HCI socket layer initialized
Jun 28 21:33:18 ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jun 28 21:33:18 ubuntu NetworkManager: <info> Will activate connection 'eth0'.
Jun 28 21:33:18 ubuntu NetworkManager: <info> Device eth0 activation scheduled...
Jun 28 21:33:18 ubuntu NetworkManager: <info> Activation (eth0) started...
Jun 28 21:33:18 ubuntu NetworkManager: <inf...

Read more...

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in network-manager.

Revision history for this message
Foppe Benedictus (foppe-benedictus) wrote :

As of today I looked into my syslog and found that the loop is still in Gutsy. A syslog file of my startup alone is about 2,7 Mb big. Of which more than 90% is this loop. I will attach my loop, but it is pretty much the same as described above by jerrylamos. In the same file is also the end of the loop where network-manager finaly seems to get its needed data.

Changed in network-manager:
status: New → Confirmed
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.