I have been using Xymon sucessfully for several weeks on my local machine as a client / server. I have now attempted to move the client portion to another system. Per the CLIENT.READ me, all I had to do was create a xymon user and copy the /home/xymon/client directory over to the cleint. I started the client and all appeared well.
However, the hostname on that system is generic and doesn't resolve to the correct DNS. In other words the host name on that system (1.2.3.4) is hostname. However, "hostname" resolves over the network as 4.3.2.1. So, when the ping test runs, it runs for 4.3.2.1. Another thing to note is that on the ghost screen, there is a ghost showing as reporting from that host... but also shows that the same host name is a Candidate. How do I tell Xymon that they are the same thing?
Also,
I am having another problem on the client whereas I'm getting a "connection refused" when trying to send the the xymon command. I have to assume this means that this is local to that machine. However, I've got my firewall turned off, so I'm not sure I understand how that can be.
-- Michael Beatty Sherwin-Williams IT Analyst/Developer michael.beatty at sherwin.com 216-515-7374
On Wed, May 16, 2012 at 4:15 AM, Michael Beatty <Michael.Beatty at sherwin.com>wrote: ...
However, the hostname on that system is generic and doesn't resolve to the correct DNS. In other words the host name on that system (1.2.3.4) is hostname. However, "hostname" resolves over the network as 4.3.2.1. So, when the ping test runs, it runs for 4.3.2.1.
You can add "testip" to the hosts.cfg file on the server, and it will use the IP address defined in hosts.cfg rather than what's in the DNS. See the "Testing sites by IP-address" section in the hosts.cfg(5) man page.
Another thing to note is that on the ghost screen, there is a ghost showing as reporting from that host... but also shows that the same host name is a Candidate. How do I tell Xymon that they are the same thing?
Xymon will extract the name from the status message and look it up in the hosts.cfg file, tring to match it exactly. The most common problem with this is when one side uses the FQDN and the other side uses the short name, and this can be remedied by adding a "CLIENT:othername" setting in hosts.cfg. However, in your case it appears that both are the same. I would double-check the status messages as they get to the server with something like this:
sudo -u xymon xymond_channel --channel=status grep "^status"
This will show you every status message coming to the server, including the full hostname being presented (with dots replaced by commas). You can then compare with the entry in hosts.cfg and confirm that they match exactly. You might need to check both status and data channels.
Alternatively, you can add "--ghosts=allow" to the execution of xymond (in tasks.cfg) to let these in, or use "--ghosts=match" to have xymond try to match after stripping the domain names.
I am having another problem on the client whereas I'm getting a "connection refused" when trying to send the the xymon command. I have to assume this means that this is local to that machine. However, I've got my firewall turned off, so I'm not sure I understand how that can be.
What is the command-line you're using for the xymon command? You'd get a "connection refused" message if you're specifying localhost as the second parameter to "xymon" instead of specifying the server IP address (or $XYMSRV).
You might get more information about the problem by appending "--debug".
Cheers Jeremy
participants (2)
-
jlaidman＠rebel-it.com.au
-
Michael.Beatty＠sherwin.com