Issues with table 'nagios_logentries'

[nixe]

Our priority is to solve this performance issue and need to solve this before thinking in upgrading your production environment.

I realized the version would be in your mysqllog. You are running 5.1. You could see performance improvements by moving to MySQL 5.5 (http://www.oracle.com/us/products/mysql ... 364861.pdf) and then to MySQL 5.6 (the MySQL 5.7 improvements largely do not look interesting in the context of XI). The entire point of bringing it up is to resolve the performance issue you are seeing. You can install the later versions of MySQL on RHEL 6. I just suggested the OS switch because that would make the move to mariadb easier and then you get an extra bump there. You could also go MariaDB on RHEL 6, but that is more complicated. Since you are on RHEL, the move to later versions of MySQL should be easier: https://access.redhat.com/solutions/1980533 . I do not have a RHEL system on which to test an upgrade to 5.1 to 5.6 using their repo, but the official MySQL documentation says MySQL (aka Oracle) doesn't support moves from 5.1 to 5.6.

XI is not designed to run with InnoDB tables.

I have read changelog for mysql 5.6 and 5.7 and all improvements are based on innodb, and since nagios xi are not designed to run on innodb it does not have much sense to upgrade right now.

Did you change your /etc/cron.d/nagiosxi to decrease the frequency of running the dbmaint? You could run it once a day if you have plenty of space.

I did that

You mentioned you are doing tuning. Is https://assets.nagios.com/downloads/nag ... ios-XI.pdf the document you are using to do that?

Yes

You might see some improvement by offloading, but if you anticipate any growth, I would not do that.

[dwhitfield]

Can you send a fresh profile? At the very least, I'd like to see if the ipcs issue is resolved. The profile is so old at this point I don't trust it, and you've made some changes and I'd like to see if they have made any improvement.

It's worth mentioning that we aren't getting rid of your logs with the truncate. We aren't getting rid of the performance data either. If you've gone through the db repair document, a truncate may be the only way to get you going.

It was slightly inaccurate for me to say XI doesn't use InnoDB as some of the tables in the mysql db are InnoDB. My point was that you can just change the bulk of the MyISAM tables to InnoDB.

To prevent this from happening in the future, I would take a look at https://assets.nagios.com/downloads/nag ... ios-XI.pdf

Please note that we may be able to schedule a remote session if you submit a ticket at https://support.nagios.com/tickets/