[Xymon] Can't clear ghost clients - RESOLVED

[Bill Arlofski]

On 03/12/14 12:57, Kris Springer wrote:
> I still monitor the ghost machines.  I’ve just given them different
> names.  I just checked each host and the name defined in it’s xymon
> client host file matches the current server host file. 
> 
>  
> 
> I seem to have been able to fix the issues.  For each one I just added
> the CLIENT: option into the server hosts.cfg file.
> 
> CLIENT:Buzzard
> 
>  
> 
> The xymon server seems to want the real hostname of each machine instead
> of the name I’m defining in the client config file.  So, I guess a
> workaround is to use the CLIENT: option.  I’ve had to use that also for
> some special hosts that I have custom scripts running on.  If I didn’t
> add the CLIENT: option the data would not post to the server webpage.
> 

Hi Kris

I was using the CLIENT: option for a while, and think I still am in come
cases, but I have seen machines report as FQDN, and then later just the
hostnane (or vice versa), so on the client, in the rc.local (or wherever
the Xymon client is being started from depending on distro), I do this:

su - xymon -c "~/client/runclient.sh restart --hostname=FQDN"

So, all my clients always report back as the FQDN that I define there.

Of course, if a hostname needs to be changed, so would that line, but I
have rarely run into that issue, and that could be automated by using
--hostname=`hostname -f`  instead of hard-coding it.

Seems with Xymon there are many options to accomplish a desired outcome.

:)

Hope this helps.


--
Bill Arlofski
Reverse Polarity, LLC