InnoDB error

This support forum board is for questions relating to Nagios Fusion.
Locked
cbeattie-unitrends
Posts: 79
Joined: Mon Oct 10, 2016 2:51 pm

InnoDB error

Post by cbeattie-unitrends »

Hello,

I see InnoDB errors when I look in /var/log/mariadb/mariadb.log on my Fusion server:
[root@den-fusion ~]# tail /var/log/mariadb/mariadb.log
190730 21:12:24 InnoDB: ERROR: the age of the last checkpoint is 9440306,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
190730 21:18:28 InnoDB: ERROR: the age of the last checkpoint is 9440864,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
What can I do to fix that?
User avatar
lmiltchev
Former Nagios Staff
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: InnoDB error

Post by lmiltchev »

What is the version of Nagios Fusion that you are currently using?

Can you show us the output of the following command?

Code: Select all

cat /etc/my.cnf
Be sure to check out our Knowledgebase for helpful articles and solutions!
cbeattie-unitrends
Posts: 79
Joined: Mon Oct 10, 2016 2:51 pm

Re: InnoDB error

Post by cbeattie-unitrends »

Fusion is version 4.1.7, and it's running on CentOS 7.6.1810. Fusion appears to be running okay. I discovered this almost by accident.

We have 7 fused Nagios instances, 1 Core and 6 XI monitoring 3K+ hosts and 82K+ services.

my.cnf looks like this:
[root@den-fusion ~]# cat /etc/my.cnf
[mysqld]
innodb_file_per_table = 1
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mariadb according to the
# instructions in http://fedoraproject.org/wiki/Systemd


# Added by Nagios 2017-08-18 08:06:58
max_allowed_packet = 32M

# Added by Nagios 2017-08-18 08:06:58
query_cache_size = 16M

# Added by Nagios 2017-08-18 08:06:58
query_cache_limit = 4M

# Added by Nagios 2017-08-18 08:06:58
tmp_table_size = 64M

# Added by Nagios 2017-08-18 08:06:58
max_heap_table_size = 64M

# Added by Nagios 2017-08-18 08:06:58
key_buffer_size = 32M

# Added by Nagios 2017-08-18 08:06:58
table_open_cache = 32

[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log
pid-file=/var/run/mariadb/mariadb.pid

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d

[root@den-fusion ~]#
User avatar
lmiltchev
Former Nagios Staff
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: InnoDB error

Post by lmiltchev »

OK, try the following:

1. Add these three lines to the /etc/my.cnf file under the [mysqld] section:

Code: Select all

innodb_log_buffer_size = 32M
innodb_buffer_pool_size = 1G
innodb_log_file_size = 256M
Save, and exit.

2. Stop mariadb.

Code: Select all

systemctl stop mariadb.service
3. Remove the ib_logfile0 and ib_logfile1 log files. Don't worry - they will be rebuild on starting mariadb.

Code: Select all

rm -f /var/lib/mysql/ib_logfile*
Note: If you wanted to play safe, you could move the files to /tmp.

Code: Select all

mv /var/lib/mysql/ib_logfile* /tmp
4. Start mariadb.

Code: Select all

systemctl start mariadb.service

Let us know if this helped.
Be sure to check out our Knowledgebase for helpful articles and solutions!
cbeattie-unitrends
Posts: 79
Joined: Mon Oct 10, 2016 2:51 pm

Re: InnoDB error

Post by cbeattie-unitrends »

Prior to your suggested fixes, there'd be a new error message in the log every few minutes. It's been more than half a day and the log file has no complaints.

Feel free to close and lock this thread.

Thanks!
User avatar
mbellerue
Posts: 1403
Joined: Fri Jul 12, 2019 11:10 am

Re: InnoDB error

Post by mbellerue »

Glad to hear it's working! Closing thread.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked