From eric-list-1@softlution.com Wed Jun 24 08:14:39 2026
From: eric-list-1@softlution.com
To: xymon@xymon.com
Subject: "Disable until OK" doesn't get logged in $BBDISABLED?
Date: Thu, 05 Oct 2006 16:36:28 +0200
Message-ID: <4525186C.1070806@softlution.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8588017718874639356=="

--===============8588017718874639356==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


Hello,


I'm currently upgrading to Hobbit 4.2.0 (our old systems still run
4.0.4) and I have an issue with a DeadCat BB extension called
"show_blue.sh". It turns out that disabling something "until OK" doesn't
write a log in $BBDISABLED, while disabling something with a specific
duration will. Re-enabling such a test by hand will also result in a
"Could not remove disable-file" log entry in the enadis.log file.

show_blue is intended to show all disabled tests in the "All non-green
view" and uses the files in $BBDISABLED to determine which tests are
disabled, the behaviour above makes it impossible for show_blue to
determine all disabled tests.

What can I do to get show_blue working correctly with "disable until OK"?


Best regards,

Eric.


--===============8588017718874639356==--


From henrik@hswn.dk Wed Jun 24 08:14:39 2026
From: henrik@hswn.dk
To: xymon@xymon.com
Subject: [hobbit] "Disable until OK" doesn't get logged in $BBDISABLED?
Date: Thu, 05 Oct 2006 17:16:24 +0200
Message-ID: <20061005151624.GA32538@hswn.dk>
In-Reply-To: <4525186C.1070806@softlution.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0213647454840155324=="

--===============0213647454840155324==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, Oct 05, 2006 at 04:36:28PM +0200, Eric van de Meerakker wrote:

> I'm currently upgrading to Hobbit 4.2.0 (our old systems still run
> 4.0.4) and I have an issue with a DeadCat BB extension called
> "show_blue.sh". It turns out that disabling something "until OK" doesn't
> write a log in $BBDISABLED, while disabling something with a specific
> duration will. Re-enabling such a test by hand will also result in a
> "Could not remove disable-file" log entry in the enadis.log file.

You could call it a bug, but on the other hand the BB compatibility
files have no way of registering the "until-ok" setting.

> show_blue is intended to show all disabled tests in the "All non-green
> view" and uses the files in $BBDISABLED to determine which tests are
> disabled, the behaviour above makes it impossible for show_blue to
> determine all disabled tests.
> 
> What can I do to get show_blue working correctly with "disable until OK"?

How about replacing it ? I don't know what the output from the show_blue
tool looks like, but if you just want an overview of the disabled
statuses then this CGI script will do it:

#!/bin/sh
. /usr/lib/hobbit/server/etc/hobbitcgi.cfg

(echo "<table border=1>"
 /usr/lib/hobbit/server/bin/hobbit-statusreport.cgi \
	--filter="color=blue" --all \
	--heading="Disabled systems" \
	--show-column \
	--show-summary \
	--link \
	--embedded
 echo "</table>") | \
/usr/lib/hobbit/server/bin/bb-webpage --color=blue --hffile=bb

exit 0


Regards,
Henrik



--===============0213647454840155324==--


From rgordonjr@gmail.com Wed Jun 24 08:14:39 2026
From: rgordonjr@gmail.com
To: xymon@xymon.com
Subject: [hobbit] "Disable until OK" doesn't get logged in $BBDISABLED?
Date: Thu, 05 Oct 2006 10:43:02 -0700
Message-ID: <d4f70c240610051043g79557eccw71019ea93fecf408@mail.gmail.com>
In-Reply-To: <20061005151624.GA32538@hswn.dk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5077401492903073456=="

--===============5077401492903073456==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On 10/5/06, Henrik Stoerner <henrik at hswn.dk> wrote:
>
> How about replacing it ? I don't know what the output from the show_blue
> tool looks like, but if you just want an overview of the disabled
> statuses then this CGI script will do it:
>

Thanks for the script Henrik..  Was exactly what I was looking for..  ;)

-- 
--==[ Bob Gordon ]==--

--===============5077401492903073456==--


From eric-list-1@softlution.com Wed Jun 24 08:14:39 2026
From: eric-list-1@softlution.com
To: xymon@xymon.com
Subject: [hobbit] "Disable until OK" doesn't get logged in $BBDISABLED?
Date: Fri, 06 Oct 2006 11:14:06 +0200
Message-ID: <45261E5E.5070409@softlution.com>
In-Reply-To: <20061005151624.GA32538@hswn.dk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7763065742937445449=="

--===============7763065742937445449==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


Hi Henrik,


Henrik Stoerner wrote:
> On Thu, Oct 05, 2006 at 04:36:28PM +0200, Eric van de Meerakker wrote:
> 
>> I'm currently upgrading to Hobbit 4.2.0 (our old systems still run
>> 4.0.4) and I have an issue with a DeadCat BB extension called
>> "show_blue.sh". It turns out that disabling something "until OK" doesn't
>> write a log in $BBDISABLED, while disabling something with a specific
>> duration will. Re-enabling such a test by hand will also result in a
>> "Could not remove disable-file" log entry in the enadis.log file.
> 
> You could call it a bug, but on the other hand the BB compatibility
> files have no way of registering the "until-ok" setting.

OK. It turns out that show_blue only needs the presence of files in
$BBDISABLED to determine which host/test combinations are disabled and
doesn't use the contents at all. It used

	cd $BBDISABLED
	ls > $BLUEFILE

to get a list of hostnames and tests that are disabled, which are then
processed further.

I've replaced the 'ls' command above with this one-liner:

	$BB $BBDISP "hobbitdboard color=blue" | cut -d'|' -f1-2 | \
		sed -e 's/\./,/g' -e 's/|/./g' > $BLUEFILE

This allowed me to leave the rest of the script alone. (I'm not too
worried about performance because we don't monitor very many hosts.)

> 
>> show_blue is intended to show all disabled tests in the "All non-green
>> view" and uses the files in $BBDISABLED to determine which tests are
>> disabled, the behaviour above makes it impossible for show_blue to
>> determine all disabled tests.
>>
>> What can I do to get show_blue working correctly with "disable until OK"?
> 
> How about replacing it ? I don't know what the output from the show_blue
> tool looks like, but if you just want an overview of the disabled
> statuses then this CGI script will do it:
> 
> [script deleted for brevity...]

That does indeed show the information I want, and I could have included
that table in the non-green page, but I prefer the compact layout
show_blue gives me: if there are disabled tests it puts up a separate
hosts/tests grid on the non-green view page, showing all and only the
disabled tests.

We use disable/enable a lot, e.g. for issues we cannot handle ourselves
or which take longer to fix, and I like the constant reminder show_blue
gives us, right on the non-green view page, which tests are disabled.
This makes sure we don't 'forget' about disabled tests...


Thanks Henrik, your reply did point me in the right direction to solve this!


Regards,

Eric.


--===============7763065742937445449==--