Can't clear ghost clients - RESOLVED
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.
Thank you.
Kris Springer
=======================
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Adam Goryachev Sent: Tuesday, March 11, 2014 9:57 PM To: xymon at xymon.com Subject: Re: [Xymon] Can't clear ghost clients
On 12/03/14 15:04, Kris Springer wrote:
I've got 6 ghost clients listed on my server webpage. I have a clean hosts.cfg file that definitely does not contain any of the names in the ghost list. The ghost names are from many months ago when I first setup the server. I've since change the names. I've attempted to clear the ghosts using the following commands but it doesn't clear anything. Buzzard is one of the hostnames in question.
#cd /usr/lib/xymon/server/bin
#xymon 127.0.0.1 "drop Buzzard"
Anyone have a clue as to how to clear old ghosts and/or where to find the pesky files that are causing it?
ghosts are there *because* you do not have them in your config file. They are "generated" by clients reporting status with that name. You should be able to determine where these reports are coming from based on the names and/or source information on the ghost report. If the client stops reporting, it will be removed from the ghost report after 5 minutes (I assume this is actually the timeout value of the status which is usually 5 minutes).
Worst case, you can firewall port 1984 to block the incoming status reports, or use tcpdump to determine where they are coming from.
Hope this is useful/helpful.
Regards, Adam
-- Adam Goryachev Website Managers www.websitemanagers.com.au
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
participants (2)
-
kspringer＠innovateteam.com
-
waa-hobbitml＠revpol.com