On 9 May 2018 at 02:14, Rich Jones <rich at corporationpop.co.uk> wrote:
Hi all,
Another one of those things I keep meaning to ask but keep on forgetting... I'm seeing under the xymond column the following:
Multi-source statuses xymon.url.com:cpu reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:disk reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:files reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:inode reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:memory reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:msgs reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:ports reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:procs reported by 127.0.0.1 and xx.xxx.226.227 xymon.url.com:uptime reported by 127.0.0.1 and xx.xxx.226.227
Looking through the archive it makes sense, Xymon is receiving data from two sources, which I guess it is, however the two IPs are localhost and the server IP address.
I'm guessing this is likely to do with how the things are setup on the server rather than Xymon itself (eg in /etc/hosts)?
Can someone point me in the right direction to resolve this? I'm running Xymon 4.3.28
It appears that the Xymon server is reporting to itself twice, using its network IP address and the loopback address. The Xymon client that generates the client data messages (from where these metrics come) will use the $XYMSRV environment variable, and send to whatever IP address is defined therein. Sometimes this is set to "0.0.0.0" which tells the Xymon client to look at $XYMSERVERS as a list of multiple destinations. I suspect you have XYMSERVERS="127.0.0.1 xx.xxx.226.227". On a Xymon server these variables are is set in xymonserver.cfg.
J