Updated to latest version: Failed to initialize ORM engine #2168

@Zeuh commented on GitHub (Aug 10, 2018):

This is probably caused by table charset set to utf8mb4 or when default charset table is utf8mb4.

By default, there is some restrictions on index size in InnoDB :

https://dev.mysql.com/doc/refman/5.5/en/innodb-restrictions.html

@Zeuh commented on GitHub (Aug 10, 2018): This is probably caused by table charset set to utf8mb4 or when default charset table is utf8mb4. By default, there is some restrictions on index size in InnoDB : - https://dev.mysql.com/doc/refman/5.5/en/innodb-restrictions.html

GiteaMirror commented

@Pofilo commented on GitHub (Aug 11, 2018):

Same problem on same OS with MySQL too.

@Pofilo commented on GitHub (Aug 11, 2018): Same problem on same OS with MySQL too.

GiteaMirror commented

@tobidope commented on GitHub (Aug 11, 2018):

Have the same problem on Centos. Do you plan to,fix this or document that utf8mb4 is not usable with your setup?

@tobidope commented on GitHub (Aug 11, 2018): Have the same problem on Centos. Do you plan to,fix this or document that utf8mb4 is not usable with your setup?

GiteaMirror commented

@tscs37 commented on GitHub (Aug 11, 2018):

Seems this is happening on Migration v68 on the Topic table:

