At the bottom of this post is my complete /etc/watchdog.conf file.
For the most part, it works as expected. If the file webcam.webp does not change in the expected amount of time, watchdog runs the repair script and reboots the Pi.
However, the syslog file has the following entry every second or so:
This is odd because the Pi is online via WiFi.
So, where is this odd message coming from and how can I get rid of it? It seems to be a rather bad use of resources which is certainly my fault. But, what did I do?
For the most part, it works as expected. If the file webcam.webp does not change in the expected amount of time, watchdog runs the repair script and reboots the Pi.
However, the syslog file has the following entry every second or so:
Code:
raspcondo watchdog[738]: device wlan0 did not receive anything since last checkSo, where is this odd message coming from and how can I get rid of it? It seems to be a rather bad use of resources which is certainly my fault. But, what did I do?
Code:
#interface = wlan0#ping = 10.0.0.254#ping-count= 5#interval= 20file= /home/pi/webcam/webcam.webpchange= 600# Uncomment to enable test. Setting one of these values to '0' disables it.# These values will hopefully never reboot your machine during normal use# (if your machine is really hung, the loadavg will go much higher than 25)max-load-1= 24#max-load-5= 18#max-load-15= 12# Note that this is the number of pages!# To get the real size, check how large the pagesize is on your machine.#min-memory= 1#allocatable-memory= 1repair-binary = /home/pi/webcam/repair.shrepair-timeout= 120#test-binary=#test-timeout= 60# The retry-timeout and repair limit are used to handle errors in a more robust# manner. Errors must persist for longer than retry-timeout to action a repair# or reboot, and if repair-maximum attempts are made without the test passing a# reboot is initiated anyway.#retry-timeout= 60#repair-maximum= 1#watchdog-device= /dev/watchdog# Defaults compiled into the binary#temperature-sensor=#max-temperature= 90# Defaults compiled into the binary#admin= root#interval= 1#logtick = 1#log-dir= /var/log/watchdog# This greatly decreases the chance that watchdog won't be scheduled before# your machine is really loadedrealtime= yespriority= 1# Check if rsyslogd is still running by enabling the following line#pidfile= /var/run/rsyslogd.pidStatistics: Posted by Ratsima — Tue Jul 22, 2025 10:40 am