Nagios Availability report not working for me

[paul.jobb]

Hi;

I just installed a new server and upgraded it to the latest version(5.4.2), this was an install on a rhel 7.1 server as opposed to using the ova . The availability report only seems to be reflecting the current state of the service regardless of the time frame selected, so if the service is current state of critical then that's displayed on the pie chart as a percentage of all services it seems (which is 50% in this case)

Capturea.JPG

then I recover the service and its 100% with no regard for the time selected

Captureb.JPG

I do have this server configured to use a ram cache but that has never impacted this report on other servers. Same results using the jsonquery tool (archivejson.cgi)

[paul.jobb]

Sorry for whatever reason the first screen shot posted twice

[avandemore]

Was this working prior to the upgrade? When you speak of ram cache do you mean RAM Disk? Does Core reflect the correct values?

[paul.jobb]

Sorry yes I meant Ram disk, it appears to be the same behavior in core.

No its never worked on this server from what I can tell, the original install was 5.4.0 (so its a fairly new build) upgraded yesterday to 5.4.2

[paul.jobb]

I checked the file permissions on the /usr/local/nagios/var/nagios.log and the files in the ./archives folder and they were all set to

-rw------- 1 nagios nagios

I updated them to
-rw-r--r-- 1 nagios nagios (chmod 644 nagios.log)

and that seems to have worked??? This matches another nagios server that I used an OVA with instead.

Is there anything else I should look at permissions wise, I didn't knowingly set permissions on any of these files.

[mcapra]

This particular issue is a known bug that will be fixed in Nagios Core 4.2.5 (ID 10891) which should propagate down the line into a future Nagios XI version. I can't think of any other immediate permissions related issues present in 5.4.2.

[paul.jobb]

oh ok , thankyou

[mcapra]

Certainly! I do apologize for the inconvenience.

Did you have additional questions regarding this issue, or can I lock this thread and mark it as resolved?