github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Migration failure 1.7.6->1.8.0: No such index: IDX_user_"idx_user_IDX_user_is_active" #3232

New Issue
Closed
opened 2025-11-02 05:04:57 -06:00 by GiteaMirror · 19 comments
GiteaMirror commented 2025-11-02 05:04:57 -06:00
Owner
Copy Link

Originally created by @tadly on GitHub (Apr 23, 2019).

  • Gitea version (or commit ref): 1.7.6
  • Git version: ---
  • Operating system: docker
  • 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/04/23 11:48:27 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"idx_user_IDX_user_is_active"
2019/04/23 11:48:27 [I] Log Mode: File(Info)
2019/04/23 11:48:27 [I] XORM Log Mode: File(Info)
2019/04/23 11:48:27 [I] Cache Service Enabled
2019/04/23 11:48:27 [I] Session Service Enabled
2019/04/23 11:48:27 [I] Mail Service Enabled
2019/04/23 11:48:27 [I] Notify Mail Service Enabled
2019/04/23 11:48:27 [I] Beginning ORM engine initialization.
2019/04/23 11:48:27 [I] ORM engine initialization attempt #1/10...
2019/04/23 11:48:27 [I] Migration: add theme to users
2019/04/23 11:48:27 [I] Backing off for 3 seconds
2019/04/23 11:48:30 [I] ORM engine initialization attempt #2/10...
2019/04/23 11:48:30 [I] Migration: add theme to users
2019/04/23 11:48:30 [I] Backing off for 3 seconds
2019/04/23 11:48:33 [I] ORM engine initialization attempt #3/10...
2019/04/23 11:48:33 [I] Migration: add theme to users
2019/04/23 11:48:33 [I] Backing off for 3 seconds
...

Description

I made sure every version from 1.7.0 up to 1.7.6 was working.
As soon as I upgrade from 1.7.6 to 1.8.0 I get the above error.

Indexes do exist and there's also one for idx_user_IDX_user_is_active

$ sqlite3 gitea.db .indexes | grep user_is_active
idx_user_IDX_user_is_active
Originally created by @tadly on GitHub (Apr 23, 2019). <!-- 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.7.6 - Git version: --- - Operating system: docker - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ``` 2019/04/23 11:48:27 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"idx_user_IDX_user_is_active" 2019/04/23 11:48:27 [I] Log Mode: File(Info) 2019/04/23 11:48:27 [I] XORM Log Mode: File(Info) 2019/04/23 11:48:27 [I] Cache Service Enabled 2019/04/23 11:48:27 [I] Session Service Enabled 2019/04/23 11:48:27 [I] Mail Service Enabled 2019/04/23 11:48:27 [I] Notify Mail Service Enabled 2019/04/23 11:48:27 [I] Beginning ORM engine initialization. 2019/04/23 11:48:27 [I] ORM engine initialization attempt #1/10... 2019/04/23 11:48:27 [I] Migration: add theme to users 2019/04/23 11:48:27 [I] Backing off for 3 seconds 2019/04/23 11:48:30 [I] ORM engine initialization attempt #2/10... 2019/04/23 11:48:30 [I] Migration: add theme to users 2019/04/23 11:48:30 [I] Backing off for 3 seconds 2019/04/23 11:48:33 [I] ORM engine initialization attempt #3/10... 2019/04/23 11:48:33 [I] Migration: add theme to users 2019/04/23 11:48:33 [I] Backing off for 3 seconds ... ``` ## Description I made sure every version from 1.7.0 up to 1.7.6 was working. As soon as I upgrade from 1.7.6 to 1.8.0 I get the above error. Indexes do exist and there's also one for `idx_user_IDX_user_is_active` ```sh $ sqlite3 gitea.db .indexes | grep user_is_active idx_user_IDX_user_is_active ```
GiteaMirror added the type/bug label 2025-11-02 05:04:57 -06:00
GiteaMirror commented 2025-11-02 05:04:58 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Apr 23, 2019):

