Nagios Support Forum

Posted: **Tue Jul 08, 2014 8:24 am**

Here you go:

[root@dennagxis1 ~]# tail -50 /var/log/mysqld.log > mysql.log
[root@dennagxis1 ~]# cat mysql.log
140704 13:07:16  InnoDB: Completed initialization of buffer pool
140704 13:07:16  InnoDB: Started; log sequence number 0 44243
140704 13:07:16 [Note] Event Scheduler: Loaded 0 events
140704 13:07:16 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
140704 13:07:24 [Note] /usr/libexec/mysqld: Normal shutdown

140704 13:07:24 [Note] Event Scheduler: Purging the queue. 0 events
140704 13:07:24  InnoDB: Starting shutdown...
140704 13:07:27  InnoDB: Shutdown completed; log sequence number 0 44243
140704 13:07:27 [Note] /usr/libexec/mysqld: Shutdown complete

140704 13:07:27 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140704 13:07:27 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140704 13:07:27  InnoDB: Initializing buffer pool, size = 8.0M
140704 13:07:27  InnoDB: Completed initialization of buffer pool
140704 13:07:28  InnoDB: Started; log sequence number 0 44243
140704 13:07:28 [Note] Event Scheduler: Loaded 0 events
140704 13:07:28 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
140704 13:10:16 [Note] /usr/libexec/mysqld: Normal shutdown

140704 13:10:16 [Note] Event Scheduler: Purging the queue. 0 events
140704 13:10:18  InnoDB: Starting shutdown...
140704 13:10:18  InnoDB: Shutdown completed; log sequence number 0 44243
140704 13:10:18 [Note] /usr/libexec/mysqld: Shutdown complete

140704 13:10:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140704 13:10:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140704 13:10:19  InnoDB: Initializing buffer pool, size = 8.0M
140704 13:10:19  InnoDB: Completed initialization of buffer pool
140704 13:10:19  InnoDB: Started; log sequence number 0 44243
140704 13:10:19 [Note] Event Scheduler: Loaded 0 events
140704 13:10:19 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
140704 13:10:20 [Note] /usr/libexec/mysqld: Normal shutdown

140704 13:10:20 [Note] Event Scheduler: Purging the queue. 0 events
140704 13:10:20  InnoDB: Starting shutdown...
140704 13:10:24  InnoDB: Shutdown completed; log sequence number 0 44243
140704 13:10:24 [Note] /usr/libexec/mysqld: Shutdown complete

140704 13:10:24 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140704 13:10:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140704 13:10:25  InnoDB: Initializing buffer pool, size = 8.0M
140704 13:10:25  InnoDB: Completed initialization of buffer pool
140704 13:10:25  InnoDB: Started; log sequence number 0 44243
140704 13:10:25 [Note] Event Scheduler: Loaded 0 events
140704 13:10:25 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution

Posted: **Tue Jul 08, 2014 2:22 pm**

Is the Last Check time still incorrect if you click the service and view the Overview tab?

Posted: **Tue Jul 08, 2014 2:41 pm**

Yes, it is.

Posted: **Tue Jul 08, 2014 5:17 pm**

Out of curiosity can you run the following again right after you visit the page with issues?:

Code: Select all

tail -50 /var/log/httpd/error_log

Have you noticed time issues elsewhere in the interface? Are your dashlett times in sync with your local time? etc?

Posted: **Wed Jul 09, 2014 8:38 am**

The dashlet times are correct. I don't see any place else where things are out of sync.

Posted: **Wed Jul 09, 2014 3:29 pm**

I just noticed that Fusion is reporting the status as displayed in XI which is outdated and doesn't match what Core is reporting. Does that help at all?

Posted: **Wed Jul 09, 2014 3:32 pm**

Ahh, actually that might, I wonder if something is or was wrong with your retention.dat file, a good test would be to stop nagios, and remove it, then restart nagios. All of your current checks will be re-ran however, it will clear the board of the past states/data returned to your hosts/services, if you are okay with that, run:

Code: Select all

service nagios stop

rm -f /usr/local/nagios/var/retention.dat

service nagios start

Then allow them to be re-scheduled and checked, fingers crossed that the time will be correct now.

Posted: **Wed Jul 09, 2014 3:56 pm**

All the service checks re-ran and posted properly in Core - XI is still showing the old data however.

Posted: **Wed Jul 09, 2014 3:59 pm**

Rick,

Can you open a ticket by sending an email to [email protected]? We will most likely want to move to a remote session.

Posted: **Wed Jul 09, 2014 4:02 pm**

I really don't want to use any of our paid support for this. I'll see about just wiping it and recreating it.

Nagios Support Forum

XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating

Re: XI "Last Check" not updating