Description
- Gitea version (or commit ref): 1.10.1
- Git version: 2.20.1
- Operating system: Debian 10
- Database (use
[x]
):- PostgreSQL
- MySQL
- [] MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist:
2019/12/07 11:13:44 routers/init.go:59:initDBEngine() [E] ORM engine initialization attempt #7/10 failed. Error: commands out of sync. Did you run multiple statements at once?
2019/12/07 11:13:44 routers/init.go:60:initDBEngine() [I] Backing off for 3 seconds
2019/12/07 11:13:47 routers/init.go:53:initDBEngine() [I] ORM engine initialization attempt #8/10...
2019/12/07 11:13:47 ...-xorm/xorm/engine.go:330:Ping() [I] PING DATABASE mysql
2019/12/07 11:13:47 routers/init.go:59:initDBEngine() [E] ORM engine initialization attempt #8/10 failed. Error: commands out of sync. Did you run multiple statements at once?
2019/12/07 11:13:47 routers/init.go:60:initDBEngine() [I] Backing off for 3 seconds
Description
I migrate my gitea from debian 10, mariadb 10.3 (from apt installed) from debian repo to
debian 10, mariadb 10.4 (from mariadb repository installed).
MySQL database has been dumped from 10.3 with:
mysqldump --single-transaction gitea > gitea.sql
Strict mode on new MariaDB 10.4 was disabled:
mysql -e 'select @@GLOBAL.sql_mode;'
+------------------------+
| @@GLOBAL.sql_mode |
+------------------------+
| NO_ENGINE_SUBSTITUTION |
+------------------------+
MySQL database name. user and password was correct.
Is there any ideas how to fix that ?
...