Freshess checks on Nagios xi 2011R3.2

nagiosadmin42 · Post by **nagiosadmin42** » Thu Jul 05, 2012 7:27 pm

The log messages are back, the ones indicating "The results of service 'xyz' on host 'ABC' are stale".

Things have quieted down a bit, and the messages I'm seeing now relate to services that actually ARE stale. This probably means that Nagios forces an immediate check for an already-stale service when it receives a passive result, regardless of the threshold test. I was probably thrown by the log message which made it appear the threshold hadn't been met, not considering the current service status.

Maybe that was the problem all along... thanks for helping me work through this, and sorry for the confusion.

scottwilkerson · Post by **scottwilkerson** » Thu Jul 05, 2012 9:58 pm

Glad to here things have calmed down and appear normal.

I'm not going to lock this topic just yet, if additional related problems come up add them to this thread.

lmilkovic · Post by **lmilkovic** » Fri Jul 06, 2012 2:04 am

nagiosadmin42 wrote:I've edited /usr/local/nagios/etc/nagios.cfg and set debug_verbosity=16, re-enabled "Check freshness" for the xiwizard_passive_service template, and have applied the configuration changes.

It's been about half an hour, and I've been monitoring /var/log/messages for the debug lines you mentioned, but so far see nothing related to them or the problem I described where the freshness check is being triggered even though the threshold hasn't been reached.

Very strange... I'll keep you posted if I find out anything new.

Debug information is most probably not sent to /var/log/messages - debug log is specified by the debug_file option in the nagios.cfg.

But it's irrelevant now that you solved the problem:)

scottwilkerson · Post by **scottwilkerson** » Fri Jul 06, 2012 9:05 am

lmilkovic wrote:Debug information is most probably not sent to /var/log/messages - debug log is specified by the debug_file option in the nagios.cfg

This is correct, just validating in case others have a similar situation.

nagiosadmin42 · Post by **nagiosadmin42** » Fri Jul 06, 2012 11:52 am

Some clarification before this thread is closed...

I did figure out why I wasn't seeing any debug info, the flag I should have changed is debug_level=16, not debug_verbosity=16. Once I did that and restarted the service, the nagios.debug file was created.

nagiosadmin42, please enable debugging by setting the debug_verbosity to 16 (Host/service check information) in nagios.cfg.
Can you post the line(s) that start with "HBC: xx, PC: xx, ..."?

I did see a section in the debug file "Checking the freshness of service check results..." which contains the same type of log entry as seen in /var/log/messages without debug enabled:

Code: Select all

Check results for service 'Test Service' on host 'TEST-HOST' are stale by 0d 0h 0m 11s (threshold=0d 1h 0m 0s).  Forcing an immediate check of the service...

However, I'm not seeing HBC: or PC: lines in the debug file, maybe the debug_verbosity controls that, I had left it at the default debug_verbosity=1.

In any case, I learned a lot more about Nagios debugging through this exercise, which will undoubtedly help in the future! Thanks for your help.

Nagios Support Forum

Freshess checks on Nagios xi 2011R3.2

Re: Freshess checks on Nagios xi 2011R3.2

Re: Freshess checks on Nagios xi 2011R3.2

Re: Freshess checks on Nagios xi 2011R3.2

Re: Freshess checks on Nagios xi 2011R3.2

Re: Freshess checks on Nagios xi 2011R3.2