On 29/11/2022 01:21, Kris Springer wrote:
Thanks for pointing me in the direction of the client script. I messed around with it a lot
I'd advise against editing the xymonclient script unless you're very careful, because...
So then in the script with all the df stuff commented out, I had it run
df /dev/sda
...putting this in the client script will break server-side processing because...
The results of the script show the USB, but nothing shows up on the Server Disk page except this error.
Expected strings (Capacity and Mounted) not found in df output
..one of the df arguments specified in the original client script is "-P" which specifies "use the POSIX output format". Compare the header row generated by df with and without -P:
$ df | head -n1
Filesystem 1K-blocks Used Available Use% Mounted on
$ df -P | head -n1
Filesystem 1024-blocks Used Available Capacity Mounted on
xymond is expecting the latter format, so by manually hacking the client script and changing the arguments, the message sent to the server is no longer in the format it expects - which is what's leading to that "Expected strings ... not found" message, I think.
I'd suggest putting the original client script back in place and debugging from there. Perhaps a good place to start would be with a very simple analysis.cfg with just two lines:
DEFAULT
DISK * 90 95
and nothing else. If your disk then shows up in the 'disk' report, the problem is somewhere in your live analysis.cfg. I'm not immediately sure when analysis.cfg is reread - I can't see any mention in the documentation, but I may not be looking in the right place.
Adam