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.
We’re running 2.48. I’m seeing the issue right now on 1e464992d4426c665b1a7c45857ecc40. I have provided support access, but I may have to reboot to avoid the system going offline completely.
It could be related to the issue you linked to. We have a script that periodically tears down the wifi and brings it back up again as a response to a problem we have seen. It may be that this process is what causes the issue. Also, our internet connection is via cellular and are not very reliable.
Hi,
I’ve just checked the device and see nmcli working normally there.
We suggest editing the network manager configuration to disable connectivity check and observing the device to see if it has any effect.
The connectivity check settings are defined in /etc/NetworkManager/conf.d/os-networkmanager.conf.
Normally, it’s controlled with config.json:
And will be rewritten on reboot. But if you need to do an experiment without a reboot, you can edit the file directly.
Also, it’s worth checking the difference between NetworkManager/nmcli installed on the host OS and in your container. Big version differences can cause problems as well.
The versions are 1.20.8 and 1.120.2 so presumably close. I’ll continue playing around to see if changing the connectivity checks affects stability. As it is now, the resident NetworkManager connectivity check is every hour.