We frequently see devices in the field where nmcli does not work:
root@e448591:~# nmcli c show Error: Could not create NMClient object: Timeout was reached.
However, the NetworkManager service seems to be happily running:
root@e448591:~# systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/NetworkManager.service.d └─NetworkManager.conf Active: active (running) since Thu 2020-05-28 17:33:02 UTC; 1min 13s ago Docs: man:NetworkManager(8) Main PID: 10939 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─10939 /usr/sbin/NetworkManager --no-daemon
The diagnostics indicate issues with the container engine although it’s up so it seems to have recovered.
Googling does not yield much
We see this problem somewhat often. Rebooting often solves the issue but we’re a bit gun-shy as we’ve had incidences where the device has not returned from reboots, requiring manual reset, which is an issue since our devices are remote.