[arch-general] upgrading mysql to mariadb

[Martti Kühne]

Hi

On 3/29/13, David Benfell <benfell at parts-unknown.org> wrote:
[...]
> Phase 3/3: Running 'mysql_fix_privilege_tables'...
this.

> ERROR 1064 (42000) at line 87: You have an error in your SQL syntax;
> check the manual that corresponds to your MySQL server version for the
> right syntax to use near '(6) NOT NULL, user_host MEDIUMTEXT NOT NULL,
> thread_id INTEGER NOT NULL, server_' at line 1
and this.

> ERROR 1243 (HY000) at line 88: Unknown prepared statement handler
> (stmt) given to EXECUTE
> ERROR 1243 (HY000) at line 89: Unknown prepared statement handler
> (stmt) given to DEALLOCATE PREPARE
> ERROR 1064 (42000) at line 95: You have an error in your SQL syntax;
> check the manual that corresponds to your MySQL server version for the
> right syntax to use near '(6) NOT NULL, user_host MEDIUMTEXT NOT NULL,
> query_time TIME(6) NOT NULL, lock_t' at line 1
> ERROR 1243 (HY000) at line 96: Unknown prepared statement handler
> (stmt) given to EXECUTE
> ERROR 1243 (HY000) at line 97: Unknown prepared statement handler
> (stmt) given to DEALLOCATE PREPARE
> ERROR 1064 (42000) at line 343: You have an error in your SQL syntax;
> check the manual that corresponds to your MySQL server version for the
> right syntax to use near '(6) NOT NULL,
> ERROR 1064 (42000) at line 354: You have an error in your SQL syntax;
> check the manual that corresponds to your MySQL server version for the
> right syntax to use near '(6) NOT NULL,
> ERROR 1548 (HY000) at line 1136: Cannot load from mysql.proc. The
> table is probably corrupted
> ERROR 1548 (HY000) at line 1137: Cannot load from mysql.proc. The
> table is probably corrupted
> ERROR 1548 (HY000) at line 1150: Cannot load from mysql.proc. The
> table is probably corrupted
> FATAL ERROR: Upgrade failed
>


Your sites are up. You'll want to check if database users are unable
to log in. Expect that not all privilege tables look like they should
including triggers and all, so you'll either have to look into said
script, attempt to fix it and rerun on a backup (which includes the
internal schema)... But then, as it's not really a given to be sure
what the sum of what went wrong there is, you might be better off
migrating your dbs to a new working directory from dumps. The easiest
road would probably be downgrading to mysql for now (and grabbing
backups) and fixing the issues calmly with upstream.

Sorry to hear it didn't work.

cheers!
mar77i