Cannot recover from backup of gitea 1.4.0 #2178

Closed
opened 2025-11-02 04:26:17 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @fbettag on GitHub (Aug 12, 2018).

  • Gitea version (or commit ref):
  • Git version: 1.4.0
  • Operating system: FreeBSD 11.1 / Ubuntu 16.04
  • 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:

Description

Trying to migrate (dump/restore) on gitea 1.4.0 on FreeBSD and move it to Ubuntu 16.04 running 1.5.0. I also tried every major release from 1.0.0 to 1.5.0 and i always get "[E] Fail to initialize ORM engine: sync database struct error: Unknown col name in indexe" with a different column in each version.

This database dump works fine on FreeBSD but when i try to start gitea web on 1.4.0 on Ubuntu, it won't start. Ideally i want 1.5.0 but best of all would be a running version.

If i remove all columns in question, this goes as far as ssh keys owner_id, which gets removed. is there any manual way to do db migration?
...

Originally created by @fbettag on GitHub (Aug 12, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) 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): - Git version: 1.4.0 - Operating system: FreeBSD 11.1 / Ubuntu 16.04 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Trying to migrate (dump/restore) on gitea 1.4.0 on FreeBSD and move it to Ubuntu 16.04 running 1.5.0. I also tried every major release from 1.0.0 to 1.5.0 and i always get "[E] Fail to initialize ORM engine: sync database struct error: Unknown col name in indexe" with a different column in each version. This database dump works fine on FreeBSD but when i try to start gitea web on 1.4.0 on Ubuntu, it won't start. Ideally i want 1.5.0 but best of all would be a running version. If i remove all columns in question, this goes as far as ssh keys owner_id, which gets removed. is there any manual way to do db migration? ...
GiteaMirror added the type/questionissue/stale labels 2025-11-02 04:26:17 -06:00
Author
Owner

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

It would be recommended to first run same version as you were running on freebsd. Does it give you any error?

@lafriks commented on GitHub (Aug 12, 2018): It would be recommended to first run same version as you were running on freebsd. Does it give you any error?
Author
Owner

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

I already tried the 1.4.0 that my pkg info on freebsd shows me :) i downloaded the binary on Ubuntu with wget and i tried to alter table user drop column XYZ whatever it was reporting me.

To be totally honest, this was an old gogs installation that got migrated over with gitea 1.1. So i assume that there is still some db-fields that didn't get migrated.

@fbettag commented on GitHub (Aug 13, 2018): I already tried the 1.4.0 that my pkg info on freebsd shows me :) i downloaded the binary on Ubuntu with wget and i tried to alter table user drop column XYZ whatever it was reporting me. To be totally honest, this was an old gogs installation that got migrated over with gitea 1.1. So i assume that there is still some db-fields that didn't get migrated.
Author
Owner

@stale[bot] commented on GitHub (Jan 14, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 14, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2178