I'd start at the client, and make sure that you can telnet to the server on port 1984. Check also the values of $XYMSRV, $XYMSERVERS and $XYMONDPORT from within xymoncmd, like so:
$ echo 'echo XYMSRV=$XYMSRV XYMSERVERS=$XYMSERVERS XYMONDPORT=$XYMONDPORT' | ~xymon/client/bin/xymoncmd
Either XYMSRV or XYMSERVERS should have the IP address of your Xymon server.
You should also be able to do this:
$ echo '$XYMON $XYMSRV "hostinfo host=$MACHINE"' | ~xymon/client/bin/xymoncmd
This should dump the section of your hosts.cfg file from your server related to the Xymon client on which you're running your command. If you get nothing, you have a problem either with the local configuration or a mis-match between the host name as it is known on Xymon client vs Xymon server.
In the latter case, this should at least give you something:
$ echo '$XYMON $XYMSRV "hostinfo"' | ~xymon/client/bin/xymoncmd
On the Xymon server side, you could run tcpdump or snoop to capture Xymon packets and confirm they are being received by the Xymon server.
To confirm client messages are being processed, run this on the Xymon server:
$ su - xymon -c '~xymon/server/bin/xymoncmd xymond_channel --channel=client --filter=10.1.2.3 cat'
The filter can be anything that matches the first line of a client message, which typically contains the IP address and name of the client that is sending the message.
If you get something (might have to wait up to 5 minutes) then you know that xymond has received and processed the client message.
J
On 20 February 2013 10:23, Mills, David (IS) <David.Mills at ngc.com> wrote:
Jeremy / Dan –****
I think you’re on the right track. How can I check from the server side to make sure current data has arrived for the expected tests?****
david****
*From:* Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] *Sent:* Tuesday, February 19, 2013 5:16 PM *To:* Mills, David (IS) *Cc:* xymon at xymon.com *Subject:* EXT :Re: [Xymon] What tests are coming from a client?****
David****
Those tests that are showing are server-side "probe" tests. They can work even if the target host is not running a Xymon client, and they involve the Xymon server (specifically xymonnet) sending ping packets and attempting TCP socket connections.****
The other tests you want (CPU, memory, iostat) require the Xymon client to be running on the host. If you have that installed and running, it might not be sending the client-side messages to the server, and you should try to find out why. Start by checking your ghost client report.****
Cheers****
Jeremy****
On 20 February 2013 09:49, Mills, David (IS) <David.Mills at ngc.com> wrote:*
Hi, all…****
My boss just walked up and asked me “why all the tests aren’t available for this host on Xymon?” I had to confess I didn’t know the answer and am hoping you can help.****
The entry for the host in hosts.cfg is:****
<ip> <hostname> # ssh ntp TRENDS:*,zonestat:zonestatcpu|zonestatmem|zonestatnproc|zonestatsize|zonersssize
What shows on the screen is just the results from ntp, ssh, info and trends. ****
For the life of me, I can’t get it to display cpu, memory, mem2, iostat, or any of the other usual column “tests”. I’ve tried using the following configuration variations in hosts.cfg, all with the same results:****
<ip> <hostname> #****and ****
<ip> <hostname> # cpu disk iostat iostat2 mem memory ntp sshTRENDS:*,zonestat:zonestatcpu|zonestatmem|zonestatnproc|zonestatsize|zonersssize
but I can’t get more than the original four columns mentioned above to populate.****
It is painfully obvious to me at this point that I do not fully understand the rules at work as to what causes columns to appear / disappear. ****
Help? / Thanks!****
david****
*David Mills* Systems Administrator *Northrop Grumman* **** 512-595-1238 david.mills at ngc.com **** **** **** **** _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon**** ** **