Hi all!

I have a problem with Icinga scheduler's functionality. Once the host is
unreachable, scheduler isn't start to using the retry_interval to check
host's reachability, but it still using check_interval. Because the
max_check_attempt parameter is set to 3, after 3 attempts the system
changes from soft to hard state and sends notification by e-mail. If I know
well, the usual behaviour should be (by config listed below), that after
first check failure, the system changes from check_interval (4 minutes) to
retry_interval (2 minutes) and until max_check_attemp -1 (2) times it
checks the host's reachablity. If the host is still unreachable (after 8
minutes), Icinga sends notification about it. But, in real case it sends
after 12 minutes.
For service checks there is also a problem in scheduling - in template is
configured 7 minutes as normal check_interval and 3 minutes for
retry_interval, like in host's config, the max_check_attempts parameter is
set to 3 - it should notify after 13 minutes. In reality, the scheduler
perform checking with fix ~5 minutes interval, so I get notification after
15 minutes.
Parallel service checks are calculated by system and as I checked, the
value is correct. I have tried to set it manually, but with no success.

I have also a running Icinga v2 instance with similar values and it works
perfectly in scheduling (v2 instance will replace the old v1 system, now
it's running only in test mode).
My main problem is that I feel, as if I don't have any influence in
checking hosts and services.

Do you have any idea, why the scheduler works as it does?

--------------------------------

There are my Icinga templates, all of hosts and services are using them :

define host {
    name general_host
    notifications_enabled 1
    event_handler_enabled 1
    flap_detection_enabled 1
    process_perf_data 1
    retain_status_information 1
    retain_nonstatus_information 1
    check_interval 4
    retry_interval 2
    max_check_attempts 3
    notification_interval 0
    notification_period 24x7
    notification_options d,r
    register 0
}

define service {
    name general_service
    is_volatile 0
    check_interval 7
    retry_interval 3
    max_check_attempts 3
    active_checks_enabled 1
    passive_checks_enabled 0
    check_period 24x7
    parallelize_check 1
    obsess_over_service 0
    check_freshness 0
    event_handler_enabled 1
    flap_detection_enabled 1
    process_perf_data 1
    retain_status_information 1
    retain_nonstatus_information 1
    notification_interval 0
    notification_period 24x7
    notification_options w,u,c,r
    notifications_enabled 1
    contact_groups admin
    register 0
}


Thank you in advance for any answers! :)
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to