[Xymon] Double combo's - returning -1 - xymon 4.3.3
Bill Richardson
wrichardson at llbean.com
Thu Sep 15 17:32:51 CEST 2011
Thank you!
-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner
Sent: Wednesday, September 14, 2011 2:22 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Double combo's - returning -1 - xymon 4.3.3
I can almost guarantee it will behave just like the other 4.3.x versions
- there haven't been any changes to that code in quite a while.
A work-around for it might be to split the evaluation of the combo
statuses into two - i.e. run the "combostatus" tool twice with different
config files. The first run does the first level of combos, and the
second run then does the combined combos. Yes it's a kludge, but it may
be an interim solution to the problem.
Alas, the combostatus tool won't let you specify the configuration file
to use, so you'll need to attached patch for that.
Another possible solution would be to not have combostatus do the
processing, but use a script to determine the status. You can get the
color of any status with the xymon "query" command - e.g.
COLOR1=`xymon 127.0.0.1 "query Web1.http"`
COLOR2=`xymon 127.0.0.1 "query Web2.http"`
if test "$COLOR1" = "green" -o "$COLOR2" = "green"
then
xymon 127.0.0.1 "status WebCluster.http green"
else
xymon 127.0.0.1 "status WebCluster.http red"
fi
does the same as the combo-configuration
WebCluster.http = (Web1.http || Web2.http)
So you could script your way through it. That would also allow you to
provide a more meaningful status message.
I will look at what is happening with the nested combo-stuff, but I am
not really happy about how the whole "combostatus" thing works.
Regards,
Henrik
On 13-09-2011 21:23, Bill Richardson wrote:
> The older version of Xymon that I have running 4.3.0.0-beta2 has the same "&unknown" issue. Will let you know how 4.3.5 goes...
>
> -----Original Message-----
> From: Bill Richardson
> Sent: Tuesday, September 13, 2011 9:58 AM
> To: David W Gore; xymon at xymon.com
> Subject: RE: [Xymon] Double combo's - returning -1 - xymon 4.3.3
>
> I was doing some testing of this feature today and notice the same problem. I am testing with 4.3.3. Will be upgrading to 4.3.5 this week and will let you know what I find. If that doesn't work I have an older 4.3.0 that I can test on just to see if maybe something got broken along the way... This is the first time I have ever tested double level combos.
>
> -----Original Message-----
> From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of David W Gore
> Sent: Friday, July 29, 2011 3:17 PM
> To: xymon at xymon.com
> Subject: Re: [Xymon] Double combo's - returning -1 - xymon 4.3.3
>
> Does anyone out there using double leveled combos, combos of combos that work? If so perhaps you could share an example from your config that works? Thanks in advance,
>
> Here is the example from the man pages:
>
> ----
> WebCluster.http = (Web1.http || Web2.http) AppSrvCluster.procs = (AppSrv1.conn&& AppSrv1.procs) || (AppSrv2.conn&&
> AppSrv2.procs)
> Customer.cluster = WebCluster.http&& AppSrvCluster.procs
>
> The first line defines a new test, with hostname "WebCluster" and the columnname "http". It will be green if the http test on either the "Web1" or the "Web2" server is green.
>
> The second line defines a "procs" test for the "AppSrvCluster" host. Each of the AppSrv1 and AppSrv2 hosts is checked for "conn" (ping) and their "procs"
> test. On each host, both of these must be green, but the combined test is green if that condition is fulfilled on just one of the hosts.
>
> The third line uses the two first tests to build a "double combined" test, defining a test that shows the overall health of the system.
> ----
>
> So in theory it should work? For reference we are using Xymon 4.3.3 on RedHat Linux Enterprise 5.7.
>
> ~David
>
> From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Rager, Richard R (Rich)
> Sent: Thursday, June 30, 2011 19:02
> To: xymon at xymon.com
> Subject: [Xymon] Double combo's - returning -1 - xymon 4.3.3
>
> Hi,
>
> Anyone using double combo messages? I was following the man pages, which state they are possible, but my tests calculate "-1" and the color comes out $unknown.
>
> Thu Jun 30 18:43:24 2011
> (iam.db&&gam.db) = (-1&&-1) = 1
> &unknown iam.db
> &unknown gam.db
> Sample config from combo.cfg. I have changed hostnames to protect the innocent...combos based on the values returned by dbcheck.pl...our DB's are served on 4 node Oracle Grid clusters, which is why we have alias' for the DB, such as servername_dbname.
>
> Hostnames are defined in hosts.d as "0.0.0.0 gam # noconn nonongreen noproppurple:*" gam/iam/impact all defined the same in hosts.
>
> iam.db = (servername\_iam.audit&& servername\_iam.conn&& servername\_iam.extent&& servername\_iam.info&& servername\_iam.invobj&& servername\_iam.locks&& servername\_iam.rollback&& servername\_iam.session&& servername\_iam.tblspace&& servername\_iam.trends&&
> servername\_iam.uptime)
>
> gam.db = (servername\_gam.audit&& servername\_gam.conn&& servername\_gam.extent&& servername\_gam.info&& servername\_gam.invobj&& servername\_gam.locks&& servername\_gam.rollback&& servername\_gam.session&& servername\_gam.tblspace&& servername\_gam.trends&&
> servername\_gam.uptime)
>
> These two above work fine. They are single layer combo tests...All my single layer combo tests work.
>
> The double combo is this:
>
> impact.db = (iam.db&& gam.db) - same with our without parenthesys...if I use single ampersand, color propogates up, but staus still shows&unknown.
>
>
> We have tried multiple combinations taking the combo down to barest form, and still get the errors (&unknown).
>
> Log doesn't really help...
>
> combostatus.log.1:21316 2011-06-30 03:58:03 Symbolic 'event.db&&gam.db&&iam.db&&jbpm.db' converted to '-1&&-1&&-1&&-1'
> I put the --debug on the cmd in tasks, and not logging much else helpful.
>
> Appreciate some thoughs or suggestions.
>
> Rich Rager
> VZB
>
>
> ________________________________________
> This message was created by the sender using your @mci.com address. If you wish to continue to receive messages from this sender, please respond informing them to use your @verizonbusiness.com email address.
>
> The mci.com email domain will be decommissioned October 31, 2010.
> Please inform sender to use your @verizonbusiness.com address, if you desire to continue to receive messages from them.
>
> Thank You
>
> Verizon Business Messaging
>
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
More information about the Xymon
mailing list