thanks jeremy...
server OS is CentOS release 5.5
client OS is CentOS release 6.4
I did find some gumf about uising a bb-hosts entry
XXX.XXX.XXX.XXX client # NOCOLUMNS:memory
to at least avoid showing the reports/monitor
but that made absolutely zero difference so i have no idea what on earth that is about :-)
cheers
ian
From: Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
To: Ian Diddams <user-7fbf34ed5219@xymon.invalid>
Cc: "xymon at xymon.com" <xymon at xymon.com>
Sent: Thursday, 10 July 2014, 4:48
Subject: Re: [Xymon] stop monitoring memory
On 9 July 2014 20:43, Ian Diddams <user-7fbf34ed5219@xymon.invalid> wrote:
Oh - as I understand this is in local mode.
My understanding is that in local mode, the memory data is analysed and sent by xymond_client. Perhaps you could run this with the "--debug" switch to see what's going on. Also, you could use a xymond_channel command on the server to watch the memory status messages come in, to check whether they're coming from the client. Something like:
xymond_channel --channel=status --filter='name-of-host.*\|memory\|' cat
As far as I can tell from reviewing the code, the xymond_client program gets its memory numbers from the client data, but it uses different section names depending on the OS. For Linux, it looks only in [free], for FreeBSD it looks in [meminfo] and [swapinfo], and for Solaris it looks in [memory], [swap] and [swaplist]. What OS are you using?
Cheers
Jeremy