Nagios Support Forum

tmcdonald wrote:If you want, you can post this to our Github so our Core dev can take a look at it: https://github.com/NagiosEnterprises/nagioscore/issues

That'll get more traction on our end.

Thanks!

Currently under a very hard workload. This works for now with my ugly patch. Look into it later.

/Marcus

Can you post the configuration for one of the service checks that is having the issue so we can review it? define service { name xxxxxx-service use generic-service register 0 is_volatile 0 check_period 24x7 max_check_attempts 3 normal_check_interval 5 retry_check_interval 1 notification_interval 0 ...

I did not find a solution to this. I do not have the time to investigate it further. Did an ugly workaround by adding the following to the is_service_result_fresh and the corresponding in is_host_result_fresh /* Added by MR. Just check for insanely small expiration times */ if (expiration_time < 140...

I can't seem to find any issues with the time. I added some debugging and came up with this. [1454505675] Warning: The results of service 'CPU' on host 'all-xxx1' are stale by 0d 0h 4m 1s (threshold=0d 0h 6m 0s) (current_time=1454505675, expiration_time=1454505434). I'm forcing an immediate check of...

[quote="hsmith"]Is the time on your system off by chance?

No, I don't think so. The time is correct. However this is on a virtual server. I'll see if I can investigate this lead in more depth. Thanks for the input!

Marcus

I'm experiencing a lot of false alarms from passive checks. I have raised the threshold to a much longer time than needed to minimize the false alarms, but still a lot is coming through. Looking at the log there seems to be an apparent bug since the log says a service is stale by 16829d 6h 38m 22s (...