Page 2 of 3
Re: Nagios Service status got frozen
Posted: Thu Aug 03, 2017 8:13 am
by concise
I have tried both given guides to fix database issue but nothing help us to solve the issue. I am stil having the below issue
Code: Select all
mysqlcheck -f -r -u root -pnagiosxi --all-databases
......
nagiosxi.xi_incidents
note : The storage engine for the table doesn't support repair
....
Thanks
Re: Nagios Service status got frozen
Posted: Thu Aug 03, 2017 11:03 am
by tgriep
That table somehow was setup as an innodb table that does not support the the repair command. It can be converted to myisam by running the following and then the repair will work.
Code: Select all
echo 'ALTER TABLE nagiosxi.xi_incidents engine=MyISAM;' | mysql -u root -pnagiosxi
Re: Nagios Service status got frozen
Posted: Thu Aug 03, 2017 11:37 am
by concise
Thanks it does fix the table on repair. But still my issue exists. (NagiosXI service status GUI not updating)
Re: Nagios Service status got frozen
Posted: Thu Aug 03, 2017 12:45 pm
by tgriep
You may want to open a ticket up for this so we can better support this.
To do that, send an email to
[email protected] and if your email address is on the support contract, a ticket will be generated.
If you don't want to open a Ticket, can you PM me a System Profile from the server?
To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and email it back to us.
Re: Nagios Service status got frozen
Posted: Thu Aug 03, 2017 1:00 pm
by concise
Hi tgriep,
I have PM my system profile.zip. Please check and do the needful action
Thanks
Re: Nagios Service status got frozen
Posted: Thu Aug 03, 2017 1:49 pm
by tgriep
I received the profile and shared it with the other Techs.
I took a look at the log files and I see that there are max connection errors when connecting to the mysql database and that is probably causing the issue.
The following KB article are the steps to fix it.
https://support.nagios.com/kb/article/n ... tions.html
Let us know if this solves the issue.
Re: Nagios Service status got frozen
Posted: Thu Aug 03, 2017 9:46 pm
by concise
Hi,
Sorry still not resolved.
Code: Select all
[root@ip-172-31-0-10 centos]# mysql -uroot -pnagiosxi -e "show global status like 'Max_used_connections';"
+----------------------+-------+
| Variable_name | Value |
+----------------------+-------+
| Max_used_connections | 39 |
+----------------------+-------+
[root@ip-172-31-0-10 centos]# mysql -uroot -pnagiosxi -e "show variables like 'max_connections';"
+-----------------+-------+
| Variable_name | Value |
+-----------------+-------+
| max_connections | 818 |
+-----------------+-------+
You can see on the above my max_used_connections is 39. Still increased the max_connections to 818 and tried but it doesn't fix my issue.
Thanks
Re: Nagios Service status got frozen
Posted: Fri Aug 04, 2017 11:02 am
by tgriep
I think I found it. There are some additional settings added to the ndo2db config file that could be causing it to not write the data to the MYSQL database.
Edit this file
and remove the following lines from the bottom of the file.
Code: Select all
socket_type=tcp
socket_name=/var/run/ndo.sock
lock_file=/usr/local/nagios/var/ndo2db.lock
tcp_port=5668
Save the file and restart the ndo daemon by running
Let the server run for a while and let us know if the GUI updates with current data.
Re: Nagios Service status got frozen
Posted: Fri Aug 04, 2017 11:35 pm
by concise
On removing the above configuration. we are able to restart ndo2db but on checking it status it says "not running but subsystem locked".
Code: Select all
[root@ip-172-31-0-10 centos]# vi /usr/local/nagios/etc/ndo2db.cfg
[root@ip-172-31-0-10 centos]# service ndo2db restart
Restarting ndo2db (via systemctl): [ OK ]
[root@ip-172-31-0-10 centos]# service ndo2db status
ndo2db is not running but subsystem locked
[root@ip-172-31-0-10 centos]#
Thanks
Re: Nagios Service status got frozen
Posted: Sun Aug 06, 2017 11:47 pm
by concise
still we are waiting for your response. Please help us to fix the ASAP. Its been a week i have opened this ticket.
Thanks