Looks like this is https://github.com/go-gitea/gitea/pull/5681 but it was fixed not sure why this is happening ..


$ sqlite3 gitea.db
$ UPDATE users SET theme=""
@adelowo commented on GitHub (Apr 23, 2019): Looks like this is https://github.com/go-gitea/gitea/pull/5681 but it was fixed not sure why this is happening .. ``` $ sqlite3 gitea.db $ UPDATE users SET theme="" ```
GiteaMirror commented 2025-11-02 05:04:58 -06:00
Author
Owner
Copy Link

@tadly commented on GitHub (Apr 23, 2019):

Nope, not it especially as the error says: no such index: IDX_user_"idx_user_IDX_user_is_active"
I did try your suggestion anyways but again, didn't work.

The first IDX_user_ prefix seems to much. No idea where this one is coming from though.

@tadly commented on GitHub (Apr 23, 2019): Nope, not it especially as the error says: `no such index: IDX_user_"idx_user_IDX_user_is_active"` I did try your suggestion anyways but again, didn't work. The first `IDX_user_` prefix seems to much. No idea where this one is coming from though.
GiteaMirror commented 2025-11-02 05:04:58 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Apr 23, 2019):

The log you pasted doesn’t contain anything related to indexes though

@adelowo commented on GitHub (Apr 23, 2019): The log you pasted doesn’t contain anything related to indexes though
GiteaMirror commented 2025-11-02 05:04:58 -06:00
Author
Owner
Copy Link

@tadly commented on GitHub (Apr 23, 2019):

Uhm the very first line?

2019/04/23 11:48:27 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"idx_user_IDX_user_is_active"

specifically: no such index

Anyways, the fact it says "idx_user_IDX_user_is_active" is wrong already which I've manually fixed but it still prefixes it with an additional IDX_user_.

So currently I'm stuck at

ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"IDX_user_created_unix"

while it should be just IDX_user_created_unix

Will have to investigate more some time later as I'm rather busy right now :(

@tadly commented on GitHub (Apr 23, 2019): Uhm the very first line? ``` 2019/04/23 11:48:27 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"idx_user_IDX_user_is_active" ``` specifically: `no such index` Anyways, the fact it says `"idx_user_IDX_user_is_active"` is wrong already which I've manually fixed but it still prefixes it with an additional `IDX_user_`. So currently I'm stuck at ``` ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"IDX_user_created_unix" ``` while it **should be** just `IDX_user_created_unix` Will have to investigate more some time later as I'm rather busy right now :(
GiteaMirror commented 2025-11-02 05:04:59 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Apr 23, 2019):

OK let's try to figure out which migration is doing this. What's the version number of your database?

SELECT * from Version;
@zeripath commented on GitHub (Apr 23, 2019): OK let's try to figure out which migration is doing this. What's the version number of your database? ```sql SELECT * from Version; ```
GiteaMirror commented 2025-11-02 05:04:59 -06:00
Author
Owner
Copy Link

@tadly commented on GitHub (Apr 24, 2019):

Sorry for the delay. First of, I'm using the official docker image and am curious how the upgrade strategy for gitea usually is. Do you have to make sure you hit every version or could you (in theory) go from 1.7.0 straight to 1.8.0

As for the version, 77 is what I get.
Seems like I'm missing quite a bit... 78 - 84 ._.
As to how to apply them I'm not quite sure 🙄

@tadly commented on GitHub (Apr 24, 2019): Sorry for the delay. First of, I'm using the official [docker image](https://hub.docker.com/r/gitea/gitea) and am curious how the upgrade strategy for gitea usually is. Do you **have to** make sure you hit every version or could you (in theory) go from 1.7.0 straight to 1.8.0 As for the version, `77` is what I get. Seems like I'm missing quite a bit... 78 - 84 ._. As to how to apply them I'm not quite sure 🙄
GiteaMirror commented 2025-11-02 05:04:59 -06:00
Author
Owner
Copy Link

