Unified Manager - MySQL log spamming, big error log of several GB
Applies to
Unified Manager 9.4/9.5
Issue
Mainly after upgrading from older MySQL versions lower than 5.7.23, we see error which seem to have no functional impact in the MySQL error logs. It is possible that the available capacity on the install drive is impacted since the log is not rotated and could grow infinite. It will also cause problems in handling the support bundle, which is collecting the file. It could huge- and not because of the database.
The relevant MySQL error log in the data directory is named [server_name].err
.
Location
RHEL/CentOS/OVA
/var/log/mysql/error.log or /opt/netapp/data/mysql/[server_name].err
Windows standard path
[install drive]:\ProgramData\MYSQL\MySQLServerData\Data\[server_name].err
The log gets spammed with messages like
2019-10-29T02:35:50.450367Z 0 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
2019-10-29T02:35:50.452470Z 0 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
2019-10-29T02:35:50.454512Z 0 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
2019-10-29T02:35:50.461723Z 0 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
2019-10-29T02:35:50.464300Z 0 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
As a result, the log could grow to sizes beyond 10GB. In an OVA, it might cause problems.