Yocto BSP Mickledore-LF6.1.22/LF6.1.36 : NetworkManager.service: Start request repeated too quickly.

[khang_letruong]

Dear Community,

I followed the instruction in the following discussion and was able to replace the Connection Manager by the Network Manager : https://community.nxp.com/t5/i-MX-Processors/Yocto-BSP-Mickledore-LF6-1-22-How-to-add-Network-Manage...

However, I am struggling with the NetworkManager.service on booting up : it is often failed to load

root@viperimx8mp:~# systemctl status NetworkManager.service
x NetworkManager.service - Network Manager
     Loaded: loaded (8;;file://viperimx8mp/lib/systemd/system/NetworkManager.service/lib/systemd/sy;
     Active: failed (Result: exit-code) since Tue 2023-10-17 07:13:26 UTC; 9min ago
       Docs: 8;;man:NetworkManager(8)man:NetworkManager(8)8;;8;;
    Process: 663 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, status=1/FAILURE)
   Main PID: 663 (code=exited, status=1/FAILURE)

Oct 17 07:13:26 viperimx8mp systemd[1]: NetworkManager.service: Scheduled restart job, restart coun.
Oct 17 07:13:26 viperimx8mp systemd[1]: Stopped Network Manager.
Oct 17 07:13:26 viperimx8mp systemd[1]: NetworkManager.service: Start request repeated too quickly.
Oct 17 07:13:26 viperimx8mp systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
Oct 17 07:13:26 viperimx8mp systemd[1]: Failed to start Network Manager.

Stopping and (re-)staring the service manually does not change the status.

In attachment is the output of journalctl command. It seems that other NetworkManager processes (than the 554) were launched by the service restarting mechanism (due to some reason) but failed, while the existing NetworkManager process (554) was still running:

root@viperimx8mp:~# ps aux | grep Network
root         554  0.1  0.7 246932 13292 ?        Ssl  07:13   0:02 /usr/sbin/NetworkManager
root         760  0.0  0.0   2948  1308 ttymxc1  S+   07:34   0:00 grep Network

I even downgraded the Network Manager to the version that works well and is aligned with the Yocto Hardknott-LF5.10.72 :

root@viperimx8mp:~# nmcli -v
nmcli tool, version 1.30.4

But it does NOT seem better. Could you give your advice, please ?

Thanks in advance and best regards,
Khang

[Harvey021]

From log, it seems the NetworkManager.service conflicts with other service.

Have tried to kill the PID and then restart the service?

Best regards

Harvey

Best regards

Harvey

[khang_letruong]

Hi @Harvey021 ,

From the log, I think that it conflicts with itself : an NetworkManager process (554) was already running early, why other processes (other than the 554) were also launched for some unknown reason.

Regards,

Khang