@Cellebyte commented on GitHub (Apr 24, 2019):

Same here from 1.7.3 to 1.8 Docker image.

2019/04/24 07:50:00 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: Drop column failed: mssql: ALTER TABLE DROP COLUMN is_bare failed because one or more objects access this column

I will try to upgrade to 1.7.latest and then to 1.8 but i think the migrate is not working from 1.7 to 1.8

Tried it is not working.

@Cellebyte commented on GitHub (Apr 24, 2019): Same here from 1.7.3 to 1.8 Docker image. ``` 2019/04/24 07:50:00 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: Drop column failed: mssql: ALTER TABLE DROP COLUMN is_bare failed because one or more objects access this column ``` I will try to upgrade to 1.7.latest and then to 1.8 but i think the migrate is not working from 1.7 to 1.8 Tried it is not working.
GiteaMirror commented 2025-11-02 05:04:59 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Apr 24, 2019):

Oh sorry, I was on mobile and didn't see that :)

@adelowo commented on GitHub (Apr 24, 2019): Oh sorry, I was on mobile and didn't see that :)
GiteaMirror commented 2025-11-02 05:05:00 -06:00
Author
Owner
Copy Link

@ChriFo commented on GitHub (Apr 24, 2019):

I am running v1.7.6 from Docker image with PostgreSQL.
Currently I am at version 77.

And I think I should wait with upgrade to 1.8 😃

@ChriFo commented on GitHub (Apr 24, 2019): I am running v1.7.6 from Docker image with PostgreSQL. Currently I am at version 77. And I think I should wait with upgrade to 1.8 :smiley:
GiteaMirror commented 2025-11-02 05:05:00 -06:00
Author
Owner
Copy Link

@xor-gate commented on GitHub (Apr 24, 2019):

Same for me with Version 78.

2019/04/24 10:14:10 [I] Backing off for 3 seconds
2019/04/24 10:14:13 [I] ORM engine initialization attempt #10/10...
2019/04/24 10:14:13 [I] Migration: rename repo is_bare to repo is_empty
2019/04/24 10:14:13 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: Drop index failed: Error 1091: Can't DROP INDEX `IDX_repository_is_ba
re`; check that it exists

b80d6490f3/models/migrations/v78.go (L37)

@xor-gate commented on GitHub (Apr 24, 2019): Same for me with Version 78. ``` 2019/04/24 10:14:10 [I] Backing off for 3 seconds 2019/04/24 10:14:13 [I] ORM engine initialization attempt #10/10... 2019/04/24 10:14:13 [I] Migration: rename repo is_bare to repo is_empty 2019/04/24 10:14:13 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: Drop index failed: Error 1091: Can't DROP INDEX `IDX_repository_is_ba re`; check that it exists ``` https://github.com/go-gitea/gitea/blob/b80d6490f31d2dde2e12aeb7a68236bae5f6809d/models/migrations/v78.go#L37
GiteaMirror commented 2025-11-02 05:05:00 -06:00
Author
Owner
Copy Link

@xor-gate commented on GitHub (Apr 24, 2019):

Fixed for me with:

MariaDB [gitea]> CREATE INDEX IDX_repository_is_bare ON repository(is_bare);
Query OK, 0 rows affected (0.03 sec)
Records: 0  Duplicates: 0  Warnings: 0

MariaDB [gitea]> quit
Bye
root@src02:/home/git/gitea# tail -f log/gitea.log
2019/04/24 10:27:06 [I] Migration: update U2F counter type
2019/04/24 10:27:06 [I] Migration: hot fix for wrong release sha1 on release table
2019/04/24 10:27:06 [I] ORM engine initialization successful!
2019/04/24 10:27:07 [I] Git Version: 2.1.4
2019/04/24 10:27:07 [I] SQLite3 Supported
2019/04/24 10:27:07 [I] Run Mode: Production
2019/04/24 10:27:07 [...gitea/models/pull.go:1464 TestPullRequests()] [E] testPatch: git read-tree --index-output=/tmp/gitea-am-45990841 release/1.24.0: exec(5:testPatch (git read-tree): 23) failed: exit status 128(<nil>) stdout:  stderr: fatal: Not a valid object name release/1.24.0
 - fatal: Not a valid object name release/1.24.0

