Active service goes critical in 40 sec

[rentsys]

I have a service set up for a switch that checks the status of a port.

Code: Select all

define service {
        host_name                       cssw3750backbone
        service_description             DR VM Server 2 G1/0/17 Status
        use                             xiwizard_switch_port_status_service
        check_command                   check_xi_service_ifoperstatus!Rentsys!10117!-v 2!!!!!
        max_check_attempts              5
        check_interval                  5
        retry_interval                  1
        active_checks_enabled           1
        passive_checks_enabled          0
        check_period                    xi_timeperiod_24x7
        notification_interval           0
        notification_period             xi_timeperiod_24x7
        contact_groups                  admins,rentsysNetwork
        _xiwizard                       switch
        register                        1
        }

When it goes down it takes 40 seconds to go to critical where it should take five minutes. How do I fix this?

Code: Select all

Service Critical[06-18-2014 11:50:08] SERVICE ALERT: cssw3750backbone;DR VM Server 2 G1/0/17 Status;CRITICAL;HARD;5;CRITICAL: Interface GigabitEthernet1/0/17 (index 10117) is down.\n
Service Critical[06-18-2014 11:49:58] SERVICE ALERT: cssw3750backbone;DR VM Server 2 G1/0/17 Status;CRITICAL;SOFT;4;CRITICAL: Interface GigabitEthernet1/0/17 (index 10117) is down.\n
Service Critical[06-18-2014 11:49:48] SERVICE ALERT: cssw3750backbone;DR VM Server 2 G1/0/17 Status;CRITICAL;SOFT;3;CRITICAL: Interface GigabitEthernet1/0/17 (index 10117) is down.\n
Service Critical[06-18-2014 11:49:37] SERVICE ALERT: cssw3750backbone;DR VM Server 2 G1/0/17 Status;CRITICAL;SOFT;2;CRITICAL: Interface GigabitEthernet1/0/17 (index 10117) is down.\n
Service Critical[06-18-2014 11:49:27] SERVICE ALERT: cssw3750backbone;DR VM Server 2 G1/0/17 Status;CRITICAL;SOFT;1;CRITICAL: Interface GigabitEthernet1/0/17 (index 10117) is down.\n

[slansing]

It won't take 5 minutes to go critical, it will pick this up immediately, what will take 5 minutes is the transition from a SOFT critical state to a HARD critical state. This is another way of filtering notifications.

[rentsys]

sorry, that is what i meant. I checked a few different services and it seems that all my services going from soft to hard within 40 sec. The hosts are not doing this.

[Box293]

Lets check a couple of things:

System Time
Goto Admin > System Profile.
What is shown under Date/Time?

Interval Length
Run this command at the CLI and report back what it says:

Code: Select all

grep interval_length /usr/local/nagios/etc/nagios.cfg

Also, I found this on the web which talked about on-demand checks.
https://bugs.op5.com/view.php?id=8547