XI reporting not working properly
-
anil_kumarv
- Posts: 50
- Joined: Thu Oct 17, 2013 2:00 am
Re: XI reporting not working properly
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
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.
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.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
anil_kumarv
- Posts: 50
- Joined: Thu Oct 17, 2013 2:00 am
Re: XI reporting not working properly
Do we need to take backup of db before doing repair. Any specific instructions on how to take backup of db in Nagios.?
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: XI reporting not working properly
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
http://assets.nagios.com/downloads/nagi ... ios-XI.pdf
-
anil_kumarv
- Posts: 50
- Joined: Thu Oct 17, 2013 2:00 am
Re: XI reporting not working properly
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.
[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.
Last edited by scottwilkerson on Thu Jan 22, 2015 4:11 pm, edited 1 time in total.
Reason: security
Reason: security
Re: XI reporting not working properly
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]
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.
"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.