Page 4 of 4
Re: XI reporting not working properly
Posted: Wed Jun 11, 2014 1:32 pm
by anil_kumarv
Will the repair require a downtime and how long the monitoring will be affected. We are monitoring several critical customer facing servers so we do not want this to affect our monitoring.
Re: XI reporting not working properly
Posted: Wed Jun 11, 2014 2:21 pm
by lmiltchev
The repair script may run for a time period of somewhere between a minute to 15-20 minutes, depending on the size of the tables.
If you have database errors, you don't have much of a choice. You need to fix the errors, as if you don't, you may experience unexpected behavior in Nagios XI.
Re: XI reporting not working properly
Posted: Tue Jun 17, 2014 12:29 am
by anil_kumarv
Do we need to take backup of db before doing repair. Any specific instructions on how to take backup of db in Nagios.?
Re: XI reporting not working properly
Posted: Tue Jun 17, 2014 9:25 am
by slansing
No you do not, though it is recommended that you take regular backups, and XI does this to an extent. Please read the following for more information:
http://assets.nagios.com/downloads/nagi ... ios-XI.pdf
Re: XI reporting not working properly
Posted: Tue Jul 08, 2014 4:54 am
by anil_kumarv
Okay we have done XI DB repair and following is the db log post repair :
[root@---- Snip --- admins]# tail -50 /var/log/mysqld.log
131205 10:09:06 InnoDB: Completed initialization of buffer pool
131205 10:09:06 InnoDB: Started; log sequence number 0 44233
131205 10:09:06 [Note] Event Scheduler: Loaded 0 events
131205 10:09:06 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.69' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
140108 14:14:32 [Note] /usr/libexec/mysqld: Normal shutdown
140108 14:14:32 [Note] Event Scheduler: Purging the queue. 0 events
140108 14:14:32 InnoDB: Starting shutdown...
140108 14:14:37 InnoDB: Shutdown completed; log sequence number 0 44233
140108 14:14:37 [Note] /usr/libexec/mysqld: Shutdown complete
140108 14:14:37 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140108 14:15:05 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140108 14:15:05 InnoDB: Initializing buffer pool, size = 8.0M
140108 14:15:05 InnoDB: Completed initialization of buffer pool
140108 14:15:05 InnoDB: Started; log sequence number 0 44233
140108 14:15:05 [Note] Event Scheduler: Loaded 0 events
140108 14:15:05 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.69' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
140708 7:06:34 [Note] /usr/libexec/mysqld: Normal shutdown
140708 7:06:34 [Note] Event Scheduler: Purging the queue. 0 events
140708 7:06:34 InnoDB: Starting shutdown...
140708 7:06:39 InnoDB: Shutdown completed; log sequence number 0 44233
140708 7:06:39 [Note] /usr/libexec/mysqld: Shutdown complete
140708 07:06:39 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140708 07:10:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140708 7:10:15 InnoDB: Initializing buffer pool, size = 8.0M
140708 7:10:15 InnoDB: Completed initialization of buffer pool
140708 7:10:15 InnoDB: Started; log sequence number 0 44233
140708 7:10:15 [Note] Event Scheduler: Loaded 0 events
140708 7:10:15 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.69' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
140708 7:10:35 [Note] /usr/libexec/mysqld: Normal shutdown
140708 7:10:35 [Note] Event Scheduler: Purging the queue. 0 events
140708 7:10:37 InnoDB: Starting shutdown...
140708 7:10:40 InnoDB: Shutdown completed; log sequence number 0 44233
140708 7:10:40 [Note] /usr/libexec/mysqld: Shutdown complete
140708 07:10:40 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140708 07:10:41 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140708 7:10:41 InnoDB: Initializing buffer pool, size = 8.0M
140708 7:10:41 InnoDB: Completed initialization of buffer pool
140708 7:10:41 InnoDB: Started; log sequence number 0 44233
140708 7:10:41 [Note] Event Scheduler: Loaded 0 events
140708 7:10:41 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.69' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
----------------------------------------------------------------------------------------------------------
We are still facing same problem. When sorted Top Alert Producers report for any hostroup, it does say 0 records though I can see that specific hostgroup hosts when not filtered.
Re: XI reporting not working properly
Posted: Tue Jul 08, 2014 4:51 pm
by abrist
At this point, lets move you into the ticket system so that we can resolve the issue through a remote session if necessary. Please send an email referencing this thread to
[email protected]