Henrik,

I knew I could count on you to help me see the light. I hadn't even considered checking the status and acting on the result.

Just out of curiosity, Big Brother didn't act this too did it?

Henrik Stoerner wrote:

On Wed, Nov 09, 2005 at 12:49:57PM -0500, Steve wrote:

...

I wrote a client script to monitor an application, added to the clientlaunch.cfg file restarted hobbit, the monitor works well

Because the application I am monitoring is faulty I added to the client script a section of code to start up the application should it fail. I shut down the application and Hobbit starts it up ... Cool.

To avoid having the application start up during the backup or maintenance window I disable the client script.

I ran a test backup to be sure it worked, but it appears that Hobbit executes the client script even when the test is disabled, and the application goes from blue to red to green.

You're right that Hobbit runs the client script regardless of whether the status that the script reports is disabled or not. hobbitlaunch which runs the script simply has no idea what status column(s) your script might report.

...

So now the 64K question ... what can I change so the test does not run when disabled or ... where did I error?

Have your script check if the test is disabled, and abort if it is. Something like this:

STATUS=$BB $BBDISP "query $MACHINE.mytest" | awk '{print $1}' if [ "$STATUS" = "blue" ]; then exit 0; fi

The bb(1) man-page has some more examples of how you can use the "query" command.

Regards, Henrik

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Steve DiSorbo System Programmer Yale University ITS, AM&T Library Systems Voice (203) 432-6694 Fax (203) 436-4067 steve.disorbo at yale.edu http://www.library.yale.edu/

I just looked at the history logs on my BB server and see that ... yep you're right !!! not that I didn't believe you, but I was disillusioned.

Henrik Stoerner wrote:

Hi Steve,

On Wed, Nov 09, 2005 at 04:30:41PM -0500, Steve wrote:

...

I knew I could count on you to help me see the light. I hadn't even considered checking the status and acting on the result.

Just out of curiosity, Big Brother didn't act this too did it?

BB would also run the script regardless of whether that status was disabled or not. And BB doesn't have any way for a client script to check if the status is disabled - I added this in Hobbit because I needed it for much the same reasons that you do.

Regards, Henrik

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

-- Steve DiSorbo System Programmer Yale University ITS, AM&T Library Systems Voice (203) 432-6694 Fax (203) 436-4067 steve.disorbo at yale.edu http://www.library.yale.edu/

Steve a écrit :

So ...

I add the code you suggest, query bb for status and test for blue, but it is never blue, even when disabled.

Hi

same here (with Hobbit 4.1.2), it returns the "true" color of the test, and not blue :

$ ./bb localhost "query dashboard.conn" red <!-- [flags:ordAstILe] --> Thu Nov 10 16:53:30 2005 conn NOT ok

It works fine on my bbgen 3.6 server :

$ ./bb localhost "query dashboard.conn" blue Wed Oct 26 18:24:17 2005 OFFLINE UNTIL Mon Jul 21 18:24:17 2008

--

Frédéric Mangeant

Steria EDC Sophia-Antipolis

On Mon, Nov 14, 2005 at 05:18:41PM +0100, Frédéric Mangeant wrote:

...

same here (with Hobbit 4.1.2), it returns the "true" color of the test, and not blue :

$ ./bb localhost "query dashboard.conn" red <!-- [flags:ordAstILe] --> Thu Nov 10 16:53:30 2005 conn NOT ok

It works fine on my bbgen 3.6 server :

$ ./bb localhost "query dashboard.conn" blue Wed Oct 26 18:24:17 2005 OFFLINE UNTIL Mon Jul 21 18:24:17 2008

using "hobbitdlog" (from 4.1.2p1) it works fine, the blue color shows up on the first line :

Eureka - I should have thought of that right away.

When hobbitd responds to a "query" command, it just spits back the first line of the last status message it received. But that will be the "raw" status message - i.e. it will show red, because a disable is handled through some internal status flags in Hobbit that aren't reflected in the status message text hobbitd stores.

That is why when you look at the detailed status view for something that is disabled, you'll see the "true" status below the "Disabled until .... " message.

This patch should fix it - against 4.1.2p1.

Regards, Henrik

We are undergoing some restructuring among support teams, and are separating and defining some responsibilities a little better. System admins will be called on system specific problems, while DBAs and apps support people will be called on others. One of my frequent complaints in the past has been getting calls on filled file systems containing Oracle trace files, dumps, logs, temporary files etc. that I don't feel I should be making decisions to remove, gzip etc.

That is changing - DBAs will be called on those file systems in other environments where we're using HP's ITO (aka Vantage Point / OpenView, call it what you will).

I want to try to do the same on the servers I am monitoring with hobbit. Is there any way, or a possibility of a feature request that would allow me to specify alerts to me for all filesystems, other than a few specific ones? E.g. using a modified version of the hobbit-alerts page example:

HOST=www.foo.com MAIL dba at foo.com SERVICE=disk.ora-db,disk.ora-idx,disk.ora-log REPEAT=1h MAIL unixsupport at foo.com SERVICE=cpu,disk,memory