If problem persists notifications...

[cmort]

Hello, I am trying to update the default time of 60 minutes for the "if problem persists" send a notificaton every x-minutes. I have change this to a variable of 3 but Nagios does not seem to recognize the change. I am still getting a 60 minute interval notice for a persisting problem.
The services config file seems to have been updated but I am not getting notifications every 3 minute but do get them @ 60 minute intervals. Any help is appreciated.
###############################################################################

define service {
host_name 10.1.110.17
service_description QAWEB17_ URL Status
use xiwizard_website_http_service
check_command check_xi_service_http! -H 10.1.110.17 -f ok -I 10.1.110.17 -u "/" -p 80 -w 3 -c 6 !!!!!!!
max_check_attempts 2
check_interval 5
retry_interval 1
notification_interval 3
first_notification_delay 0
notification_period 24x7
notifications_enabled 1
contacts cmort,nagiosadmin
_xiwizard websiteurl
register 1
}

#########################################################################

[jsmurphy]

did you reload the nagios configuration after making the change? /etc/init.d/nagios reload or restart

[cmort]

Ah I think I found the issue, There is a /hosts/10.1.110.17.cfg and a /services/10.1.110.17.cfg. When I modified the services check parameters throught he nagios core config manager it only modifies the /services/10.1.110.17.cfg and not the /hosts/10.1.110.cfg. once I modified the host check parameter for persistance I started getting the notifications @ 3 minute intervals.
is this normal activity that I need to keep in mind that I might need to update parameters for both a service and a host or does one take priority over another?

Thank You

[jsmurphy]

The host and the service are considered to be completely separate entities... so if you want both to be uniform you will need to change it in both the service and host definition. Otherwise the host-alive check will run at the interval defined for the host and services interval will run as defined for the service.

The reason for this, is that you may want to know the host is alive more urgently than you want to know http has stopped working.