Monitor stops working after update/upgrade of OS

[stu247]

I use Monitor on a Pi Zero W. It has worked great for me for a couple years now. I recently ran an update/upgrade on the OS. After that the Pi Zero would stop working after an hour or two. The Pi Zero was not accessible via ping or ssh and Monitor would not send out any MQTT messages. It would work again after a reboot, but only for an hour or two.

If I stopped Monitor, then the Pi Zero runs for days without issue. I reinstalled the OS and Monitor from scratch and had the same issue. I then reinstall the OS and Monitor, but did not upgrade/update the OS. In that case, Monitor works fine without the upgrade/update.

There is no change to the Monitor code, so I do not believe the issue is with Monitor. It looks like a bug was introduced in software that Monitor depends on (for example, library, module, kernel, or firmware). I am using Raspberry Pi OS Lite 2021-10-20 and Monitor 0.2.200. The Mosquitto version is 2.0.11 and does not change with the update/upgrade.

Is there a particular package update that could be causing this?

Here is the list of updated packages:

base-files (11.1+rpi1+deb11u2) over (11.1+rpi1+deb11u1) ...
libc6-dbg:armhf (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
libc-devtools (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
libc6-dev:armhf (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
libc-dev-bin (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
linux-libc-dev:armhf (1:1.20211118-3) over (1:1.20211029-1) ...
libc6:armhf (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
libc-bin (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
libwbclient0:armhf (2:4.13.13+dfsg-1~deb11u2) over (2:4.13.5+dfsg-2) ...
libgmp10:armhf (2:6.2.1+dfsg-1+deb11u1) over (2:6.2.1+dfsg-1) ...
libseccomp2:armhf (2.5.1-1+rpi1+deb11u1) over (2.5.1-1+rpi1) ...
tzdata (2021a-1+deb11u2) over (2021a-1+deb11u1) ...
vim-tiny (2:8.2.2434-3+deb11u1) over (2:8.2.2434-3) ...
xxd (2:8.2.2434-3+deb11u1) over (2:8.2.2434-3) ...
vim-common (2:8.2.2434-3+deb11u1) over (2:8.2.2434-3) ...
libc-l10n (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
locales (2.31-13+rpt2+rpi1+deb11u2) over (2.31-13+rpt2+rpi1) ...
wget (1.21-1+deb11u1) over (1.21-1) ...
curl (7.74.0-1.3+deb11u1) over (7.74.0-1.3) ...
libcurl4:armhf (7.74.0-1.3+deb11u1) over (7.74.0-1.3) ...
dhcpcd5 (1:8.1.2-1+rpt3) over (1:8.1.2-1+rpt2) ...
distro-info-data (0.51+deb11u1) over (0.51) ...
firmware-atheros (1:20210315-3+rpt4) over (1:20210315-3+rpt2) ...
firmware-brcm80211 (1:20210315-3+rpt4) over (1:20210315-3+rpt2) ...
firmware-libertas (1:20210315-3+rpt4) over (1:20210315-3+rpt2) ...
firmware-misc-nonfree (1:20210315-3+rpt4) over (1:20210315-3+rpt2) ...
firmware-realtek (1:20210315-3+rpt4) over (1:20210315-3+rpt2) ...
libatopology2:armhf (1.2.4-1.1+rpt2) over (1.2.4-1.1+rpt1) ...
libasound2:armhf (1.2.4-1.1+rpt2) over (1.2.4-1.1+rpt1) ...
libasound2-data (1.2.4-1.1+rpt2) over (1.2.4-1.1+rpt1) ...
libcamera0:armhf (0~git20211020+f4070274-3) over (0~git20211020+f4070274-1) ...
libcurl3-gnutls:armhf (7.74.0-1.3+deb11u1) over (7.74.0-1.3) ...
libraspberrypi-dev (1:2+git20211125~155417+14b90ff-2) over (1:2+git20210928~141951+6e8f786-2) ...
raspberrypi-kernel (1:1.20211118-3) over (1:1.20211029-1) ...
raspberrypi-bootloader (1:1.20211118-3) over (1:1.20211029-1) ...
libraspberrypi-bin (1:2+git20211125~155417+14b90ff-2) over (1:2+git20210928~141951+6e8f786-2) ...
libraspberrypi0:armhf (1:2+git20211125~155417+14b90ff-2) over (1:2+git20210928~141951+6e8f786-2) ...
libraspberrypi-doc (1:2+git20211125~155417+14b90ff-2) over (1:2+git20210928~141951+6e8f786-2) ...
publicsuffix (20211207.1025-0+deb11u1) over (20210108.1309-1) ...
raspberrypi-net-mods (1.3.3) over (1.3.0) ...
raspi-config (20211203) over (20211019) ...
rpi-eeprom (13.3-1) over (12.13-1) ...
vcdbg (1:1.20211118-3) over (1:1.20211029-1) ...

[stockfisch]

Happy new year!
I'm suffering from the same issues, and I believe it's something ARM/ Raspberry Pi specific.
I'm running 3 Monitor installations, 1x RPI Zero W, 1x RPI Zero 2W, 1x x86 Debian on a Proxmox VM.
All 3 installations are up to date. WLAN power- save is switched off on the RPIs.
Both RPI's are randomly becoming unresponsive within a few hours after startup. The x86 installation is running flawlessly. When the RPI's are crashing, it seems to happen at an arrival/ departure scan.

Will try a "2021-10-30-raspios" installation without updates now.

Thanks Dirk

[gedger]

Did you get anywhere with this, I have the same issue but don't have time to debug at the moment?

[stu247]

I have not done anything since creating the issue in github. I have stayed on Raspberry Pi OS Lite 2021-10-20 without doing any update/upgrade and Monitor is working fine. Recently, I was thinking about doing an update/upgrade to see if the problem went away, but if you recently had the same issue, then I don't think I will do the update/upgrade.