Bug 209009

Summary: NetworkManager crashes pretty often
Product: [Fedora] Fedora Reporter: Pekka Pietikäinen <pp>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: F8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-12 08:18:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/messages from affected machine
none
/var/log/messages output for NetworkManager catching Signal 6 none

Description Pekka Pietikäinen 2006-10-02 22:08:23 UTC 
Description of problem:

NetworkManager crashes every few days for no apparent reason. Hardware is
eth0=e1000, eth1=airo, typically only wireless gets used (and one of them
often gets renamed to somethin like __tmp1804289383 by something, but that's
another thing).

Version-Release number of selected component (if applicable):

0.6.4-5.fc6

How reproducible:

Use NetworkManager in a scenario, where there's one SSID that's almost always
there, occasionally a second one with WEP turned on (and when that's in reach,
it's also used). Wired port is seldom touched.

Crashdump from syslog attached including debug symbols.

Could be related to #195643, but since the traceback didn't have any symbols,
it's impossible to say whether this is the same crash or not.
Comment 1 Pekka Pietikäinen 2006-10-02 22:08:23 UTC 
Created attachment 137606 [details]
/var/log/messages from affected machine
Comment 2 Christopher Aillon 2006-10-05 22:12:00 UTC 
A workaround seems to be to fill in the appropriate HWADDR lines in
/etc/sysconfig/network-scripts/ifcfg-*
Comment 3 Tom London 2006-10-27 14:03:42 UTC 
I'm getting a different crash: Signal 6: (log attached)

Oct 27 06:51:01 localhost NetworkManager: <WARN>  nm_signal_handler(): Caught
signal 6.  Generating backtrace...
Oct 27 06:51:02 localhost NetworkManager: ******************* START
**********************************
Oct 27 06:51:03 localhost NetworkManager: (no debugging symbols found)
Oct 27 06:51:03 localhost NetworkManager: Using host libthread_db library
"/lib/libthread_db.so.1".
Oct 27 06:51:03 localhost NetworkManager: (no debugging symbols found)
Oct 27 06:51:04 localhost last message repeated 10 times

[root@localhost ~]# service NetworkManager status
NetworkManager dead but pid file exists
[root@localhost ~]# 
[root@localhost ~]# service NetworkManager start
Setting network parameters... 
Starting NetworkManager daemon:                            [  OK  ]
[root@localhost ~]# 

Started up correctly and seems to be working.
Comment 4 Tom London 2006-10-27 14:07:05 UTC 
Created attachment 139582 [details]
/var/log/messages output for NetworkManager catching Signal 6
Comment 5 Dan Williams 2008-02-12 03:23:52 UTC 
Seems more like a libdbus error, what version of dbus do you have installed?
Comment 6 Pekka Pietikäinen 2008-02-12 08:18:04 UTC 
Err. Versions now are 

NetworkManager-0.7.0-0.8.svn3302.fc9.i386
dbus-1.1.4-4.fc9.i386

(vs. fc6 or rawhide after it in the report) and I can't remember NM crashing for
ages, F8 was fine at least. -> closing CURRENTRELEASE, I'm pretty sure someone
would have added later comments had this not been fixed by either a NM or dbus
update.