2019/04/24 10:27:07 [I] Listen: http://0.0.0.0:3000/git
@xor-gate commented on GitHub (Apr 24, 2019): Fixed for me with: ``` MariaDB [gitea]> CREATE INDEX IDX_repository_is_bare ON repository(is_bare); Query OK, 0 rows affected (0.03 sec) Records: 0 Duplicates: 0 Warnings: 0 MariaDB [gitea]> quit Bye root@src02:/home/git/gitea# tail -f log/gitea.log 2019/04/24 10:27:06 [I] Migration: update U2F counter type 2019/04/24 10:27:06 [I] Migration: hot fix for wrong release sha1 on release table 2019/04/24 10:27:06 [I] ORM engine initialization successful! 2019/04/24 10:27:07 [I] Git Version: 2.1.4 2019/04/24 10:27:07 [I] SQLite3 Supported 2019/04/24 10:27:07 [I] Run Mode: Production 2019/04/24 10:27:07 [...gitea/models/pull.go:1464 TestPullRequests()] [E] testPatch: git read-tree --index-output=/tmp/gitea-am-45990841 release/1.24.0: exec(5:testPatch (git read-tree): 23) failed: exit status 128(<nil>) stdout: stderr: fatal: Not a valid object name release/1.24.0 - fatal: Not a valid object name release/1.24.0 2019/04/24 10:27:07 [I] Listen: http://0.0.0.0:3000/git ```
GiteaMirror commented 2025-11-02 05:05:01 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Apr 24, 2019):

Will send a fix after lunch

@adelowo commented on GitHub (Apr 24, 2019): Will send a fix after lunch
GiteaMirror commented 2025-11-02 05:05:01 -06:00
Author
Owner
Copy Link

@ChriFo commented on GitHub (Apr 24, 2019):

I am running v1.7.6 from Docker image with PostgreSQL.
Currently I am at version 77.

And I think I should wait with upgrade to 1.8 😃

Update to 1.8 was successful. Current version is 83.

@ChriFo commented on GitHub (Apr 24, 2019): > I am running v1.7.6 from Docker image with PostgreSQL. > Currently I am at version 77. > > And I think I should wait with upgrade to 1.8 😃 Update to 1.8 was successful. Current version is 83.
GiteaMirror commented 2025-11-02 05:05:01 -06:00
Author
Owner
Copy Link

@Cellebyte commented on GitHub (Apr 24, 2019):

Same here for MSSQL from 1.7.6 to 1.8 Docker image.

2019/04/24 07:50:00 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: Drop column failed: mssql: ALTER TABLE DROP COLUMN is_bare failed because one or more objects access this column

Cannot upgrade.

@Cellebyte commented on GitHub (Apr 24, 2019): Same here for MSSQL from 1.7.6 to 1.8 Docker image. ``` 2019/04/24 07:50:00 [...itea/routers/init.go:82 GlobalInit()] [E] ORM engine initialization failed: migrate: do migrate: Drop column failed: mssql: ALTER TABLE DROP COLUMN is_bare failed because one or more objects access this column ``` Cannot upgrade.
GiteaMirror commented 2025-11-02 05:05:01 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Apr 24, 2019):

@lafriks Since my pr doesn't fix everything, can we reopen this? The original post says ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"idx_user_IDX_user_is_active"

