What tests are coming from a client?
list David Mills
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 ssh TRENDS:*,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
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid
list Dan McDonald
On 2/19/13 4:49 PM, "Mills, David (IS)" <user-eb64c112f0e9@xymon.invalid> wrote:
Hi, allS 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.
Make sure the client is actually running on the host Check ghosts to see if the hostname might not match the line in hosts.cfg -- Daniel J McDonald, CCIE # 2495, CISSP # 78281
list Roland Soderstrom
Hi, Sounds like you have a group-only setting in the hosts file. group-only ntp|ssh|info|trends <ip> <host> # <ip> <host> # <ip> <host> # Maybe change to group-compress or comment out the group-only line See the hosts man page for different options. - Roland
▸
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Mills, David (IS)
Sent: Wednesday, 20 February 2013 9:50 AM
To: xymon at xymon.com
Subject: [Xymon] What tests are coming from a client?
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 ssh TRENDS:*,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
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>
list Jeremy Laidman
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) <user-eb64c112f0e9@xymon.invalid> 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 ssh
TRENDS:*,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*
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid
list David Mills
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:user-71895fb2e44c@xymon.invalid]
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) <user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>> 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 ssh TRENDS:*,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
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>
list Ryan Novosielski
Like he said, check the ghost client report and make sure your client software is even running at all on the client machine.
▸
From: Mills, David (IS) [mailto:user-eb64c112f0e9@xymon.invalid]
Sent: Tuesday, February 19, 2013 06:23 PM
To: Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
Cc: xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] EXT :Re: What tests are coming from a client?
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:user-71895fb2e44c@xymon.invalid]
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) <user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>> 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 ssh TRENDS:*,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
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>
list David Mills
Many thanks to all who replied: you were right on the money! FWIW, can anyone point out where I can look on the server side to make sure current data has arrived for the expected tests? Thanks! david
▸
From: Novosielski, Ryan [mailto:user-ae4522577e16@xymon.invalid]
Sent: Tuesday, February 19, 2013 5:27 PM
To: Mills, David (IS); 'user-71895fb2e44c@xymon.invalid'
Cc: 'xymon at xymon.com'
Subject: Re: [Xymon] EXT :Re: What tests are coming from a client?
Like he said, check the ghost client report and make sure your client software is even running at all on the client machine.
From: Mills, David (IS) [mailto:user-eb64c112f0e9@xymon.invalid]
Sent: Tuesday, February 19, 2013 06:23 PM
To: Jeremy Laidman <user-71895fb2e44c@xymon.invalid<mailto:user-71895fb2e44c@xymon.invalid>>
Cc: xymon at xymon.com<mailto:xymon at xymon.com> <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: Re: [Xymon] EXT :Re: What tests are coming from a client?
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:user-71895fb2e44c@xymon.invalid]
Sent: Tuesday, February 19, 2013 5:16 PM
To: Mills, David (IS)
Cc: xymon at xymon.com<mailto: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) <user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>> 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 ssh TRENDS:*,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
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>
list Adam Goryachev
▸
On 20/02/13 10:35, Mills, David (IS) wrote:
Many thanks to all who replied: you were right on the money! FWIW, can anyone point out where I can look on the server side to make sure current data has arrived for the expected tests?
I know, but please, make it easier for people to help you. I know, but my mail client just does it that way.. It makes it hard to read Why not? Can we all please try to remember not to top post? In answer to your question, I'd just use tcpdump to verify it from the server if you don't have access to the client. tcpdump -tn -i ethX -s0 -A host 10.1.1.1 and port 1984 Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au
list Jeremy Laidman
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) <user-eb64c112f0e9@xymon.invalid> 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:user-71895fb2e44c@xymon.invalid]
*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) <user-eb64c112f0e9@xymon.invalid> 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 ssh
TRENDS:*,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* ****
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid ****
****
****
****
** **
list David Mills
Excellent tips, Jeremy! Thanks! ;-)
▸
From: Jeremy Laidman [mailto:user-71895fb2e44c@xymon.invalid]
Sent: Wednesday, February 20, 2013 9:15 PM
To: Mills, David (IS)
Cc: xymon at xymon.com
Subject: Re: EXT :Re: [Xymon] What tests are coming from a client?
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) <user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>> 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:user-71895fb2e44c@xymon.invalid<mailto:user-71895fb2e44c@xymon.invalid>]
Sent: Tuesday, February 19, 2013 5:16 PM
To: Mills, David (IS)
Cc: xymon at xymon.com<mailto: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) <user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>> 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 ssh TRENDS:*,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
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid<mailto:user-eb64c112f0e9@xymon.invalid>
list Ryan Novosielski
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
▸
On 02/19/2013 07:19 PM, Adam Goryachev wrote:On 20/02/13 10:35, Mills, David (IS) wrote:Many thanks to all who replied: you were right on the money! FWIW, can anyone point out where I can look on the server side to make sure current data has arrived for the expected tests?I know, but please, make it easier for people to help you. I know, but my mail client just does it that way.. It makes it hard to read Why not? Can we all please try to remember not to top post? In answer to your question, I'd just use tcpdump to verify it from the server if you don't have access to the client. tcpdump -tn -i ethX -s0 -A host 10.1.1.1 and port 1984
Some mail clients make it damn near impossible not to top post. Blackberry's comes to mind. As long as you see the data under one of the tests on the Xymon server and you check the date of the data, you'll see it's arrived. The client-side tests are the same by default unless you add one. Get one working and you'll see which tests are client side (you can make it even more obvious by setting up no server side tests -- remember to add "noconn"). - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEmRHMACgkQmb+gadEcsb7BMACfVNA+YRZnLruCkT7enr9XPXrk 6TYAnA5TygITUGn5seD7+UMMOXEG8LD8 =na9a -----END PGP SIGNATURE-----