[I] [SQL] CREATE UNIQUE INDEX `UQE_topic_name` ON `topic` (`name`)
[...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Sync2: Error 1071: Specified key was too long; max key length is 767 bytes

A temporary workaround is to convert the topic table to utf8 (only this table);

alter table topic convert to character set utf8 collate utf8_unicode_ci;

@tscs37 commented on GitHub (Aug 11, 2018): Seems this is happening on Migration [v68 on the Topic table](https://github.com/go-gitea/gitea/blob/master/models/migrations/v68.go#L28): ``` [I] [SQL] CREATE UNIQUE INDEX `UQE_topic_name` ON `topic` (`name`) [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Sync2: Error 1071: Specified key was too long; max key length is 767 bytes ``` A temporary workaround is to convert the topic table to utf8 (only this table); ```sql alter table topic convert to character set utf8 collate utf8_unicode_ci; ```

GiteaMirror commented

@akuzia commented on GitHub (Aug 11, 2018):

Had same behavior. Restored my db to 1.4.3 and then update binary. Worked, but with some data corruption on repository.description. Perhaps bad encoding. Example:

Скрипты бекапов => Ð¡ÐºÑ€Ð¸Ð¿Ñ‚Ñ‹ Ð±ÐµÐºÐ°Ð¿Ð¾Ð²

But I cant detect what coding it is.

And a bad migration on one instance:

2018/08/11 21:54:41 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Insert team units: Error 1062: Duplicate entry '1-1' for key 'UQE_team_unit_s'

Then the same ORM fail message.

@akuzia commented on GitHub (Aug 11, 2018): Had same behavior. Restored my db to 1.4.3 and then update binary. Worked, but with some data corruption on `repository.description`. Perhaps bad encoding. Example: ``` Скрипты бекапов => Ð¡ÐºÑ€Ð¸Ð¿Ñ‚Ñ‹ Ð±ÐµÐºÐ°Ð¿Ð¾Ð² ``` But I cant detect what coding it is. And a bad migration on one instance: ``` 2018/08/11 21:54:41 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Insert team units: Error 1062: Duplicate entry '1-1' for key 'UQE_team_unit_s' ``` Then the same ORM fail message.

GiteaMirror commented

@lafriks commented on GitHub (Aug 11, 2018):

Seems to be duplicate of #2979

@lafriks commented on GitHub (Aug 11, 2018): Seems to be duplicate of #2979

GiteaMirror commented

@tobidope commented on GitHub (Aug 12, 2018):

Setting the row_format to dynamic solved my issue with the topic table.

@tobidope commented on GitHub (Aug 12, 2018): Setting the row_format to dynamic solved my issue with the topic table.

GiteaMirror commented

@lunny commented on GitHub (Aug 12, 2018):

@trahibidadido just clear table team_unit and restart the gitea should resolve your issue. Your issue is different from others.

@lunny commented on GitHub (Aug 12, 2018): @trahibidadido just clear table `team_unit` and restart the gitea should resolve your issue. Your issue is different from others.

GiteaMirror commented

@ghost commented on GitHub (Aug 13, 2018):

Hi guys, I have a similar issue regarding team_unit migration:

2018/08/13 12:10:03 [I] Migration: move team units to team_unit table
2018/08/13 12:10:03 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Insert team units: UNIQUE constraint failed: team_unit.team_id, team_unit.type

It seems that such unique contraint already exists:

sqlite> .schema team_unit
CREATE TABLE `team_unit` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `org_id` INTEGER NULL, `team_id` INTEGER NULL, `type` INTEGER NULL);
CREATE UNIQUE INDEX `UQE_team_unit_s` ON `team_unit` (`team_id`,`type`);
CREATE INDEX `IDX_team_unit_org_id` ON `team_unit` (`org_id`);
sqlite> select * from team_unit;
1|4|1|1
2|4|1|2
3|4|1|3
4|4|1|4
5|4|1|5
6|4|1|6
7|4|1|7
8|17|4|1
9|17|4|2
10|17|4|3
11|17|4|4
12|17|4|5
13|17|4|6
14|17|4|7
15|36|6|1
16|36|6|2
17|36|6|3
18|36|6|4
19|36|6|5
20|36|6|6
21|36|6|7

@ghost commented on GitHub (Aug 13, 2018): Hi guys, I have a similar issue regarding `team_unit` migration: ``` 2018/08/13 12:10:03 [I] Migration: move team units to team_unit table 2018/08/13 12:10:03 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Insert team units: UNIQUE constraint failed: team_unit.team_id, team_unit.type ``` It seems that such unique contraint already exists: ``` sqlite> .schema team_unit CREATE TABLE `team_unit` (`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, `org_id` INTEGER NULL, `team_id` INTEGER NULL, `type` INTEGER NULL); CREATE UNIQUE INDEX `UQE_team_unit_s` ON `team_unit` (`team_id`,`type`); CREATE INDEX `IDX_team_unit_org_id` ON `team_unit` (`org_id`); sqlite> select * from team_unit; 1|4|1|1 2|4|1|2 3|4|1|3 4|4|1|4 5|4|1|5 6|4|1|6 7|4|1|7 8|17|4|1 9|17|4|2 10|17|4|3 11|17|4|4 12|17|4|5 13|17|4|6 14|17|4|7 15|36|6|1 16|36|6|2 17|36|6|3 18|36|6|4 19|36|6|5 20|36|6|6 21|36|6|7 ```

GiteaMirror commented

@lafriks commented on GitHub (Aug 13, 2018):

just delete records from team_unit and try again

@lafriks commented on GitHub (Aug 13, 2018): just delete records from `team_unit` and try again

GiteaMirror commented

@ghost commented on GitHub (Aug 13, 2018):

Worked perfectly. Thanks @lafriks

@ghost commented on GitHub (Aug 13, 2018): Worked perfectly. Thanks @lafriks

GiteaMirror commented

@moelski commented on GitHub (Aug 30, 2018):

Hi !
Just have the same issue ...
[...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Sync2: Error 1071: Specified key was too long; max key length is 767 bytes

What can I do now? Also using MariaDB 10.

regards Dominik

@moelski commented on GitHub (Aug 30, 2018): Hi ! Just have the same issue ... [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Sync2: Error 1071: Specified key was too long; max key length is 767 bytes But I have no table which is called team_unit: | star | | stopwatch | | team | | team_repo | | team_user | | topic | | tracked_time | What can I do now? Also using MariaDB 10. regards Dominik

GiteaMirror commented

@tobidope commented on GitHub (Aug 30, 2018):

Set the row_format to dynamic for each table having the problem.

@tobidope commented on GitHub (Aug 30, 2018): Set the row_format to dynamic for each table having the problem.

GiteaMirror commented

@moelski commented on GitHub (Aug 30, 2018):

Ok but

how can I determine the tables
how can I update the row_format
?

@moelski commented on GitHub (Aug 30, 2018): Ok but 1) how can I determine the tables 2) how can I update the row_format ?

GiteaMirror commented

@msphn commented on GitHub (Oct 6, 2018):

@moelski aside from the Gitea.log files, you'll find a file called xorm.log, there it should show all recent sql statements. The last one is the failing one.

@msphn commented on GitHub (Oct 6, 2018): @moelski aside from the Gitea.log files, you'll find a file called xorm.log, there it should show all recent sql statements. The last one is the failing one.

GiteaMirror commented