Hi Thomas
Firstly, it can take as much as 15 minutes for FILE/file: config changes to start showing up in Xymon. Also note that changes to analysis.cfg might not be picked up automatically, and I often run "sudo -u xymon pkill -f xymond_client" to ensure that changes are instantiated quickly. I don't think I've ever needed to do anything for changes to analysis.cfg to be picked up by Xymon.
The first thing I would check is to see if the client-local.cfg "file:" settings are correct for the bookworm systems. Review the client-local.cfg file, and if it looks correct, try submitting a dummy client message to see what Xymon returns:
from on the Xymon server:
$ xymon 127.1 "client/test yourhostname.linux"
This should spit out the parts of the client-local.cfg file that apply to the host. Look for "file:" entries.
Then I would confirm that the systems are receiving and storing the client-local snippet. On the client, locate the logfetch cfg file, example:
$ echo 'ls $XYMONTMP/*cfg' | xymoncmd sh /dev/shm/logfetch.yourhostname.example.com.cfg
Have a look in the file, and see if the contents match what's in the client-local.cfg, and the output of the "xymon" client command above. If not, there might be something wrong on the client, such as the file being owned by root so that the xymon user cannot update it.
Cheers Jeremy
On Wed, 14 Aug 2024 at 00:22, Thomas Mackell Sr. <ki4fru@gmail.com> wrote:
I'm using a\several Raspberry PI 4 with 8Gb memory running Debian 12 Bookworm using Xymon 4.3.30. I have other Pi's running Debian GNU/Linux 11 (bullseye) with no issues.
On the Bookworm systems the Files column is blank.
Click on it shows: *Tue Aug 13 10:03:01 EDT 2024 - Files ok*
No files checked This is the Here is the analysis.cfg entry
HOST=raspberrypi5 LOAD 5.0 10.0 DISK * 80 85 MEMPHYS 99 101 MEMSWAP 80 90 MEMACT 90 97 UP 30m PROC cron 1 9 red "TEXT=cron task " PROC nmon 0 2 yellow "TEXT=NMON Monitor " FILE /etc/machine-info SIZE>0 red FILE /var/log/pi-Available.list SIZE>0 yellow FILE /var/log/pi-Installed.list SIZE>0 yellow LOG /var/log/messages \%NOTICE|\%ERROR COLOR=yellow IGNORE=INFO LOG /var/log/xymon/xymonclient.log \%NOTICE|\%ERROR|\%Whoops COLOR=yellow LOG /var/log/xymon/clientlaunch.log \%NOTICE|\%ERROR|\%Whoops COLOR=yellow
It the same basic entries for all of my systems. At this point only the bookworm systems have this issue.
Any ideas on how to fix this?
Tom Mackell ki4fru@gmail.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com