Monitoring Engine Time Incorrect - Causing 'Status' problems

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
jkeith
Posts: 18
Joined: Tue Mar 19, 2013 4:20 pm

Monitoring Engine Time Incorrect - Causing 'Status' problems

Post by jkeith »

Hello,

I've identified an issue with Host/Service 'Duration' values, in some cases they were displaying a negative value. I realize now this may have been caused by the timezone change which I had made a few days prior, while Nagios was still running. (My mistake) After researching the issue, I found a few threads which suggested the removal of the 'retention.dat' file resolved the issue for some. I tried this and instead of correcting the issue, the negative 'Duration' value is consistent on EVERY host/service.

Upon further investigation, I'm noticing the 'Monitoring Engine' 'Process Start Time' is exactly two hours ahead of 'System Profile' Date/Time. See below.
Process Start Time
2013-06-21 12:08:22
Total Running Time
15m 57s
Date/Time
PHP Timezone: America/Phoenix
PHP Time: Fri, 21 Jun 2013 10:24:50 -0700
System Time: Fri, 21 Jun 2013 10:24:50 -0700
I've checked time settings related to Nagios, PHP, any system time... all seem to be correct. Do you have any ideas on how I would go about resolving this issue?

Thanks,
Josh
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: Monitoring Engine Time Incorrect - Causing 'Status' prob

Post by abrist »

First, I suggest you verify that all steps from the Nagios XI timezone/datetime document have been successfully completed:
http://assets.nagios.com/downloads/nagi ... m_Time.pdf

Second I have seen this happen before, and you can either reboot the box, or bring the following service down and back up:

Code: Select all

service nagios stop
service ndo2db stop
service nagios start
service ndo2db start
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
jkeith
Posts: 18
Joined: Tue Mar 19, 2013 4:20 pm

Re: Monitoring Engine Time Incorrect - Causing 'Status' prob

Post by jkeith »

Thanks.

I noticed that "Notifications" have been disabled for all my services. Do you believe this to be an issue with the Status being incorrect?

If not, is there a way to batch enable notifications for all services?

Josh

UPDATE:

The service restarts did not resolve the issue, however a restart of the Nagios XI instance did. The monitoring engine is now showing the correct time stamp.

As I mentioned before, somehow all my service notifications were disabled. Is there a way to re-enable these services without visiting each one and selecting "Enable"

Josh

UPDATE TO MY UPDATE:

I re-enabled Service notifications by modifying my Service template to DISABLE notifications. Saved config. Went back to the same template, ENABLED notifications. Saved config... all Service notifications are enabled.

Josh
Last edited by slansing on Fri Jun 21, 2013 2:42 pm, edited 1 time in total.
Reason: Please make updates to your previouse post and not create new ones if you are the last poster.. thank you!
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Monitoring Engine Time Incorrect - Causing 'Status' prob

Post by slansing »

Great! Does this answer your questions? Was it just service notifications disabled, or the entire system's notifications? These can be controlled at:

Admin > Monitoring Engine Status > "Click the Green check mark next to Notifications, if it has a red circle."
jkeith
Posts: 18
Joined: Tue Mar 19, 2013 4:20 pm

Re: Monitoring Engine Time Incorrect - Causing 'Status' prob

Post by jkeith »

What it ended up being, is that the services in question were using a template they were not supposed to. So once I corrected the template settings, notifications began working.

Thanks!
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Monitoring Engine Time Incorrect - Causing 'Status' prob

Post by slansing »

Great to hear keith! Closing as resolved.
Locked