Notifications not happening

[Upayavira]

Steve Shipway wrote:

>You will have to wait for 999 minutes for an alert, the way you have it
>configured.
>
>The alerts happen after max_check_attempts have confirmed the status.
>
>Every nromal_check_interval, then service is checked.  If it changes to an
>alert state, then it is rechecked after retry_check_interval.  This is
>repeated until it either goes to an OK state, or until it reaches
>max_check_attempts.
>If it has reached the max_check_attempts and is still alerting, then it
>sends an alert, and does so again after notification_interval repeatedly
>until the state changes.
>  
>
Fantastic. I know it was something simple.

Thank you for your simple, clear explaination.

With best wishes,

Upayavira

>>-----Original Message-----
>>From: nagios-users-admin at lists.sourceforge.net 
>>[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of 
>>Upayavira
>>Sent: Tuesday, 27 April 2004 9:11 a.m.
>>To: nagios-users at lists.sourceforge.net
>>Subject: [Nagios-users] Notifications not happening
>>
>>
>>I feel like I'm soooo close...
>>
>>I've got the following in services.cfg:
>>define service{
>>       use                             generic-service
>>       host_name                       roy
>>       service_description             HTTP
>>       is_volatile                     0
>>       check_period                    24x7
>>       max_check_attempts              999
>>       normal_check_interval           1
>>       retry_check_interval            1
>>       contact_groups                  internet-team
>>       notification_interval           1
>>       notification_period             24x7
>>       notification_options            w,u,c,r
>>       check_command                   check_http!roy!80!/myapp
>>       }
>>
>>and in checkcommands.cfg:
>>
>>define command{
>>       command_name    check_http
>>       command_line    $USER1$/check_http -H $ARG1$ -p $ARG2$ 
>>-u $ARG3$
>>       }
>>
>>in misccommands.cfg:
>>
>>define command{
>>       command_name    notify-by-sms
>>       command_line    /bin/date >> /home/web/bin/sms.log
>>       }
>>
>>in contactgroups.cfg:
>>
>>define contactgroup{
>>       contactgroup_name       internet-team
>>       alias                   Internet Team
>>       members                 upayavira
>>       }
>>
>>and in contacts.cfg:
>>
>>define contact{
>>       contact_name                    upayavira
>>       alias                           Upayavira
>>       service_notification_period     24x7
>>       host_notification_period        24x7
>>       service_notification_options    w,u,c,r
>>       host_notification_options       d,u,r
>>       service_notification_commands   notify-by-sms,notify-by-email
>>       host_notification_commands      
>>host-notify-by-sms,host-notify-by-email
>>       email                           upayavira at xyz.com
>>       pager                           071234556
>>       }
>>
>>Now, as far as I can see, when I shut down Apache on server Roy, I 
>>should get a notification by email to upayavira at xyz.com, and 
>>the current 
>>date/time appended to /home/web/bin/sms.log (just to prove that 
>>something is happening).
>>
>>This should happen every minute or so (as I set the intervals 
>>to 1). But 
>>I haven't been getting any nofications at all, by email or 
>>into my text 
>>file.
>>
>>Can anyone see anything?
>>
>>I feel like I'm sooo close to understanding this!
>>
>>Thanks, Upayavira
>>    
>>




-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null