[Xymon] Bogus hosts filling up alert.log

[Mills,David (HHSC Contractor)]

Well, John, I added a bogus entry to what we call our "orphans" page -- part of the hosts.cfg hierarchy -- culled from the current ghostlist report, so Xymon will officially have it in the hosts.cfg hierarchy.

   $ tail -1 orphaned-hosts.cfg
   10.11.22.245    0FS_96_192_168_22_1__export_ # noconn

   $ pkill -HUP 'xymond '

Perhaps because this is not really a host you can interact with (hence the "noconn" tag) Xymon claims it still doesn't know about this host:

   $ /usr/share/xymon/bin/xymon localhost "xymondboard  host=0FS_96_192_168_22_1__export_"
   $ 


~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
David Mills
Systems Administrator
Northrop Grumman
(512) 595-1238 (mobile)


-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of John Thurston
Sent: Tuesday, October 31, 2017 4:00 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Bogus hosts filling up alert.log


On 10/31/2017 12:31 PM, Mills,David (HHSC Contractor) wrote:
> This “host” is not a real client host but an artifact I’ve created on 
> the server side to represent a file system I’m monitoring in a 
> server-side ext script, so I know it is not announcing it’s presence 
> over port 1984. For the life of me I can’t figure out where the alerts 
> daemon is running across this hostname.

Based on the output of your interactive run, I suggest the host named "0FS_94_192_168_22_1__export_" is not defined in your hosts.cfg, but the xymon server is seeing messages being sent to it under this name.

Does it appear in your 'ghost report'?
If you define this name in hosts.cfg, do the nasty messages cease?

--
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska
_______________________________________________
Xymon mailing list
Xymon at xymon.com
http://lists.xymon.com/mailman/listinfo/xymon