Re: NM stops and doesn't connect

[Dan Williams <dcbw redhat com>]

On Mon, 2009-03-09 at 19:43 +0000, Cliff McDiarmid wrote:
> Hi
> 
> The last mail ended up blank trying this one:
> 
> Can anyone advise on this error from NM after the supplicant is up with:

Are you using the supplicant manually?  With NM, there's no need to have
a supplicant config file even, since NM will send config information to
the supplicant on its own, based on the connections you've defined
either in your distro config files or in GConf.

> Trying to associate with ************* (SSID='Thomson7F8759' freq=2412 MHz)
> Associated with *************
> WPA: Key negotiation completed with ************ [PTK=CCMP GTK=TKIP]
> CTRL-EVENT-CONNECTED - Connection to ************ completed (auth) [id=0 id_str=]
> CTRL-EVENT-SCAN-RESULTS 
> CTRL-EVENT-SCAN-RESULTS 
> 
> 
> Mar  7 14:29:50 cliffhanger NetworkManager: <info>  starting... 
> Mar  7 14:29:50 cliffhanger NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess  
> Mar  7 14:29:50 cliffhanger NetworkManager: <info>  wlan0: driver is 'iwl3945'. 
> Mar  7 14:29:50 cliffhanger NetworkManager: <info>  wlan0: driver supports SSID scans (scan_capa 0x01). 
> Mar  7 14:29:50 cliffhanger NetworkManager: <info>  Found new 802.11 WiFi device 'wlan0'. 
> Mar  7 14:29:50 cliffhanger NetworkManager: <info>  (wlan0): exported as /org/freedesktop/Hal/devices/net_00_13_02_0d_3f_93 
> Mar  7 14:29:50 cliffhanger NetworkManager: <info>  Trying to start the system settings daemon... 
> Mar  7 14:29:54 cliffhanger NetworkManager: <info>  (wlan0): device state change: 1 -> 2 
> Mar  7 14:29:54 cliffhanger NetworkManager: <info>  (wlan0): preparing device. 
> Mar  7 14:29:54 cliffhanger NetworkManager: <info>  (wlan0): deactivating device (reason: 2). 
> Mar  7 14:29:54 cliffhanger NetworkManager: <info>  Setting system hostname to 'localhost.localdomain' (no default device) 
> Mar  7 14:29:54 cliffhanger NetworkManager: <info>  (wlan0): device state change: 2 -> 3 
> Mar  7 14:29:54 cliffhanger NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready 
> Mar  7 14:31:50 cliffhanger NetworkManager: <info>  Trying to start the system settings daemon... 
> Mar  7 14:33:50 cliffhanger NetworkManager: <info>  Trying to start the system settings daemon... 
> Mar  7 14:35:50 cliffhanger NetworkManager: <info>  Trying to start the system settings  
> ETC ETC ETC

NetworkManager is trying to start the system settings service with D-Bus
service activation, which is normal.  Do you have
the /usr/share/dbus-1/system-services/org.freedesktop.NetworkManagerSystemSettings.service file, and if so, what does it contain?

> If I use this check 
> 
> nm-system-settings --debug --config /etc/NetworkManager/nm-system-settings.conf
> 
> I get:.
> 
> ** Message: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list

Expected, the service is running as normal and should be providing data
to NetworkManager via D-Bus.  It does not daemonize becuase it doesn't
need to when its started with D-Bus service activation, which is the
normal procedure.

When nm-system-settings is started, what's the output of the following
command?

dbus-send --system --print-reply --dest=org.freedesktop.NetworkManagerSystemSettings /org/freedesktop/NetworkManagerSettings org.freedesktop.NetworkManagerSettings.ListConnections

If that returns something like:

method return sender=:1.6 -> dest=:1.5810 reply_serial=2
   array [
      object path "/org/freedesktop/NetworkManagerSettings/0"
   ]

then the system settings service is working correctly.

Dan

> the system then stops and I have to ctrl-c to bring the prompt back
> 
> What's going on?  Google mentions this error but no solution.
> 
> thanks
> 
> MAC
>