DOWNTIME tag question

5 messages in this thread

list Eric Meddaugh · Thu, 28 Sep 2006 08:52:52 -0400 ·

 

I'm just starting to use Hobbit for monitoring.  The DOWNTIME tag I have
a question with.  I had this:

 
129.21.35.49    sc3oracle02     # ssh oracle:COBDPROD
DOWNTIME=*:0244:0546:Backups COMMENT:"<font size=-1>cobddb</font>

 
The Database went down at 2:45am, however things went Red.  I see this
in the hobbitd.log:

 
2006-09-28 02:44:33 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:37 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:41 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:41 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:46 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:47 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:49 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:49 Invalid timespec - expected 4 digits, got: 'Backups'

 
So I thought maybe it was Backups was not quoted, so I changed it to:

 
129.21.35.49    sc3oracle02     # ssh oracle:COBDPROD
DOWNTIME=*:0244:0546:"Backups" COMMENT:"<font size=-1>cobddb</font>

 
I then extended the Endtime and shutdown the DB, I still got this error:

 
2006-09-28 08:11:32 Invalid timespec - expected 4 digits, got: 'Backups'

 
However this time it appeared that it was blue and disabled.

 
My question is more of a clarification.  I have not tried to put in
DOWNTIME=oracle:*:0244:0546:"Backups"

 
Can someone clear up what is happening and how it should work?

 
Thanks.

 
---Eric

list Eric Meddaugh · Wed, 4 Oct 2006 11:11:29 -0400 ·

 

Just wondering if anyone had more experience with the DOWNTIME tag.

▸ quoted from Eric Meddaugh


 
I'm just starting to use Hobbit for monitoring.  The DOWNTIME tag I have
a question with.  I had this:

 
129.21.35.49    sc3oracle02     # ssh oracle:COBDPROD
DOWNTIME=*:0244:0546:Backups COMMENT:"<font size=-1>cobddb</font>

 
The Database went down at 2:45am, however things went Red.  I see this
in the hobbitd.log:

 
2006-09-28 02:44:33 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:37 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:41 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:41 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:46 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:47 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:49 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:49 Invalid timespec - expected 4 digits, got: 'Backups'

 
So I thought maybe it was Backups was not quoted, so I changed it to:

 
129.21.35.49    sc3oracle02     # ssh oracle:COBDPROD
DOWNTIME=*:0244:0546:"Backups" COMMENT:"<font size=-1>cobddb</font>

 
I then extended the Endtime and shutdown the DB, I still got this error:

 
2006-09-28 08:11:32 Invalid timespec - expected 4 digits, got: 'Backups'

 
However this time it appeared that it was blue and disabled.

 
My question is more of a clarification.  I have not tried to put in
DOWNTIME=oracle:*:0244:0546:"Backups"

 
Can someone clear up what is happening and how it should work?

 
Thanks.

 
---Eric

list Henrik Størner · Wed, 4 Oct 2006 17:42:41 +0200 ·

▸ quoted from Eric Meddaugh

On Wed, Oct 04, 2006 at 11:11:29AM -0400, Eric Meddaugh wrote:

I'm just starting to use Hobbit for monitoring.  The DOWNTIME tag I have
a question with.  I had this:

129.21.35.49    sc3oracle02     # ssh oracle:COBDPROD
DOWNTIME=*:0244:0546:Backups COMMENT:"<font size=-1>cobddb</font>

The Database went down at 2:45am, however things went Red.  I see this
in the hobbitd.log:

2006-09-28 02:44:33 Invalid timespec - expected 4 digits, got: 'Backups'

Something appears to be wrong in how Hobbit handles this - your
configuration looks ok, so it should have been blue instead. 

I'll check it.


Regards,
Henrik

list Mark Chastain · Wed, 4 Oct 2006 13:19:06 -0400 ·

I just put this is yesterday and tested.  It seemed to work.

 
192.168.xx.xx   hostname # DOWNTIME=*:0100:0535

 
I tried putting a tag at the end.  In quotes, not in quotes ect.  It did not
work.  Adding 

the proc modifier seemed to work.  We took it off as procs was the only
thing we had this 

host.

 
Hope this helps

Mark Chastain

▸ quoted from Eric Meddaugh

-----Original Message-----
From: Eric Meddaugh [mailto:user-4e1e735fdc96@xymon.invalid] 
Sent: Wednesday, October 04, 2006 11:11 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Re: DOWNTIME tag question

Just wondering if anyone had more experience with the DOWNTIME tag.  

I'm just starting to use Hobbit for monitoring.  The DOWNTIME tag I have a
question with.  I had this:

129.21.35.49    sc3oracle02     # ssh oracle:COBDPROD
DOWNTIME=*:0244:0546:Backups COMMENT:"<font size=-1>cobddb</font>

The Database went down at 2:45am, however things went Red.  I see this in
the hobbitd.log:

2006-09-28 02:44:33 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:37 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:41 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:41 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:46 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:47 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:49 Invalid timespec - expected 4 digits, got: 'Backups'

2006-09-28 02:44:49 Invalid timespec - expected 4 digits, got: 'Backups'

So I thought maybe it was Backups was not quoted, so I changed it to:

129.21.35.49    sc3oracle02     # ssh oracle:COBDPROD
DOWNTIME=*:0244:0546:"Backups" COMMENT:"<font size=-1>cobddb</font>

I then extended the Endtime and shutdown the DB, I still got this error:

2006-09-28 08:11:32 Invalid timespec - expected 4 digits, got: 'Backups'

However this time it appeared that it was blue and disabled.

My question is more of a clarification.  I have not tried to put in
DOWNTIME=oracle:*:0244:0546:"Backups"

Can someone clear up what is happening and how it should work?

Thanks.

---Eric


This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.

list Henrik Størner · Wed, 4 Oct 2006 21:52:39 +0200 ·

▸ quoted from Mark Chastain

On Wed, Oct 04, 2006 at 01:19:06PM -0400, Chastain, Mark wrote:

I just put this is yesterday and tested.  It seemed to work.

192.168.xx.xx   hostname # DOWNTIME=*:0100:0535

I tried putting a tag at the end.  In quotes, not in quotes ect.  It did not
work.  Adding the proc modifier seemed to work.  We took it off as procs 
was the only thing we had this host.


I've gone over the code, and it doesn't quite match what the docs say.
You can use either
   DOWNTIME=*:0244:2046
or
   DOWNTIME=*:*:0244:2046:Backups

So if you specify a cause, you must also specify which columns it
is for. This is not what the docs say, so I'll have to update one
of them. Probably the code :-)


Regards,
Henrik

DOWNTIME tag question 🔗 link

DOWNTIME tag question