gitea: Updated to latest version: Failed to initialize ORM engine

Gitea version (or commit ref): 1.5.0-linux-amd64
Git version: 2.11.0
Operating system: Debian 4.9.88-1+deb9u1 (2018-05-07)
Database (use [x]):
- PostgreSQL
- MySQL (Ver 15.1 Distrib 10.1.26-MariaDB, using readline 5.2)
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist: [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Sync2: Error 1709: Index column size too large. The maximum column size is 767 bytes

Description

Updated binary from v1.4.3 to v1.5.0 sha256sum is correct.

Unable to start, no more output. Above log gist is from logfile.

$ ./gitea-1.5.0-linux-amd64 
2018/08/10 20:41:02 [T] AppPath: /home/gitea/gitea-1.5.0-linux-amd64
2018/08/10 20:41:02 [T] AppWorkPath: /home/gitea
2018/08/10 20:41:02 [T] Custom path: /home/gitea/custom
2018/08/10 20:41:02 [T] Log path: /home/gitea/log

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 11
Comments: 17 (4 by maintainers)

Most upvoted comments

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;

+24

tscs37 on Aug 11, 2018

just delete records from team_unit and try again

lafriks on Aug 13, 2018

Ok but

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

moelski on Aug 30, 2018