No, I didn't see that email come through, thanks. There are no rules above it. I'll have to try testing things.

---Eric

-----Original Message----- From: Trent Melcher [mailto:trent.melcher at sitel.com] Sent: Friday, September 28, 2007 10:14 To: hobbit at hswn.dk Subject: RE: [hobbit] Weird Alerting behavior...bug or expected??

Did you test your configuration as suggested in this reply ?

http://www.hswn.dk/hobbiton/2007/09/msg00333.html

Trent

From: Eric Meddaugh [mailto:etmsys at rit.edu] Sent: Friday, September 28, 2007 7:14 AM To: hobbit at hswn.dk Subject: RE: [hobbit] Weird Alerting behavior...bug or expected??

Just checking to see again if anyone has experienced this issue/problem???  I haven't seen anything about it.

Thanks.

---Eric

From: Eric Meddaugh [mailto:etmsys at rit.edu] Sent: Monday, September 24, 2007 09:18 To: hobbit at hswn.dk Subject: [hobbit] Weird Alerting behavior...bug or expected??

We have the following the the Alerts file:

on-call page

$TSSSYS_ONCALL_DAY=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=10 TIME=W:0800:1700 RECOVERED $TSSSYS_ONCALL_OFF=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=20 TIME=W:1700:0800 RECOVERED $TSSSYS_ONCALL_END=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=20 TIME=06:*:* RECOVERED

$DUPING=%(mxgate)

HOST=$DUPING SERVICE=conn $TSSSYS_ONCALL_DAY $TSSSYS_ONCALL_OFF $TSSSYS_ONCALL_END

We had a host (mxgate03) go down at 3:15am, it sent 1 initial page, but no follow ups.  No repeats.  Does Monday from 12am-8am fall in a "limbo" timeframe where the 2nd rule does not apply since it's not a Weekday after 5pm, but before 8am???   The host was down for over 3 hours without any follow up pages.

Do I need a rule similar to:

$TSSSYS_ONCALL_MON=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=10 TIME=1:0000:0800 RECOVERED

The different rules are suppose to repeat 10 minute during business hours, and 20 minutes off-hours.

Any ideas?  Is this a bug or expected behavior?

Thanks.

---Eric

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

On Fri, 2007-09-28 at 11:08 -0400, Kauffman, Tom wrote:

IIRC there have been problems with crossing over midnight, so you may want to split the second rule to TIME=W:1700:2359 and TIME=W:0000:0800

(and I may be remembering from the Big Brother days . . .)

Yes Big Brother did have this issue, Henrik fixed this with hobbit.

Trent

Tom

---

From: Eric Meddaugh [mailto:etmsys at rit.edu] Sent: Friday, September 28, 2007 8:14 AM To: hobbit at hswn.dk Subject: RE: [hobbit] Weird Alerting behavior...bug or expected??

Just checking to see again if anyone has experienced this issue/problem??? I haven’t seen anything about it.

Thanks.

---Eric

---

From: Eric Meddaugh [mailto:etmsys at rit.edu] Sent: Monday, September 24, 2007 09:18 To: hobbit at hswn.dk Subject: [hobbit] Weird Alerting behavior...bug or expected??

We have the following the the Alerts file:

on-call page

$TSSSYS_ONCALL_DAY=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=10 TIME=W:0800:1700 RECOVERED

$TSSSYS_ONCALL_OFF=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=20 TIME=W:1700:0800 RECOVERED

$TSSSYS_ONCALL_END=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=20 TIME=06:*:* RECOVERED

$DUPING=%(mxgate)

HOST=$DUPING SERVICE=conn

    $TSSSYS_ONCALL_DAY

    $TSSSYS_ONCALL_OFF

    $TSSSYS_ONCALL_END

We had a host (mxgate03) go down at 3:15am, it sent 1 initial page, but no follow ups. No repeats. Does Monday from 12am-8am fall in a “limbo” timeframe where the 2nd rule does not apply since it’s not a Weekday after 5pm, but before 8am??? The host was down for over 3 hours without any follow up pages.

Do I need a rule similar to:

$TSSSYS_ONCALL_MON=SCRIPT /home/hobbit/server/ext/qpage.pl tss_sys_oncall COLOR=red REPEAT=10 TIME=1:0000:0800 RECOVERED

The different rules are suppose to repeat 10 minute during business hours, and 20 minutes off-hours.

Any ideas? Is this a bug or expected behavior?

Thanks.

---Eric

CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this message.