Xymon Mailing List Archive search

Nothing showing except CONN for one host

5 messages in this thread

list Wes Neal · Wed, 18 Jun 2014 13:48:05 -0400 ·
I have a single host that won’t show anything but the CONN column on the display page for it.  It is running a client, but nothing is being populated on the server end.  I have many, many other clients installed, some in this same location and on the same network.  Normally this might be a short name vs FQDN name in bb-hosts, but I have both the short and fqdn in the file currently.  I am running an older version of Xymon 4.2 still, but again no issue with other hosts.  Any other idea what might be causing the DISPLAY not to be populated?

Thanks
list Bill Arlofski · Wed, 18 Jun 2014 15:31:48 -0400 ·
quoted from Wes Neal
On 06/18/14 13:48, Neal, Jonathan W wrote:
I have a single host that won’t show anything but the CONN column on the
display page for it.  It is running a client, but nothing is being
populated on the server end.  I have many, many other clients installed,
some in this same location and on the same network.  Normally this might
be a short name vs FQDN name in bb-hosts, but I have both the short and
fqdn in the file currently.  I am running an older version of Xymon 4.2
still, but again no issue with other hosts.  Any other idea what might
be causing the DISPLAY not to be populated?

 
Thanks
Hi Johnathan,

You should check under Reports --> Ghost Clients to see if the system is
sending in reports under a different hostname, or different fqdn than
your bb-hosts is configured to be expecting.

If it is, you can do one of a couple things:

1. on the client, add a --hostname host.example.com  to the list that
starts your runclient.sh script and set host.example.com to whatever
FQDN you have in your bb-hosts file

2. On the client's line in bb-hosts add the CLIENT option and define it
as whatever the Ghost Client report shows it to be reporting as.


Other possibility is that there is a firewall (host based or otherwise)
blocking that one client from connecting to your server on port 1984/TCP

And final possibility is that the client is misconfigured and is trying
to send its reports to 127.0.0.1 or somewhere else.   Check the
~xymon/client/hobbitclient.cfg file (pretty sure that is what it was
called back then)


Hope this helps!

Bill


--
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --
list Wes Neal · Wed, 18 Jun 2014 15:41:05 -0400 ·
You should check under Reports --> Ghost Clients to see if the system is sending in reports under a different hostname, or different fqdn than your bb-hosts is configured to be expecting.

------There is no ghost report in version 4.2 that I see.  I was looking to see if I could just download that CGI script but haven't been able to find it yet.
quoted from Bill Arlofski

If it is, you can do one of a couple things:

1. on the client, add a --hostname host.example.com  to the list that starts your runclient.sh script and set host.example.com to whatever FQDN you have in your bb-hosts file

------I will look at this possibility if I can figure out if it is a "Ghost" client.


2. On the client's line in bb-hosts add the CLIENT option and define it as whatever the Ghost Client report shows it to be reporting as.

-----Again if I can figure out what it is trying to report as, I will look into this as well.


Other possibility is that there is a firewall (host based or otherwise) blocking that one client from connecting to your server on port 1984/TCP

------no firewall, I have a working machine on IP address away that is working just fine.
quoted from Bill Arlofski

And final possibility is that the client is misconfigured and is trying
to send its reports to 127.0.0.1 or somewhere else.   Check the
~xymon/client/hobbitclient.cfg file (pretty sure that is what it was called back then)

-----I have already verified it has the proper IP in the hobbbitclient.cfg

Thanks for the input!
list Wes Neal · Wed, 18 Jun 2014 15:52:07 -0400 ·
Problem solved.  I should have looked harder at it myself the first time.  I let someone else build the bb-hosts file entry and the hostname was missing a single character.

Thanks
quoted from Wes Neal


-----Original Message-----
From: Neal, Jonathan W 
Sent: Wednesday, June 18, 2014 3:41 PM
To: 'Bill Arlofski'; xymon at xymon.com
Subject: RE: [Xymon] Nothing showing except CONN for one host

You should check under Reports --> Ghost Clients to see if the system is sending in reports under a different hostname, or different fqdn than your bb-hosts is configured to be expecting.

------There is no ghost report in version 4.2 that I see.  I was looking to see if I could just download that CGI script but haven't been able to find it yet.

If it is, you can do one of a couple things:

1. on the client, add a --hostname host.example.com  to the list that starts your runclient.sh script and set host.example.com to whatever FQDN you have in your bb-hosts file

------I will look at this possibility if I can figure out if it is a "Ghost" client.


2. On the client's line in bb-hosts add the CLIENT option and define it as whatever the Ghost Client report shows it to be reporting as.

-----Again if I can figure out what it is trying to report as, I will look into this as well.


Other possibility is that there is a firewall (host based or otherwise) blocking that one client from connecting to your server on port 1984/TCP

------no firewall, I have a working machine on IP address away that is working just fine.

And final possibility is that the client is misconfigured and is trying
to send its reports to 127.0.0.1 or somewhere else.   Check the
~xymon/client/hobbitclient.cfg file (pretty sure that is what it was called back then)

-----I have already verified it has the proper IP in the hobbbitclient.cfg

Thanks for the input!
list Bill Arlofski · Wed, 18 Jun 2014 17:24:00 -0400 ·
quoted from Wes Neal
On 06/18/14 15:52, Neal, Jonathan W wrote:
Problem solved.  I should have looked harder at it myself the first time.  I let someone else build the bb-hosts file entry and the hostname was missing a single character.

Thanks
It's (almost) always the simple things!  :)

Glad you got it sorted out.
quoted from Bill Arlofski


Bill


--
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --