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