[Bug 522819] Re: Loosing connections with "Connection reset by peer" message

GregoryHuey ghlaunchpad_ubuntubugs at cosmology.name
Wed Feb 17 00:15:50 GMT 2010


I have more info to add.
This bug seems to involve wpa_supplicant. I have wpa_supplicant version 0.6.9-3ubuntu1 installed on the Ubuntu box in question. Internet traffic is over wired ethernet (eth0). ifconfig eth0 and route -n both report what one expects. However, I noticed wpa_supplicant was running. Why is wpa_supplicant running when the wireless device is not active? (I am using _only_ wired ethernet, eth0, at the moment). I noticed the following in /var/log/syslog :
Feb 16 15:44:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 
Feb 16 15:45:43 fingon wpa_supplicant[30855]: CTRL-EVENT-SCAN-RESULTS 
Feb 16 15:45:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 
Feb 16 15:46:43 fingon wpa_supplicant[30855]: CTRL-EVENT-SCAN-RESULTS 
Feb 16 15:46:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 
Feb 16 15:47:43 fingon wpa_supplicant[30855]: CTRL-EVENT-SCAN-RESULTS 
Feb 16 15:47:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 
Feb 16 15:48:43 fingon wpa_supplicant[30855]: CTRL-EVENT-SCAN-RESULTS 
Feb 16 15:48:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 
Feb 16 15:49:43 fingon wpa_supplicant[30855]: CTRL-EVENT-SCAN-RESULTS 
Feb 16 15:49:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 
Feb 16 15:50:43 fingon wpa_supplicant[30855]: CTRL-EVENT-SCAN-RESULTS 
Feb 16 15:50:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 
Feb 16 15:51:43 fingon wpa_supplicant[30855]: CTRL-EVENT-SCAN-RESULTS 
Feb 16 15:51:43 fingon wpa_supplicant[30855]: WPS-AP-AVAILABLE 

ps -auxwww | grep wpa_supplicant yields:
root     30855  0.0  0.0  28328  2676 ?        S    13:32   0:00 /sbin/wpa_supplicant -u -s

So why is it running?
I did a kill -9 30855, and that process died, but a new one was created (by NetworkManager ?) This happened each time I killed the current wpa_supplicant process, until I killed them in rapid succession (with many killall -9 wpa_supplicant). That does finally kill wpa_supplicant _without_ it getting immediately restarted, but now the NetworkManager icon is gone from the toolbar at the botton of the screen (however, a ps -auxwww | grep NetworkManager reveals it is still running). The network device, eth0, was shut down, and the route table flushed. So, I manually restarted eth0 with ifconfig, and recreated the route table. I had network access. I logged into other machines from the Ubuntu box in question, and the remote sessions did not die as before. So, getting rid of  wpa_supplicant apparently solved one problem, but now NetworkManager is screwed - here is part of /var/log/messages:

