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
