Bug 492538

Summary: Network Manager is dead but pid file exists
Product: [Fedora] Fedora Reporter: markm <marek78uk>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: low    
Version: 10CC: dcbw, dusan, yunus.tji.nyan
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-27 15:50:02 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
crash of NM none

Description markm 2009-03-27 10:44:09 UTC 
Description of problem:

I've started my laptop today and there was no network. Network Manager was started, but died:

[root@m4300 ~]# /etc/init.d/NetworkManager status
NetworkManager dead but pid file exists
[root@m4300 ~]# /etc/init.d/NetworkManager start
Setting network parameters...                              [  OK  ]
Starting NetworkManager daemon:                            [  OK  ]
[root@m4300 ~]# /etc/init.d/NetworkManager status
NetworkManager dead but pid file exists
[root@m4300 ~]#

I've restarted my laptop two times, no change.

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

[root@m4300 ~]# rpm -qa | grep NetworkManager
NetworkManager-gnome-0.7.0.99-4.git20090324.fc10.i386
NetworkManager-glib-0.7.0.99-4.git20090324.fc10.i386
NetworkManager-0.7.0.99-4.git20090324.fc10.i386
[root@m4300 ~]# 

How reproducible:

always

Additional info:

I've managed to start wired connection via Network applet from System -> Administration, when I tried to start NM after that, my pidgin thought it got disconnected while I could still ping internet from command line.
Comment 1 markm 2009-03-27 11:34:40 UTC 
downgrade to:

NetworkManager-glib-0.7.0-0.11.svn4229.fc10.i386
NetworkManager-gnome-0.7.0-0.11.svn4229.fc10.i386
NetworkManager-0.7.0-0.11.svn4229.fc10.i386

solved the problem
Comment 2 Dušan Hokův 2009-03-27 13:02:53 UTC 
Created attachment 337005 [details]
crash of NM

NM crashed after successful connect to openvpn type vpn.
Comment 3 Dušan Hokův 2009-03-27 13:50:04 UTC 
downgrade to:

NetworkManager-glib-0.7.0.99-3.fc10.i386
NetworkManager-0.7.0.99-3.fc10.i386
NetworkManager-vpnc-0.7.0.99-1.fc10.i386
NetworkManager-gnome-0.7.0.99-3.fc10.i386
NetworkManager-openvpn-0.7.0.99-1.fc10.i386
NetworkManager-pptp-0.7.0.99-1.fc10.i386

solve my problem
Comment 4 Dušan Hokův 2009-03-27 13:56:42 UTC 
I downgraded only NM, NM-glib and NM-gnome and it works for me.
Comment 5 yunus 2009-03-27 15:50:02 UTC 

*** This bug has been marked as a duplicate of bug 492246 ***