notifications

[Marc Powell]

On Sep 24, 2009, at 12:05 PM, alexus wrote:

> On Thu, Sep 24, 2009 at 12:19 PM, Marc Powell <marc at ena.com> wrote:
>> 2009/9/19 alexus <alexus at gmail.com>:

>> *From objects.cache* --
>>
>> host definition
>
> define host {

looks good

>> service definition
>
> define service {

looks good.

>> contactgroup definition
>
> define contactgroup {
>        contactgroup_name       staff
>        alias   alexusbiz corp.
>        members dmitry chorine

I haven't seen anyone use contact names with spaces in them but I'm  
not aware of any reason it wouldn't work.

>> contact definition
>
> define contact {

This looks good as well.

>> the service notification command{} definition for the contact
>
> define command {

Fine.

>> all referenced timeperiod definitions
>
> define timeperiod {

Here too...

Nothing obviously wrong with the object configs that I can see.

>>  From nagios.log --
>>
>> all entries related to this host or service around the time you  
>> expect
>> a notification to be sent.
>
> -bash-3.2# grep dummy nagios.log
> [1253764800] CURRENT SERVICE STATE: jothost.j;dummy;CRITICAL;HARD; 
> 3;CRITICAL
> [1253807636] SERVICE ALERT: jothost.j;dummy;CRITICAL;SOFT;1;CRITICAL
> [1253807696] SERVICE ALERT: jothost.j;dummy;CRITICAL;SOFT;2;CRITICAL
> [1253807756] SERVICE ALERT: jothost.j;dummy;CRITICAL;HARD;3;CRITICAL

Yet nagios doesn't believe that it's supposed to attempt a notification

>> Also, verify in the web interface that notifications are enabled for
>> the host and service and that it is not in a period of scheduled
>> downtime.

Did you check the web interface to verify that notifications for the  
specific service are enabled? You should also check under 'Process  
Info' to make sure notifications are enabled program wide  
(enable_notifications 1 in nagios.cfg).

Both of these options can be disabled in the web interface. Since you  
appear to be using retention, those settings will be remembered  
between restarts and will take precedence over config file/ 
objects.cache settings. You can see the current settings for these  
types of things in the status.dat file but using the web interface is  
usually easier.

--
Marc

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
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