Topic: Errors in message log after latest update

[AlexG]

Hi Forum

After the latest update following errors appear in the messages log:

Jan  5 13:21:26 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 22: Duplicate column name 'File_priv'
Jan  5 13:21:26 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 28: Duplicate column name 'Grant_priv'
Jan  5 13:21:26 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 29: Duplicate column name 'Grant_priv'
Jan  5 13:21:26 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 30: Duplicate column name 'Grant_priv'
Jan  5 13:21:26 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 41: Duplicate column name 'ssl_type'
Jan  5 13:21:27 sme-1 10fix_privilege_tables: ERROR 1054 (42S22) at line 87: Unknown column 'Type' in 'columns_priv'
Jan  5 13:21:27 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 93: Duplicate column name 'type'
Jan  5 13:21:27 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 103: Duplicate column name 'Show_db_priv'
Jan  5 13:21:27 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 120: Duplicate column name 'max_questions'
Jan  5 13:21:27 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 130: Duplicate column name 'Create_tmp_table_priv'
Jan  5 13:21:27 sme-1 10fix_privilege_tables: ERROR 1060 (42S21) at line 133: Duplicate column name 'Create_tmp_table_priv'
Jan  5 13:21:27 sme-1 10fix_privilege_tables: ERROR 1061 (42000) at line 141: Duplicate key name 'Grantor'

What do they mean? And what is to do to fix these errors?

Best regards
AlexG

[stephen noble]

These are known error messages.  A little searching would have netted this:

http://wiki.contribs.org/Updating_to_SME_7.2#10fix_privilege_tables_in_message_log

Which states this:

10fix_privilege_tables in message log

These messages are generated by
/usr/share/mysql/mysql_fix_privilege_tables.sql. The script itself says:

You can safely ignore all 'Duplicate column' and 'Unknown column' errors
because these just mean that your tables are already up to date.
This script is safe to run even if your tables are already up to date!