Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[E] Failed to initialize ORM engine: migrate: do migrate: pq: column "is_fsck_enabled" does not exist #3864

Closed
3 tasks
kenny-ngo opened this issue Apr 30, 2018 · 3 comments · Fixed by #3870
Closed
3 tasks
Labels
Milestone

Comments

@kenny-ngo
Copy link

This happens during migration.

  • Gitea version (or commit ref): v1.4.0
  • Git version:
  • Operating system: Ubuntu
  • Database (use [x]):
    • [ x ] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

Description

Compiled from source then try to execute the binary. That when this happens
gitea@slave:$ ./gitea web
2018/04/30 02:44:08 [T] AppPath: /home/gitea/gitea
2018/04/30 02:44:08 [T] AppWorkPath: /home/gitea
2018/04/30 02:44:08 [T] Custom path: /home/gitea/custom
2018/04/30 02:44:08 [T] Log path: /home/gitea/log
gitea@slave:
$ tail -10 log/gitea.log
2018/04/30 02:30:52 [I] Migration: adds comment to an action
2018/04/30 02:30:53 [I] Migration: regenerate git hooks
2018/04/30 02:30:53 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: pq: column "is_fsck_enabled" does not exist
2018/04/30 02:44:08 [I] Log Mode: File(Info)
2018/04/30 02:44:08 [I] XORM Log Mode: File(Info)
2018/04/30 02:44:08 [I] Cache Service Enabled
2018/04/30 02:44:08 [I] Session Service Enabled
2018/04/30 02:44:08 [I] Mail Service Enabled
2018/04/30 02:44:08 [I] Migration: regenerate git hooks
2018/04/30 02:44:08 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: pq: column "is_fsck_enabled" does not exist
gitea@slave:~$

Screenshots

@lafriks
Copy link
Member

lafriks commented Apr 30, 2018

From what version were you upgrading?

@lafriks
Copy link
Member

lafriks commented Apr 30, 2018

Can you try if cherry-picked changes from #3870 fixes migration for you?

@lafriks lafriks added this to the 1.5.0 milestone May 2, 2018
@cweickhmann
Copy link

I have the same problem coming from "e90bbca" and trying to use "2fcd9b6".

  • Gitea version (or commit ref): 2fcd9b6
  • Git version: 2.15.2
  • Operating system: Docker 18.03.1-ce, build 9ee9f40 on Ubuntu 16.04
  • Database
    • PostgreSQL (version: 9.6.3)
    • MySQL
    • MSSQL
    • SQLite

gitea=> select * from version; returns:

 id | version
----+---------
  1 |      39
(1 row)

which seems to be a rather new version. Is it possible that at some point, migration starts, fails and leaves the database schema saying it's a newer version than it actually is?

I've got a running container of an older gitea version (e90bbca), so we're not crashed here. But I don't get it, and the log entry is pretty cryptic, too.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants