linux watchdog on raspberrypi 3

Begonnen von HarryT, 03 Juni 2026, 15:33:41

Vorheriges Thema - Nächstes Thema

HarryT

Hi
I use the linux watchdog on my raspberrypi 3 for years without problems. 
Now I build a new fhem installation on top of Trixie / Debian 13.
After about a week my RaspberryPi stops working. FHEM stops and the raspberry won't accept an ssh connection anymore. However the yellow led add the raspberry is still blinking a bit so there seems to be some activity.Strange enough my watchdog doesn't kickin and reboot the raspberry.  However a test with
 sudo bash -c ':(){ :|:& };:'triggers a reboot. So I guess watchdog is installed correct. 
I used scripted installations and the install for watchdog is:

sudo apt install watchdog

echo 'watchdog-timeout = 15' | sudo tee -a  /etc/watchdog.conf
echo 'max-load-1 = 24' | sudo tee -a  /etc/watchdog.conf

echo 'dtparam=watchdog=on' | sudo tee -a  /boot/firmware/config.txt

sudo systemctl enable watchdog
sudo systemctl start watchdog

I will change the watchdog config a bit so it will also trigger when a specific fhem file is not updated. That might be enough.
Has anybody an idea why my watchdog  doesn't trigger a reboot yet or even an idea why my raspberry stops responding?
Thanks for any response.
FHEM 6.4 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz), Raspberry Pi4 and RaspberryPi 5 for testing
German reading skills are good.

KölnSolar

I had a lot of problems setting up a rpi3 with Trixie, which worked with older debian. Main Problem were the USBs which are connected to the ethernet port. Thats possibly the cause not rebooting by the watchdog, because the system is still Running but network isn't working.

With a new rpi5 my problems were gone. The network is separated from the USBs !

Regards
Markus
RPi5/3/2 Trixie-SamsungAV_E/N-RFXTRX-IT-RSL-NC5462-Oregon-CUL433-GT-TMBBQ-01e-CUL868-FS20-EMGZ-1W(GPIO)-DS18B20-CO2-USBRS232-USBRS422-Betty_Boop-EchoDot-OBIS(Easymeter-Q3/EMH-KW8)-PCA301(S'duino)-Deebot(mqtt2)-ecovacs(mqtt2)-zigbee2mqtt

HarryT

Zitat von: KölnSolar am 03 Juni 2026, 15:46:41I had a lot of problems setting up a rpi3 with Trixie, which worked with older debian.

Me too. Previous updates where easy, but this one....

ZitatMain Problem were the USBs which are connected to the ethernet port. Thats possibly the cause not rebooting by the watchdog, because the system is still Running but network isn't working.

With a new rpi5 my problems were gone. The network is separated from the USBs !

Regards
Markus

Might be the reason. I now trigger watchdog on a file which is on an ssd attached over USB. What do you think about that? Could it be enough to trigger the watchdog?

A liitle bit out of time now. I will study the previous threat about this tomorrow. 

Thanks
FHEM 6.4 auf Raspberry Pi3  (1,2 Ghz)
RFXTRX433XL, ZWave, KFL200 and ConBeeIII
Raspberry Pi1 (0,7 Ghz), Raspberry Pi4 and RaspberryPi 5 for testing
German reading skills are good.

KölnSolar

ZitatWhat do you think about that? Could it be enough to trigger the watchdog?
I think it will not help. FHEM is still running, I assume.

Maybe there is another watchdog option, that reboots the rpi, if LAN isn't accessible ?
RPi5/3/2 Trixie-SamsungAV_E/N-RFXTRX-IT-RSL-NC5462-Oregon-CUL433-GT-TMBBQ-01e-CUL868-FS20-EMGZ-1W(GPIO)-DS18B20-CO2-USBRS232-USBRS422-Betty_Boop-EchoDot-OBIS(Easymeter-Q3/EMH-KW8)-PCA301(S'duino)-Deebot(mqtt2)-ecovacs(mqtt2)-zigbee2mqtt