Bug #85615 mysqld logging prior to doing an upgrade is rather alarming

• Submitted: 24 Mar 2017 15:34
• Modified: 30 Mar 2017 5:45
• Reporter: Simon Mudd (OCA)
• Status: Verified
• Category: MySQL Server: Installing
• Severity: S4 (Feature request)
• Version: 8.0.1
• OS: Any
• CPU Architecture: Any
• Tags: corrupt tables

[24 Mar 2017 15:34] Simon Mudd

Description:
When doing a in-place binary upgrade from 5.7.17 to 8.0.1 I notice the following error message:

2017-03-24T14:34:09.288896Z 25 [ERROR] /usr/sbin/mysqld: Column count of mysql.user is wrong. Expected 47, found 45. The table is probably corrupted
..
(there are other similar messages due to change in table structure)

This is rather alarming even if you know you're doing an upgrade.

How to repeat:
See the line above.

Suggested fix:
I'd suggest that you make a slightly less alarming message of the form:

2017-03-24T14:34:09.288896Z 25 [ERROR] /usr/sbin/mysqld: Column count of mysql.user is wrong. Expected 47, found 45. The table structure may be from a different version of mysql.

This is easier to understand: the problem is explained in the same way but the most likely reason for the discrepency is also given.

So not a big change but perhaps it might be good to adjust the text in the form indicated.

[30 Mar 2017 5:45] MySQL Verification Team

Hello Simon,

Thank you for the report and feedback!

Thanks,
Umesh