Nagios Support Forum

Hi:

We have Nagios XI enterprise licensed

I have a problem with nagios Availability Reports and after some digging I found something strange when I go to advanced configuration and go directly to nagios core reports

for example in April 1 , at 2.30am the host present a Critial hard failure check and the table reports after that 21hours and 21 minuts of failure ( the rest of the day) and suddenly in April 2 change to ok
however in nagios log I see that after a couple of minutes the service recovers and for the rest of the day only a few soft failures appear in logs

I suppose that this is why mi availability Reports are wrong

I am understanding this right?

There is an error in nagios?

why several hosts after a failure do not recover until the change of day?

can you help me

Jorge Arenas
CSA

What version of XI are you using? You can grab it from the bottom left hand side of the web interface.

What version of Core are you running?
Please run that availability report again but please show us the options you selected in the previous page (this is very important) and in the final page, click the [ View full log entries ] link so that we can see them all and resend the screenshot.

Thank you!

Version of Nagios XI 5.5.9

Nagios Core 4.4.3

this is the information to create the availability report , we select Report period: this month and backtraced archives: 11
service Log entries without full log entries:
service log entries with full log entries selected (I am selecting april part):

Can you show what you are selecting in step 3 of running the report?

We need to see if you are including soft states

Sorry for missing that

when I select No in soft states
I get a report with 21h 30m of Service Critical (HARD) state down

but with Yes in soft states
my question here is

1.- why 21 hours down? ( los in the first email show down the service for few minutes and then everything ok... so why 21 hours in the table

2.- why the service change state as soon as change the day? this is the other strange behavior, why a service keep the state down and why at the end of the day return to ok

3.- when I include soft states the table reflects better detail of what really happens

so, I do not know if this behavior is expected, and if it is, can you explain why? or this is a bug in the report

thanks in advance
Jorge Arenas

You didn't go back to HARD OK until 21 hours later.

However, there may be an explanation.

What version of Nagios Core is this?

There was a bug in early 4.4.x versions that could cause this to not go HARD when it is supposed to.

Hi Scott:

my version is

Nagios Core 4.4.3

this version is affected?

what version of nagios XI, I need to upgrade to get a newer Nagios Core module?

or I need to upgrade manually ?

thanks in advance

Jorge Arenas Quezada

This is the latest version.

How often is this host/service checking?

Can you share the configuration for this host/service ?