migrate 1.3.2 to 1.4.2 ORM engine errors #1905

New Issue

GiteaMirror · 2025-11-02T04:17:23-06:00

GiteaMirror commented

2025-11-02 04:17:23 -06:00

Originally created by @mariuspana on GitHub (Jun 9, 2018).

Gitea version (or commit ref):
Git version: 2.7.4
Operating system: Ubuntu 16.04 running on SmartOS (joyent_20171012T005133Z) lx-branded zone
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:

Description

Hi,

After upgrading to 1.4.2 our gitea site is no longer usable. Enabling debug logging we catch the following errors:

[...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Error 1054: Unknown column 'index' in 'field list'

and some regarding apache reverse proxy:

[Sat Jun 09 10:43:46.078346 2018] [proxy:error] [pid 57630:tid 140736586581760] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s
[Sat Jun 09 10:43:46.078358 2018] [proxy_http:error] [pid 57630:tid 140736586581760] [client 89.136.157.123:52268] AH01114: HTTP: failed to make connection to backend: 127.0.0.1

Downgrading to 1.3.2 results in the same behaviour. Any ideas on how to go about identifying the SQL errors and resolving those?

Originally created by @mariuspana on GitHub (Jun 9, 2018).  - Gitea version (or commit ref): - Git version: 2.7.4 - Operating system: Ubuntu 16.04 running on SmartOS (joyent_20171012T005133Z) lx-branded zone - 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: ## Description Hi, After upgrading to 1.4.2 our gitea site is no longer usable. Enabling debug logging we catch the following errors: [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: Error 1054: Unknown column 'index' in 'field list' and some regarding apache reverse proxy: [Sat Jun 09 10:43:46.078346 2018] [proxy:error] [pid 57630:tid 140736586581760] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s [Sat Jun 09 10:43:46.078358 2018] [proxy_http:error] [pid 57630:tid 140736586581760] [client 89.136.157.123:52268] AH01114: HTTP: failed to make connection to backend: 127.0.0.1 Downgrading to 1.3.2 results in the same behaviour. Any ideas on how to go about identifying the SQL errors and resolving those?

GiteaMirror closed this issue

2025-11-02 04:17:23 -06:00

GiteaMirror commented

2025-11-02 04:17:24 -06:00

@mariuspana commented on GitHub (Jun 10, 2018):

This seems to actually stem from our lx-branded zones. We've identified a core dump every time we hit an 500 error. I will close this as it is most likely not related directly to gitea but rather golang under lx.

@mariuspana commented on GitHub (Jun 10, 2018): This seems to actually stem from our lx-branded zones. We've identified a core dump every time we hit an 500 error. I will close this as it is most likely not related directly to gitea but rather golang under lx.

GiteaMirror commented

2025-11-02 04:17:25 -06:00

@mrbesen commented on GitHub (Jul 9, 2018):

I had the same problem. I tested the versions:
1.5, 1.4.2, 1.3.2 and 1.2.0 after i started every version in the order i mentioned, it some how fixed it self as i run 1.1.0 after i noticed that, i started
./gitea-1.2.0-linux-amd64 web with the following version order:
1.2.0 -> 1.3.2 -> 1.4.2 -> 1.5 and its some how working with 1.5 right now.
I have no idea what i did, but it somehow fixed it self.
here is my log
i run Ubuntu 16.04.04 64bit, with mysql

@mrbesen commented on GitHub (Jul 9, 2018): I had the same problem. I tested the versions: 1.5, 1.4.2, 1.3.2 and 1.2.0 after i started every version in the order i mentioned, it some how fixed it self as i run 1.1.0 after i noticed that, i started ``` ./gitea-1.2.0-linux-amd64 web``` with the following version order: 1.2.0 -> 1.3.2 -> 1.4.2 -> 1.5 and its some how working with 1.5 right now. I have no idea what i did, but it somehow fixed it self. here is my [log](https://pastebin.com/bRui7baX) i run Ubuntu 16.04.04 64bit, with mysql

GiteaMirror referenced this issue

2025-11-02 12:02:36 -06:00

[PR #1905] [MERGED] Require token before checking membership/ownership #16113

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#1905