On Mon, 2014-02-17 at 16:20 +0000, ning ji wrote: > we're running release version, we used apt-get install in the ubuntu system > (arm platform). > Will send error message when i can reproduce it. > At this point, we do see such things, even though NM is still running and > ping still works for both eth ports. > /var/log/syslog.1:Jan 10 16:50:33 utilite-ubuntu-desktop > NetworkManager[2831]: <error> [1389390633.544433] [nm-manager-auth.c:87] > pk_authority_get(): Failed to initialize PolicyKit: (23) Error initializing > authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: > GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute > program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
It looks like PolicyKit isn't running on your system. Note that NetworkManager doesn't *need* PolicyKit, but you need to specify that at build time with "--disable-polkit". So if you'd rather not run PolicyKit, you can rebuild NM to work without it. And in fact, if you're on an embedded system, that's probably what you want to do. Dan > Many thanks ! > > > > Subject: Re: NetworkManager process dies sometimes > > From: [email protected] > > To: [email protected] > > CC: [email protected] > > Date: Fri, 14 Feb 2014 09:05:40 -0600 > > > > On Fri, 2014-02-14 at 03:45 +0000, ning ji wrote: > > > This is for embedded system, kernel 3.0.35-cm-fx6-4, > > > fs is using ubuntu 12.02。NetworkManager version is 0.9.4. > > > > > > Since this is embedded system, there's no GUI, you can just view message > > > outputs from console.(BUT we do have 2 login sessions, 1 is for GUI, > > > don't ask me why, someone else did it) > > > We use networkmanager to manager the 2 ethernet ports. Most of the time > > > it's fine.0Once a while no network connection, and turned out to be > > > networkmanager process has died.Pls note this could happen during > > > weekends, no one is touching the board, our application should has > > > nothing to with it. > > > Also Not sure if related, but someone's board displays this, > > > ** (process:31111): WARNING **: Could not initialize NMClient > > > /org/freedesktop/NetworkManager: Did not receive a reply. Possible causes > > > include: the remote application did not send a reply, the message bus > > > security policy blocked the reply, the reply timeout expired, or the > > > network connection was broken. > > > Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. > > > Force execution using --nocheck, but the results are unpredictable. > > > The funny thing is, our NetworkManager is 0.9.4 from "--version".Where > > > should i get started on this pls ? > > > > > > > Are you able to get a crash trace from NetworkManager? One way to do > > this would be to run NetworkManager under 'gdb' if possible, and wait > > until it fails, then do a "backtrace" command to see where NM crashed. > > Ideally the board would also have NetworkManager build with debug > > symbols too. > > > > Would you be able to run NM under gdb and get a backtrace? > > > > Would you also be able to get some syslog 'daemon' facility output as > > well? (usually /var/log/messages or /var/log/NetworkManager.log > > or /var/log/daemon.log) > > > > Dan > > > _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
