Services false positive

It's possible to set the host name in bbwin.cfg. You might want to check
the bbwin.cfg files on each machine and make sure you don't find the same
name in each. If you set host name there, and then copy that install to
another machine ....

Thanks,
Larry Barber

On Thu, Feb 21, 2013 at 9:09 AM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid>wrote:

 If I'm not mistaken, there are notes in the client software that say that
that mode is sort of beta/buggy at this point.


 *From*: user-45a831e25f8a@xymon.invalid [mailto:user-45a831e25f8a@xymon.invalid]
*Sent*: Thursday, February 21, 2013 10:08 AM
*To*: Novosielski, Ryan; 'user-ec1bf77b1b44@xymon.invalid' <user-ec1bf77b1b44@xymon.invalid>
*Cc*: 'xymon at xymon.com' <xymon at xymon.com>
*Subject*: RE: [Xymon] Services false positive


Ok, I got it, I switched the servers from central to local and that did
the trick, thanks for all the help guys, much appreciated****

** **

*From:* Novosielski, Ryan [mailto:user-ae4522577e16@xymon.invalid]
*Sent:* Thursday, February 21, 2013 10:01 AM
*To:* Matthew Harris; 'user-ec1bf77b1b44@xymon.invalid'
*Cc:* 'xymon at xymon.com'
*Subject:* Re: [Xymon] Services false positive****

** **

That will only work for server-side tests (that originate from the Xymon
net portion). My guess is you can still solve this problem with a
combination of directives however -- look at the CLIENT directive.
Presuming you can set the client's name in BBWIN to something specific, you
can then use that directive to make the Xymon display associate that
alternate name to it. Seems like a pain in the neck though. Might be worth
it to look into the alternate Windows clients?


 ****

*From*: user-45a831e25f8a@xymon.invalid [mailto:user-45a831e25f8a@xymon.invalid<user-45a831e25f8a@xymon.invalid>]

*Sent*: Thursday, February 21, 2013 09:58 AM
*To*: Steve Holmes <user-ec1bf77b1b44@xymon.invalid>
*Cc*: xymon at xymon.com <xymon at xymon.com>
*Subject*: Re: [Xymon] Services false positive
 ****

It doesn’t look like the testip tag worked, these are windows hosts with
the bbwin 0.13 agent on them.****

** **

*From:* user-5425c7b245e1@xymon.invalid [mailto:user-5425c7b245e1@xymon.invalid<user-5425c7b245e1@xymon.invalid>]
*On Behalf Of *Steve Holmes
*Sent:* Thursday, February 21, 2013 9:56 AM
*To:* Matthew Harris
*Cc:* xymon at xymon.com
*Subject:* Re: [Xymon] Services false positive****

** **

** **

On Thu, Feb 21, 2013 at 9:18 AM, user-45a831e25f8a@xymon.invalid <
user-45a831e25f8a@xymon.invalid> wrote:****

Hey Everyone, I think I found a bug in xymon, I am monitoring a few
hundred servers and I found that servers with similar names but different
purposes are trying to report the same services.  For instance,
XXXXXXXXXXX486 and XXXXXXXXXXX487 is duplicating the service checks for
 XXXXXXXXXXX48.  Is there any way that anyone knows of to get xymon to look
at the entire machine name instead of just the first 12 characters of it?*
***

 ****

 ****


Are the servers in question Solaris zones on the same global zone? If so,
many of the checks will be duplicated. This may also happen with other
virtual environments, but I've only seen it for Solaris zones. In
particular our ESX environment does not have this problem.

Steve

-- ****

If they give you ruled paper, write the other way. -Juan Ramon Jimenez,
poet, Nobel Prize in literature (1881-1958)

I prayed for freedom for twenty years, but received no answer until I
prayed with my legs. -Frederick Douglass, Former slave, abolitionist,
editor, and orator (1817-1895) ****