Last Update 1-1-1970

[toodaly]

I have a Nagios XI server that has been running in a test environment since February 2016. Attached is what the system status has.
When I hover over the orange question marks, it says Unknown. When I hover over the red exclamation points, it says Last checked 16947d 20h 17m 47s. This was at 20:17 GMT 5/26/2016. I also noticed only three checkmarks. The monitoring engine is not one of them (I forgot what it said when I hovered over them). Host and service checks look normal and are being checked periodically. Any ideas?

Thanks.

[hsmith]

Is cron running?

What's the output of a 'date' command?

[toodaly]

Here's my results:

Code: Select all

[root@ZLA-NXI001 ~]# service crond status
crond (pid  2411) is running...
[root@ZLA-NXI001 ~]# service mysqld status
mysqld (pid  7031) is running...
[root@ZLA-NXI001 ~]# service npcd status
NPCD running (pid 8606).
[root@ZLA-NXI001 ~]# service nagios status
nagios (pid 3425) is running...
[root@ZLA-NXI001 ~]# service ntpd status
ntpd (pid  1958) is running...
[root@ZLA-NXI001 ~]# service httpd status
httpd (pid  2403) is running...
[root@ZLA-NXI001 ~]# date
Thu May 26 21:09:39 UTC 2016
[root@ZLA-NXI001  ~]#

Here's an example of a host that appears to be fine (seems to align with the February install time):
Host Status Duration Attempt Last Check Status Information
zla-gwy001 Up 98d 21h 58m 31s 1/5 2016-05-26 21:08:39 OK - 168.192.0.1: rta 3.549ms, lost 0%

The three checkmarks in the upper right are:
Active Host Checks Are Enabled
Active Service Checks Are Enabled
Notifications Are Enabled

Here's my XI version information:
full=2012R2.9
major=2012
minor=R2.9
releasedate=2014-02-11
release=320

This version has been verified against our requirements and my management does not want to upgrade/re-verify due to schedule and budget.

Thanks.

[tgriep]

Try running the following as root to see if that resolves the issue.

Code: Select all

service nagios stop
killall -9 nagios
service crond restart
service httpd restart
service nagios start

Try that and see if that fixes the issue.