Hi Josh
The host's client seems to be behaving as if it's running in local mode rather than central mode. In local mode, the host's OS metrics (CPU, disk, etc) are reported as individual "status" type messages. In central mode, the metrics are compiled into the client message log and sent as a single "client" type message.
It's been a while since I looked into running a Xymon client in local mode. I believe you can find the current mode from the xymonlaunch process list, like so:
$ sudo -u xymon strings /proc/pgrep xymonlaunch/environ | grep ^LOCALMODE
This will output "yes" if running in local mode, and "no" if running in central mode. The client runs in local mode when LOCALMODE is set to "yes". I believe this is set in the file xymonclient.cfg, which is typically located in $XYMONHOME/etc/.
Cheers Jeremy
On Fri, 20 Dec 2024 at 09:16, Josh Luthman <josh@imaginenetworksllc.com> wrote:
I'm hitting a wall and hoping someone can give me a sanity check.
I had an old server that was working. It was on Centos 7 and consequently why I'm replacing it. I installed Alma9 on a new server (hardware) and replaced said hardware.
The new server is definitely reporting information (xymon-client) to the server - cpu column has a list of processes, disk is showing df output, etc. But clientlog is absolutely empty. However, the files/procs columns are showing "No files checked" even though the same hostname with previous hardware had test results and history. The hostname is certainly the same and there are no ghost clients.
I added an extra script in ext and this works as expected.
Compiled from stable 4.3.30.
Any ideas?! I'm not seeing anything useful in any of the logs anywhere - client or server.
Josh Luthman 24/7 Help Desk: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com