LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 02-13-2014, 11:29 AM   #1
5883
Member
 
Registered: Aug 2004
Posts: 173

Rep: Reputation: 0
NetworkManager process dies sometimes


This is for embedded system, kernel 3.0.35-cm-fx6-4,

fs is using ubuntu.

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)

The problem is we use networkmanager to manager the 2 ethernet ports. Most of the time it's fine.

Once a while no network connection, and turned out to be networkmanager has died.

Pls note this could happen during weekends, no one is doing anything to the board, which has our application running.

Where should i get started on this pls ?
 
Old 02-13-2014, 11:31 AM   #2
5883
Member
 
Registered: Aug 2004
Posts: 173

Original Poster
Rep: Reputation: 0
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.
 
Old 02-13-2014, 11:42 AM   #3
5883
Member
 
Registered: Aug 2004
Posts: 173

Original Poster
Rep: Reputation: 0
actually "NetworkManager --version" shows 0.9.4.0 as well, lost ...

Quote:
Originally Posted by 5883 View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
data push from box to removable usb drive dies, then dies, then dies again. bodyofabanshee Linux - Server 11 03-15-2012 11:34 AM
NetworkManager dies on boot gregnorc Linux - Wireless Networking 1 09-30-2009 05:22 PM
Emails myself when a process dies prudens Linux - Newbie 4 08-11-2009 03:02 AM
bash `kill`: process 'B' silently dies; but process 'A' = `kill` spews back debris! GrapefruiTgirl Programming 9 06-23-2009 09:42 AM
Releasing RWLocks from SHM when process dies rajkiran.ravi Programming 4 12-08-2008 08:59 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 10:36 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration