Migration from 1.11 to 1.12 failing #5594

Closed
opened 2025-11-02 06:30:16 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @cromerc on GitHub (Jun 19, 2020).

Description

Migration is failing for me under MySQL and now gitea doesn't start.
...

Screenshots

Originally created by @cromerc on GitHub (Jun 19, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.12.0 - Git version: 2.20.1 - Operating system: Debian Buster - Database (use `[x]`): - [ ] PostgreSQL - [X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: https://gist.github.com/cromerc/e1bcde4a00f5820fef4bff0fbfa08670 ## Description Migration is failing for me under MySQL and now gitea doesn't start. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/duplicate label 2025-11-02 06:30:16 -06:00
Author
Owner

@philippbeckmann commented on GitHub (Jun 19, 2020):

Please have a look at Issue https://github.com/go-gitea/gitea/issues/9347 and the documentation https://docs.gitea.io/en-us/command-line/#convert

PS: Don't forget to backup

@philippbeckmann commented on GitHub (Jun 19, 2020): Please have a look at Issue https://github.com/go-gitea/gitea/issues/9347 and the documentation https://docs.gitea.io/en-us/command-line/#convert PS: Don't forget to backup
Author
Owner

@cromerc commented on GitHub (Jun 19, 2020):

Thanks. The convert command line option fixed the database. Then I restarted gitea 1.12.0, it used up all the available memory on my VPS causing the server to lock up and for me to loose ssh access. I ended up having to reboot my VPS into rescue mode, disable gitea, and reboot the server. After that I tried running gitea again and now it works. I have no idea what happened during the first run of gitea 1.12.0... but it killed my server. But it looks like everything is working now.

@cromerc commented on GitHub (Jun 19, 2020): Thanks. The convert command line option fixed the database. Then I restarted gitea 1.12.0, it used up all the available memory on my VPS causing the server to lock up and for me to loose ssh access. I ended up having to reboot my VPS into rescue mode, disable gitea, and reboot the server. After that I tried running gitea again and now it works. I have no idea what happened during the first run of gitea 1.12.0... but it killed my server. But it looks like everything is working now.
Author
Owner

@lafriks commented on GitHub (Jun 19, 2020):

Duplicate of #11969

@lafriks commented on GitHub (Jun 19, 2020): Duplicate of #11969
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5594