[Networkmanager] NetworkManager stopping after long run

Thomas Haller thaller at redhat.com
Wed Jun 21 12:45:44 UTC 2023

On Tue, 2023-06-20 at 13:13 +0530, manjunatha srinivasan wrote:
> Hi 
> 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; vendo>
>      Active: inactive (dead) since Sat 2023-06-17 19:07:42 UTC; 1 day
> 11h ago
>        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. 
> Regards
> Manjunatha Srinivasan N


check the logfile, that is, `journalctl`.

Also, systemd will log when it starts/stop services, look for that too.

It would seem, that something is sending SIGTERM to NetworkManager (or
call `systemctl stop NetworkManager`).


More information about the Networkmanager mailing list