[Networkmanager] NetworkManager stopping after long run

manjunatha srinivasan manjunathan.n at gmail.com
Tue Jun 20 07:43:27 UTC 2023


In the Linux environment of my embedded board, It is observed
NetworkManager (1.36.2)  is stopped with exit state as SUCCESS after a long
run (~ 4days). There was traffic movement in the ethernet interface during
long run testing.  I suspect systemd might have sent SIGTERM
to NetworkManager.   Currently I don't have proper logs from journalctl.
Anyway, I have been triggered again for a long run test with a workaround
for restarting it again after 5 secs. always.

Below is log status of NetworkManager after stopping:
systemctl status NetworkManager
○ NetworkManager.service - Network Manager
     Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
     Active: inactive (dead) since Sat 2023-06-17 19:07:42 UTC; 1 day 11h
       Docs: man:NetworkManager(8)
    Process: 926 ExecStart=/usr/sbin/NetworkManager --no-daemon
(code=exited, s>
   Main PID: 926 (code=exited, status=0/SUCCESS)

My query is why NetworkManager stopped in long run testing? Please let me
know any configuration I need to look into.

Manjunatha Srinivasan N
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/networkmanager/attachments/20230620/7281dfed/attachment.htm>

More information about the Networkmanager mailing list