<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Courier; font-size: 12pt; color: #006600'><style>p { margin: 0; }</style><div style="font-family: Courier; font-size: 12pt; color: #006600"><style>p { margin: 0; }</style><div style="font-family: Courier; font-size: 12pt; color: #006600">I think I was wrong. I the two servers are behaving differently <br>because they were configured differently. The server misbehaving was<br>actually configured (analysis.cfg) to see a performance alert.<br><br>The server that was not reporting red properly was reporting yellow <br>and the yellow masked the red status.<br><br>It seems a yellow status (that I configured in analysis.cfg) will <br>override a red status (ie. service failure). <br><br>Can anyone confirm or explain this?<br><br><br>cheers,<br><br>Troy<br><br><br><br>----- Original Message -----<br>From: "Troy Adams" <troy@athabascau.ca><br>To: "Phil Crooker" <Phil.Crooker@orix.com.au><br>Cc: xymon@xymon.com<br>Sent: Thursday, June 30, 2011 10:18:53 AM GMT -07:00 US/Canada Mountain<br>Subject: Re: [Xymon] httpstatus inconsistency<br><br><style>p { margin: 0; }</style><div style="font-family: Courier; font-size: 12pt; color: #006600">> looks like they will be overwriting each other<br>They don't overwrite; xymon supports this.<br><br>> If the above changes don't fix the problem, try turning up the<br>> debugging (in tasks.cfg) and see if you can spot what is happening.<br>Thanks, I'm off to try it.<br><br>If you want to try the multi-URL yourself then here is a simple test<br>framework (/var/www/cgi-bin/dbB.pl) that I employ to mess with HTTP <br>status:<br><div style="margin-left: 40px;">#!/usr/bin/perl -w<br><br>use CGI qw/:standard/;<br><br>print header('text/html',"200 Everything is great");<br></div><br><br><br>cheers,<br><br>Troy<br><br><br>----- Original Message -----<br>From: "Phil Crooker" <Phil.Crooker@orix.com.au><br>To: "Troy Adams" <troy@athabascau.ca><br>Cc: xymon@xymon.com<br>Sent: Tuesday, June 28, 2011 5:35:52 PM GMT -07:00 US/Canada Mountain<br>Subject: Re: [Xymon] httpstatus inconsistency<br><br>Hi Troy,<br><br>Yes I understand you are getting different responses from the different<br>URLs. The problem is first that you have two http tests for the same<br>host. You haven't put your exact config in your question, but in your<br>example:<br><br>>> 192.168.0.29 camilla # postgresql \ <br>>> http://MyUrlA \ <br>>> httpstatus=dbB;https://MyUrlB;200 \ <br>>> httpstatus=dbC;https://MyUrlC;200 \ <br>>> http://MyUrlD <br><br><br>UrlA and UrlD will both show up under the same test name "http" on the<br>web page. To me it looks like they will be overwriting each other at the<br>minimum. I'm fairly new at xymon, but I'd say to overcome this you need<br>to have the second http test attached to another host so they are<br>reported separately. Or you could use a third httpstatus test rather<br>than just http.<br><br>The second problem I saw in your example was you don't have a trailing<br>semicolon on your httpstatus lines, there is another field there that<br>needs to be represented: <br><br> httpstatus[=COLUMN];URL;okstatusexpr;notokstatusexpr<br><br>I tried your example setup on our server and don't have the<br>inconsistent error reporting you complain of, so I think there is some<br>syntactical error in your hosts.cfg.<br><br>If the above changes don't fix the problem, try turning up the<br>debugging (in tasks.cfg) and see if you can spot what is happening.<br><br>cheers, Phil<br><br><br>>>> On 29/06/2011 at 2:43 AM, in message<br><2010869917.4926371309279414670.JavaMail.root@amundsen.cs.athabascau.ca>,<br>Troy<br>Adams <troy@athabascau.ca> wrote:<br>> Thanks Phil, <br>> <br>> I do indeed have multiple http tests for the same host that go to <br>> different URLs on the same host. I know it looks funny at first but <br>> the reason for this is by design. You see, the application running <br>> behind the apache webserver on this host is programmed to hand out a<br><br>> different status on each URL that indicates the status of the<br>database <br>> yet further behind the application. <br>> <br>> For example, database dbB, is shown to be up and running if (and <br>> only if) the fetch of URL https://MyUrlB returns an HTTP Status of <br>> 200. That is to say, if the application get's a database exception <br>> then it is to throw a non-200 status. <br>> <br>> This hosts.cfg entry does work well but it works one way on one <br>> monitoring server and the other way on the other monitoring server: <br>> <br>>> The strange thing, is that when dbC fails with a non 200.... <br>>> on monitor3 dbC and http tests show red <br>>> on monitor5 dbC shows red and http shows green <br>> <br>> <br>> cheers, <br>> <br>> Troy <br>> <br>> <br>> <br>> ----- Original Message ----- <br>> From: "Phil Crooker" <Phil.Crooker@orix.com.au> <br>> To: "Troy Adams" <troy@athabascau.ca>, xymon@xymon.com <br>> Sent: Tuesday, June 28, 2011 1:16:44 AM GMT -07:00 US/Canada Mountain<br><br>> Subject: Re: [Xymon] httpstatus inconsistency <br>> <br>> A rather odd thing I see in your example - you have two http tests<br>for <br>> the same host. If you want to have both I would think you'd need to <br>> rename one of them by doing a separate portocols.cfg entry or putting<br>it <br>> under a differnet hostname. <br>> <br>> It seems to me that you probably have some syntax error in your <br>> hosts.cfg file to cause the different results. <br>> <br>> cheers, Phil <br>> <br>> <br>>>>> On 28/06/2011 at 4:03 AM, in message <br>><br><1205542418.4630071309197825488.JavaMail.root@amundsen.cs.athabascau.ca>,<br><br>> Troy <br>> Adams <troy@athabascau.ca> wrote: <br>>> I have two servers (monitor5 and monitor3) running Xymon 4.3.2 that<br><br>> both have <br>>> the same hosts.cfg entries for a particular host. The entry uses the<br><br>> <br>>> httpstatus test and goes like this: <br>>> <br>>> <br>>> 192.168.0.29 camilla # postgresql \ <br>>> http://MyUrlA \ <br>>> httpstatus=dbB;https://MyUrlB;200 \ <br>>> httpstatus=dbC;https://MyUrlC;200 \ <br>>> http://MyUrlD <br>>> <br>>> The strange thing, is that when dbC fails with a non 200.... <br>>> on monitor3 dbC and http tests show red <br>>> on monitor5 dbC shows red and http shows green <br>>> <br>>> Why do the two monitoring servers behave differently? <br>>> Any idea where to look? <br>>> <br>>> <br>>> thanks, <br>>> <br>>> Troy <br>> <br>> -- <br>> <br>> This message from ORIX Australia might contain confidential and/or <br>> privileged information. If you are not the intended recipient, any<br>use, <br>> disclosure or copying of this message (or of any attachments to it)<br>is <br>> not authorised. <br>> <br>> If you have received this message in error, please notify the sender<br><br>> immediately and delete the message and any attachments from your <br>> system. Please inform the sender if you do not wish to receive future<br><br>> communications by email. <br>> <br>> ORIX handles personal information according to a Privacy Policy that<br>is <br>> consistent with the National Privacy Principles. Please let us know<br>if <br>> you would like a copy. It is also available at http://www.orix.com.au<br>. <br>> <br>> <br>> <br>> -- <br>> This communication is intended for the use of the recipient to<br>whom it<br>> is addressed, and may contain confidential, personal, and or<br>privileged<br>> information. Please contact us immediately if you are not the<br>intended<br>> recipient of this communication, and do not copy, distribute, or<br>take<br>> action relying on it. Any communications received in error, or<br>> subsequent reply, should be deleted or destroyed.<br>> ---<br><br></div>
<br>_______________________________________________
Xymon mailing list
Xymon@xymon.com
http://lists.xymon.com/mailman/listinfo/xymon
</div></div></div></body></html>