notification)interval being ignored?

[Kyle O'Donnell]

we don't use escalations at all.

here is whats currently in the objects.cache (service is now in OK
status though)

define service {
        host_name       myserver
        service_description     fg-to-svc-os_sun_df_OS
        check_period    24x7
        check_command   fg-to-chk-nrpe-sun_df_OS!5666!10%!5%!/!/var!/tmp
        contact_groups  fg-to-cg-admins
        notification_period     24x7
        initial_state   o
        check_interval  5.000000
        retry_interval  2.000000
        max_check_attempts      3
        is_volatile     0
        parallelize_check       1
        active_checks_enabled   0
        passive_checks_enabled  1
        obsess_over_service     0
        event_handler_enabled   0
        low_flap_threshold      0.000000
        high_flap_threshold     0.000000
        flap_detection_enabled  0
        flap_detection_options  o,w,u,c
        freshness_threshold     0
        check_freshness 0
        notification_options    u,w,c,r
        notifications_enabled   1
        notification_interval   1440.000000
        first_notification_delay        0.000000
        stalking_options        n
        process_perf_data       0
        failure_prediction_enabled      1
        retain_status_information       1
        retain_nonstatus_information    1
        }

could the nagiosstatus.sav be affecting anything?

On 10/20/09, Marc Powell <marc at ena.com> wrote:
>
> On Oct 20, 2009, at 2:18 PM, Kyle O'Donnell wrote:
>
>> I am running nagios 3.0.6...
>>
>> I don't know if this is happening for all hosts/services, but it seems
>> to be happening more and more...
>>
>> critical service alert goes to hard state - notification 1 sent
>> notification_interval == 1440 minutes
>> No more notifications, service remains in the same state for 34days
>> service drops to warning state - notification 1 sent
>> service drops to OK state - notification 1 sent.
>>
>> here is the service template:
>>
>> define service {
>>        name                            fg-to-st-ni5ri2ma3
>>        is_volatile                     0
>>        check_period                    24x7
>>        max_check_attempts              3
>>        normal_check_interval           5
>>        retry_check_interval            2
>>        active_checks_enabled           0
>>        passive_checks_enabled          1
>>        parallelize_check               1
>>        obsess_over_service             0
>>        check_freshness                 0
>>        notifications_enabled           1
>>        notification_interval           1440
>
> Do you see this notification interval in objects.cache? Do you maybe
> have a service escalation that's overriding it?
>
> --
> Marc
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) 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/devconference
> _______________________________________________
> 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
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) 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/devconference
_______________________________________________
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