Re: [Maria-discuss] ERROR 1071 with mysql_upgrade

2019-07-16 Thread Sergei Golubchik
Hi, Reindl!

On Jul 16, Reindl Harald wrote:
> 
> 
> Am 16.07.19 um 21:13 schrieb Sergei Golubchik:
> > you can run mysql_fix_privilege_tables.sql manually. Like with
> > mysql -uroot -p -vvv < mysql_fix_privilege_tables.sql
> 
> how would that solve the issue of a obviously incompatible change in 10.4?

The question in the email was "How do I debug this?" and I tried to
answer it. My reply might help to find the statement that causes the
error, aborting the upgrade. Then we could look at why it fails, whether
it's something in 10.4, in mysql_upgrade, or some local change that the
user did, or may be something caused by FreeBSD patches.

> > On Jul 16, Erik Cederstrand wrote:
> >> Hi,
> >>
> >> I'm trying to upgrade a MariaDB 10.2 server to 10.4.6 on FreeBSD.
> >>
> >> When running the mysql_update command, it dies with:
> >>
> >> $ mysql_upgrade 
> >> Phase 1/7: Checking and upgrading mysql database
> >> Processing databases
> >> mysql
> > ...
> >> mysql.transaction_registry OK
> >> Phase 2/7: Installing used storage engines... Skipped
> >> Phase 3/7: Fixing views
> >> mysql.user OK
> >> Phase 4/7: Running 'mysql_fix_privilege_tables'
> >> ERROR 1071 (42000) at line 437: Specified key was too long; max key length 
> >> is 1000 bytes
> >> FATAL ERROR: Upgrade failed
> >>
> >> Adding verbose option does not give more hints, and the failing SQL
> >> statement doesn't seem to be logged with full query logging turned on.
> >>
> >> How do I debug this? I can't even see which table or column it's
> >> complaining about. I don't remember fiddling with collation or
> >> character sets on system tables.
> 
Regards,
Sergei
VP of MariaDB Server Engineering
and secur...@mariadb.org

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


Re: [Maria-discuss] ERROR 1071 with mysql_upgrade

2019-07-16 Thread Reindl Harald



Am 16.07.19 um 21:13 schrieb Sergei Golubchik:
> you can run mysql_fix_privilege_tables.sql manually. Like with
> mysql -uroot -p -vvv < mysql_fix_privilege_tables.sql

how would that solve the issue of a obviously incompatible change in 10.4?

> On Jul 16, Erik Cederstrand wrote:
>> Hi,
>>
>> I'm trying to upgrade a MariaDB 10.2 server to 10.4.6 on FreeBSD.
>>
>> When running the mysql_update command, it dies with:
>>
>> $ mysql_upgrade 
>> Phase 1/7: Checking and upgrading mysql database
>> Processing databases
>> mysql
> ...
>> mysql.transaction_registry OK
>> Phase 2/7: Installing used storage engines... Skipped
>> Phase 3/7: Fixing views
>> mysql.user OK
>> Phase 4/7: Running 'mysql_fix_privilege_tables'
>> ERROR 1071 (42000) at line 437: Specified key was too long; max key length 
>> is 1000 bytes
>> FATAL ERROR: Upgrade failed
>>
>> Adding verbose option does not give more hints, and the failing SQL
>> statement doesn't seem to be logged with full query logging turned on.
>>
>> How do I debug this? I can't even see which table or column it's
>> complaining about. I don't remember fiddling with collation or
>> character sets on system tables.


___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


Re: [Maria-discuss] ERROR 1071 with mysql_upgrade

2019-07-16 Thread Sergei Golubchik
Hi, Erik!

you can run mysql_fix_privilege_tables.sql manually. Like with
mysql -uroot -p -vvv < mysql_fix_privilege_tables.sql

Presuming FreeBSD installs this file somewhere. If it doesn't, you can
extract it from mysql_upgrade with strings, I suppose.

On Jul 16, Erik Cederstrand wrote:
> Hi,
> 
> I'm trying to upgrade a MariaDB 10.2 server to 10.4.6 on FreeBSD.
> 
> When running the mysql_update command, it dies with:
> 
> $ mysql_upgrade 
> Phase 1/7: Checking and upgrading mysql database
> Processing databases
> mysql
...
> mysql.transaction_registry OK
> Phase 2/7: Installing used storage engines... Skipped
> Phase 3/7: Fixing views
> mysql.user OK
> Phase 4/7: Running 'mysql_fix_privilege_tables'
> ERROR 1071 (42000) at line 437: Specified key was too long; max key length is 
> 1000 bytes
> FATAL ERROR: Upgrade failed
> 
> Adding verbose option does not give more hints, and the failing SQL
> statement doesn't seem to be logged with full query logging turned on.
> 
> How do I debug this? I can't even see which table or column it's
> complaining about. I don't remember fiddling with collation or
> character sets on system tables.
> 
> Kind regards,
> Erik

Regards,
Sergei
VP of MariaDB Server Engineering
and secur...@mariadb.org

___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


[Maria-discuss] ERROR 1071 with mysql_upgrade

2019-07-16 Thread Erik Cederstrand
Hi,

I'm trying to upgrade a MariaDB 10.2 server to 10.4.6 on FreeBSD.

When running the mysql_update command, it dies with:

$ mysql_upgrade 
Phase 1/7: Checking and upgrading mysql database
Processing databases
mysql
mysql.column_stats OK
mysql.columns_priv OK
mysql.db   OK
mysql.eventOK
mysql.func OK
mysql.global_priv  OK
mysql.gtid_slave_pos   OK
mysql.help_categoryOK
mysql.help_keyword OK
mysql.help_relationOK
mysql.help_topic   OK
mysql.index_stats  OK
mysql.innodb_index_stats   OK
mysql.innodb_table_stats   OK
mysql.plugin   OK
mysql.proc OK
mysql.procs_priv   OK
mysql.proxies_priv OK
mysql.roles_mappingOK
mysql.servers  OK
mysql.table_stats  OK
mysql.tables_priv  OK
mysql.time_zoneOK
mysql.time_zone_leap_secondOK
mysql.time_zone_name   OK
mysql.time_zone_transition OK
mysql.time_zone_transition_typeOK
mysql.transaction_registry OK
Phase 2/7: Installing used storage engines... Skipped
Phase 3/7: Fixing views
mysql.user OK
Phase 4/7: Running 'mysql_fix_privilege_tables'
ERROR 1071 (42000) at line 437: Specified key was too long; max key length is 
1000 bytes
FATAL ERROR: Upgrade failed


Adding verbose option does not give more hints, and the failing SQL statement 
doesn't seem to be logged with full query logging turned on.

How do I debug this? I can't even see which table or column it's complaining 
about. I don't remember fiddling with collation or character sets on system 
tables.

Kind regards,
Erik
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp