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
> notification_period 24x7
> notification_options u,c,w,r
> event_handler_enabled 0
> flap_detection_enabled 0
> process_perf_data 0
> retain_status_information 1
> retain_nonstatus_information 1
> contact_groups fg-to-cg-admins
> register 0
> }
>
> here is the service def
> define service {
> service_description fg-to-svc-os_sun_df_OS
> use fg-to-st-ni5ri2ma3
> host_name myserver
> check_command
> fg-to-chk-nrpe-sun_df_OS!5666!10%!5%!/!/var!/tmp
> }
>
> Any ideas?
>
I *could* be mistaken about this, but I don't think the notification
interval applies if you're only getting passive check results.
------------------------------------------------------------------------------
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
[email protected]
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
