NSCA problem, nagios "forgetting" info


#1

Hi

I’m having some problems using NSCA with nagios.

All servers send info to nagios server, but nagios every now and then ‘forget’ it. For example:

Jul 18 12:05:20 homer nagios2: SERVICE ALERT: SERVER;WINCPU;OK;SOFT;2;OK - El consum de CPU es: 14.21 %
Jul 18 12:06:01 homer nagios2: SERVICE ALERT: SERVER;WINCPU;WARNING;SOFT;1;WARNING: No se reciben datos desde hace demasiado tiempo

This service check is configured this way:

define service{
hostgroup_name winservers
service_description WINCPU
use generic-passive_service ; Name of service template to use
check_period 24x7
max_check_attempts 4
normal_check_interval 1
retry_check_interval 1
notification_options w,u,c,r
notification_interval 960
notification_period 24x7
freshness_threshold 180
check_command check_dummy!1!“No se reciben datos desde hace demasiado tiempo”
}

You see, freshness threshold is 180 seconds, but nagios starts complaining 40 seconds after receiving data…

What makes me feel lost is that other services configured exactly the same way have no problems:

define service{
hostgroup_name winservers
service_description Memoria
use generic-passive_service ; Name of service template to use
check_period 24x7
max_check_attempts 4
normal_check_interval 1
retry_check_interval 1
notification_options w,u,c,r
notification_interval 960
notification_period 24x7
freshness_threshold 180
check_command check_dummy!1!“No se reciben datos desde hace demasiado tiempo”
}

And other servers in the same group (winservers) never have problems… it’s just a matter of 6 or 7 servers, and 4 or 5 services…

So the server can contact nagios, can send info to NSCA, in a way nagios can use. But, from time to time, it seems like freshness threshold gets too low, or something like that, I don’t know…

I can’t find any connexion beetweem all this info, does anybody have a hint? Any clue?

Thanks in advance