@adelowo commented on GitHub (Apr 24, 2019): @lafriks Since my pr doesn't fix everything, can we reopen this? The original post says `ORM engine initialization failed: migrate: do migrate: no such index: IDX_user_"idx_user_IDX_user_is_active"`
GiteaMirror commented 2025-11-02 05:05:02 -06:00
Author
Owner
Copy Link

@tadly commented on GitHub (Apr 24, 2019):

I do suspect that this is just my db being borked and not a general issue (the IDX_user_"idx_user_IDX_user_is_active" thing)

Still would appreciate it if anyone could help me fix this as doing a fresh setup would be rather tedious and time-consuming 😅

@tadly commented on GitHub (Apr 24, 2019): I do suspect that this is just **my** db being borked and not a general issue (the `IDX_user_"idx_user_IDX_user_is_active"` thing) Still would appreciate it if anyone could help me fix this as doing a fresh setup would be rather tedious and time-consuming :sweat_smile:
GiteaMirror commented 2025-11-02 05:05:02 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Apr 24, 2019):

Try setting your version to 78 to skip the v78 migration - but do the work of the migration by hand.

@zeripath commented on GitHub (Apr 24, 2019): Try setting your version to 78 to skip the v78 migration - but do the work of the migration by hand.
GiteaMirror commented 2025-11-02 05:05:02 -06:00
Author
Owner
Copy Link

@tadly commented on GitHub (Apr 25, 2019):

@zeripath Actually did that already but now gitea isn't doing anything on startup.
Nothing in the logs (even if I set the level to Debug) and the version stays at 78 :/

I ended up doing the most stupid thing I could think of (Spoiler, it's working now):

  1. Manually drop all indexes (So everything from .indexes including the unique ones even though they would fail but I didn't care :D)
  2. Select all indexes from a fresh setup (SELECT sql FROM sqlite_master WHERE type == 'index';)
  3. Recreate all indexes using the previous commands
  4. database is locked (WhatTheHeckWhyNowAllOfASuddon.jpg)
  5. indexes where recreated automatically
  6. DB-Version is 85 now

I have this bad feeling that this isn't the last of it and that my db is quite messed up but that's not your guys fault.

Thanks for the help. I think we can close the issue again unless there are any objections?

@tadly commented on GitHub (Apr 25, 2019): @zeripath Actually did that already but now gitea isn't doing anything on startup. Nothing in the logs (even if I set the level to `Debug`) and the version stays at 78 :/ I ended up doing the most stupid thing I could think of (Spoiler, it's working now): 1. Manually drop **all** indexes (So everything from `.indexes` including the unique ones even though they would fail but I didn't care :D) 2. Select all indexes from a fresh setup (`SELECT sql FROM sqlite_master WHERE type == 'index';`) 3. Recreate all indexes using the previous commands 4. `database is locked` (_WhatTheHeckWhyNowAllOfASuddon.jpg_) 5. _indexes where recreated automatically_ 6. DB-Version is `85` now I have this bad feeling that this isn't the last of it and that my db is quite messed up but that's not your guys fault. Thanks for the help. I think we can close the issue again unless there are any objections?
GiteaMirror commented 2025-11-02 05:05:02 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Apr 26, 2019):

@tadly so it looks like you had a particularly broken db, I'm not sure how. I don't think models/migrations/v78.go could be responsible for that. Especially if the next migration in line fails too.

Dropping all the indexes and recreating them should be fine though.

Therefore I'm going to close this issue - I'm also going to change the title as I don't want people to refer to this unless they actually have a similar index problem - in which case we can reopen and reinvestigate.

@zeripath commented on GitHub (Apr 26, 2019): @tadly so it looks like you had a particularly broken db, I'm not sure how. I don't think `models/migrations/v78.go` could be responsible for that. Especially if the next migration in line fails too. Dropping all the indexes and recreating them should be fine though. Therefore I'm going to close this issue - I'm also going to change the title as I don't want people to refer to this unless they actually have a similar index problem - in which case we can reopen and reinvestigate.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3232
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?