Feb 16 13:19:39 fingon kernel: [907935.419193] Registered led device: iwl-phy0::radio
Feb 16 13:19:39 fingon kernel: [907935.419219] Registered led device: iwl-phy0::assoc
Feb 16 13:19:39 fingon kernel: [907935.419242] Registered led device: iwl-phy0::RX
Feb 16 13:19:39 fingon kernel: [907935.419262] Registered led device: iwl-phy0::TX
Feb 16 13:19:39 fingon kernel: [907935.472428] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 13:19:40 fingon kernel: [907936.785985] Registered led device: iwl-phy0::radio
Feb 16 13:19:40 fingon kernel: [907936.786016] Registered led device: iwl-phy0::assoc
Feb 16 13:19:40 fingon kernel: [907936.786038] Registered led device: iwl-phy0::RX
Feb 16 13:19:40 fingon kernel: [907936.786058] Registered led device: iwl-phy0::TX
Feb 16 13:19:40 fingon kernel: [907936.861341] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 13:19:41 fingon kernel: [907937.769498] Registered led device: iwl-phy0::radio
Feb 16 13:19:41 fingon kernel: [907937.769521] Registered led device: iwl-phy0::assoc
Feb 16 13:19:41 fingon kernel: [907937.769543] Registered led device: iwl-phy0::RX
Feb 16 13:19:41 fingon kernel: [907937.769568] Registered led device: iwl-phy0::TX
Feb 16 13:19:41 fingon kernel: [907937.801600] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 13:19:42 fingon kernel: [907938.785864] Registered led device: iwl-phy0::radio
Feb 16 13:19:42 fingon kernel: [907938.785889] Registered led device: iwl-phy0::assoc
Feb 16 13:19:42 fingon kernel: [907938.785912] Registered led device: iwl-phy0::RX
Feb 16 13:19:42 fingon kernel: [907938.785933] Registered led device: iwl-phy0::TX
Feb 16 13:19:42 fingon kernel: [907938.841474] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 13:22:38 fingon kernel: [908114.272537] NetworkManager[1217]: segfault at 7fff296cfff8 ip 00007f69b5ef23c1 sp 00007fff296d0000 error 6 in libc-2.10.1.so[7f69b5e7e000+166000]
Feb 16 13:22:41 fingon kernel: [908117.232836] NetworkManager[29216]: segfault at 7fff0220bff8 ip 00007f5d34ca5e34 sp 00007fff0220c000 error 6 in libc-2.10.1.so[7f5d34c61000+166000]
Feb 16 13:22:44 fingon kernel: [908120.299359] nm-applet[2273]: segfault at 50 ip 0000000000420d47 sp 00007fff1eda3070 error 4 in nm-applet[400000+58000]
Feb 16 13:25:18 fingon kernel: [908274.300044] usb 4-1: USB disconnect, address 21
Feb 16 13:27:26 fingon kernel: [908402.912478] ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 16 13:27:26 fingon kernel: [908402.945558] Registered led device: iwl-phy0::radio
Feb 16 13:27:26 fingon kernel: [908402.945582] Registered led device: iwl-phy0::assoc
Feb 16 13:27:26 fingon kernel: [908402.945605] Registered led device: iwl-phy0::RX
Feb 16 13:27:26 fingon kernel: [908402.945631] Registered led device: iwl-phy0::TX
Feb 16 13:27:26 fingon kernel: [908402.981481] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 13:27:28 fingon kernel: [908404.482033] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
Feb 16 13:27:28 fingon kernel: [908404.482036] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
Feb 16 13:27:28 fingon kernel: [908404.482790] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 16 13:28:06 fingon kernel: [908442.225576] Registered led device: iwl-phy0::radio
Feb 16 13:28:06 fingon kernel: [908442.225599] Registered led device: iwl-phy0::assoc
Feb 16 13:28:06 fingon kernel: [908442.225621] Registered led device: iwl-phy0::RX
Feb 16 13:28:06 fingon kernel: [908442.225642] Registered led device: iwl-phy0::TX
Feb 16 13:28:06 fingon kernel: [908442.271489] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 13:28:06 fingon kernel: [908442.860354] usb 4-1: new full speed USB device using uhci_hcd and address 22
Feb 16 13:28:07 fingon kernel: [908443.045667] usb 4-1: configuration #1 chosen from 1 choice
Feb 16 13:29:30 fingon kernel: [908526.785548] Registered led device: iwl-phy0::radio
Feb 16 13:29:30 fingon kernel: [908526.785571] Registered led device: iwl-phy0::assoc
Feb 16 13:29:30 fingon kernel: [908526.785593] Registered led device: iwl-phy0::RX
Feb 16 13:29:30 fingon kernel: [908526.785613] Registered led device: iwl-phy0::TX
Feb 16 13:29:30 fingon kernel: [908526.841482] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 16 13:29:46 fingon kernel: [908542.099638] NetworkManager[29407]: segfault at 7fff05c74f28 ip 00007f7e68285e34 sp 00007fff05c74f30 error 6 in libc-2.10.1.so[7f7e68241000+166000]
Feb 16 13:29:50 fingon kernel: [908546.506276] NetworkManager[29451]: segfault at 7fffd0d51f48 ip 00007f9ede925e34 sp 00007fffd0d51f50 error 6 in libc-2.10.1.so[7f9ede8e1000+166000]
Feb 16 13:29:52 fingon kernel: [908548.156938] NetworkManager[29486]: segfault at 7fffd66a2ff8 ip 00007fea262f83ba sp 00007fffd66a3000 error 6 in libc-2.10.1.so[7fea26284000+166000]
Feb 16 13:30:11 fingon kernel: [908567.439210] NetworkManager[29637]: segfault at 7fff3a393fb8 ip 00007f37d09cfe34 sp 00007fff3a393fc0 error 6 in libc-2.10.1.so[7f37d098b000+166000]
Feb 16 13:30:13 fingon kernel: [908569.274567] NetworkManager[29764]: segfault at 7fff8a100ff8 ip 00007f0ddc4173c1 sp 00007fff8a101000 error 6 in libc-2.10.1.so[7f0ddc3a3000+166000]
Feb 16 13:30:15 fingon kernel: [908571.092776] NetworkManager[29897]: segfault at 7fff27084f28 ip 00007f84d93e1e34 sp 00007fff27084f30 error 6 in libc-2.10.1.so[7f84d939d000+166000]
Feb 16 13:30:17 fingon kernel: [908573.196950] NetworkManager[30046]: segfault at 7ffff75f8f78 ip 00007fabca2cfe34 sp 00007ffff75f8f80 error 6 in libc-2.10.1.so[7fabca28b000+166000]
Feb 16 13:30:19 fingon kernel: [908575.062778] NetworkManager[30303]: segfault at 7fffe5c4df28 ip 00007fe46918fe34 sp 00007fffe5c4df30 error 6 in libc-2.10.1.so[7fe46914b000+166000]
Feb 16 16:03:00 fingon kernel: [917736.791505] usb 4-1: USB disconnect, address 22


If, as root, I execute the command "NetworkManager", it returns immediately as if it were launching as a demon, and it restarts wpa_supplicant again. However, that does not cause the NetworkManager icon to reappear in the toolbar.

So, it looks like this is a bug in wpa_supplicant or NetworkManager, not
openssh. This bug report should be reclassified.

I should note that I often use the wireless internet device, then
hibernate, then thaw and use the wired (eth0) internet device. I rely on
hibernate & thaw to shut down the network interfaces as appropriate.

It looks as if, for reasons I don't understand, NetworkManager is trying
to have wpa_supplicant running even when I'm not using the wireless
internet device (wlan0). Then, wpa_supplicant running seems to interfere
with/kill network connections over eth0 fairly randomly. Perhaps
wpa_supplicant is often stopping and starting, and this sometimes kills
the eth0 connections?

How do I fix the above?

How do I get NetworkManager running again normally, and get its icon
back in the desktop toolbar?

This bug is fairly devastating for me, as when I loose the network
connection to the remove shell (ie: the ssh connection dies) I loose
alot of work.

Thanks,
Greg Huey

-- 
Loosing connections with "Connection reset by peer" message
https://bugs.launchpad.net/bugs/522819
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.



More information about the Ubuntu-server-bugs mailing list