github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-21 14:06:26 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

MySQL database migration failed for upgrade to Gitea v1.12.0 #5599

New Issue
Closed
opened 2025-11-02 06:30:26 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 06:30:26 -06:00
Owner
Copy Link

Originally created by @lammel on GitHub (Jun 20, 2020).

  • Gitea version (or commit ref): v1.12
  • Operating system: Debian Buster
  • Database:
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

After upgrading from Gitea v1.11.6 to v1.12.0 a fatal error occured for the database migrations being performed during startup.

2020/06/20 10:11:28 ...es/setting/mailer.go:131:newNotifyMailService() [I] Notify Mail Service Enabled
2020/06/20 10:11:28 ...ueue_disk_channel.go:137:Run() [D] PersistableChannelQueue: mail Starting
2020/06/20 10:11:28 ...ue/queue_bytefifo.go:95:Run() [D] level: mail-level Starting
2020/06/20 10:11:28 routers/init.go:64:initDBEngine() [I] Beginning ORM engine initialization.
2020/06/20 10:11:28 routers/init.go:71:initDBEngine() [I] ORM engine initialization attempt #1/10...
2020/06/20 10:11:28 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql
2020/06/20 10:11:28 ...ueue_disk_channel.go:137:Run() [D] PersistableChannelQueue: notification-service Starting
2020/06/20 10:11:28 ...ue/queue_bytefifo.go:95:Run() [D] level: notification-service-level Starting
2020/06/20 10:11:28 ...ations/migrations.go:300:Migrate() [I] Migration[121]: add is_restricted column for users table
2020/06/20 10:11:28 routers/init.go:77:initDBEngine() [E] ORM engine initialization attempt #1/10 failed. Error: migrate: do migrate: Error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
2020/06/20 10:11:28 routers/init.go:78:initDBEngine() [I] Backing off for 5 seconds
...
2020/06/20 10:12:14 routers/init.go:71:initDBEngine() [I] ORM engine initialization attempt #10/10...
2020/06/20 10:12:14 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql
2020/06/20 10:12:14 ...ations/migrations.go:300:Migrate() [I] Migration[121]: add is_restricted column for users table
2020/06/20 10:12:14 routers/init.go:138:GlobalInit() [F] ORM engine initialization failed: migrate: do migrate: Error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

Gitea is not usable after the fatal error of course.
Reverting back to the previous running Gitea v1.11.6 immediately works.

So it seems for MySQL a rowsize limit is exceeded in the users table (just guessing).

Originally created by @lammel on GitHub (Jun 20, 2020). - Gitea version (or commit ref): v1.12 - Operating system: Debian Buster - Database: - [ ] 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 After upgrading from Gitea v1.11.6 to v1.12.0 a fatal error occured for the database migrations being performed during startup. ``` 2020/06/20 10:11:28 ...es/setting/mailer.go:131:newNotifyMailService() [I] Notify Mail Service Enabled 2020/06/20 10:11:28 ...ueue_disk_channel.go:137:Run() [D] PersistableChannelQueue: mail Starting 2020/06/20 10:11:28 ...ue/queue_bytefifo.go:95:Run() [D] level: mail-level Starting 2020/06/20 10:11:28 routers/init.go:64:initDBEngine() [I] Beginning ORM engine initialization. 2020/06/20 10:11:28 routers/init.go:71:initDBEngine() [I] ORM engine initialization attempt #1/10... 2020/06/20 10:11:28 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql 2020/06/20 10:11:28 ...ueue_disk_channel.go:137:Run() [D] PersistableChannelQueue: notification-service Starting 2020/06/20 10:11:28 ...ue/queue_bytefifo.go:95:Run() [D] level: notification-service-level Starting 2020/06/20 10:11:28 ...ations/migrations.go:300:Migrate() [I] Migration[121]: add is_restricted column for users table 2020/06/20 10:11:28 routers/init.go:77:initDBEngine() [E] ORM engine initialization attempt #1/10 failed. Error: migrate: do migrate: Error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs 2020/06/20 10:11:28 routers/init.go:78:initDBEngine() [I] Backing off for 5 seconds ... 2020/06/20 10:12:14 routers/init.go:71:initDBEngine() [I] ORM engine initialization attempt #10/10... 2020/06/20 10:12:14 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql 2020/06/20 10:12:14 ...ations/migrations.go:300:Migrate() [I] Migration[121]: add is_restricted column for users table 2020/06/20 10:12:14 routers/init.go:138:GlobalInit() [F] ORM engine initialization failed: migrate: do migrate: Error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs ``` Gitea is not usable after the fatal error of course. Reverting back to the previous running Gitea v1.11.6 immediately works. So it seems for MySQL a rowsize limit is exceeded in the users table (just guessing).
GiteaMirror added the issue/duplicate label 2025-11-02 06:30:26 -06:00
GiteaMirror commented 2025-11-02 06:30:27 -06:00
Author
Owner
Copy Link

@lammel commented on GitHub (Jun 20, 2020):

Might be related to #11976, but the error description there indicates another issue.

@lammel commented on GitHub (Jun 20, 2020): Might be related to #11976, but the error description there indicates another issue.
GiteaMirror commented 2025-11-02 06:30:27 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 20, 2020):

This is a duplicate of #9347 and #11984.

@zeripath commented on GitHub (Jun 20, 2020): This is a duplicate of #9347 and #11984.
GiteaMirror commented 2025-11-02 06:30:27 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jun 20, 2020):

The issue in #11976 appears unrelated.

@zeripath commented on GitHub (Jun 20, 2020): The issue in #11976 appears unrelated.
GiteaMirror commented 2025-11-02 06:30:27 -06:00
Author
Owner
Copy Link

@lammel commented on GitHub (Jun 20, 2020):

As pointed out in #9347, I just run gitea convert (see https://docs.gitea.io/en-us/command-line/#convert) and am up and running with v1.12.

root@bit:/opt/gitea/bin# ./gitea --config /etc/gitea/app.ini convert
2020/06/20 11:32:35 ...dules/setting/git.go:93:newGit() [I] Git Version: 2.20.1, Wire Protocol Version 2 Enabled
2020/06/20 11:32:35 cmd/convert.go:30:runConvert() [T] AppPath: /opt/gitea/bin/gitea
2020/06/20 11:32:35 cmd/convert.go:31:runConvert() [T] AppWorkPath: /opt/gitea/bin
2020/06/20 11:32:35 cmd/convert.go:32:runConvert() [T] Custom path: /opt/gitea/bin/custom
2020/06/20 11:32:35 cmd/convert.go:33:runConvert() [T] Log path: /var/log/gitea
Converted successfully, please confirm your database's character set is now utf8mb4

Sorry for the duplicate issue and thanks for the quick help.

@lammel commented on GitHub (Jun 20, 2020): As pointed out in #9347, I just run `gitea convert` (see https://docs.gitea.io/en-us/command-line/#convert) and am up and running with v1.12. ``` root@bit:/opt/gitea/bin# ./gitea --config /etc/gitea/app.ini convert 2020/06/20 11:32:35 ...dules/setting/git.go:93:newGit() [I] Git Version: 2.20.1, Wire Protocol Version 2 Enabled 2020/06/20 11:32:35 cmd/convert.go:30:runConvert() [T] AppPath: /opt/gitea/bin/gitea 2020/06/20 11:32:35 cmd/convert.go:31:runConvert() [T] AppWorkPath: /opt/gitea/bin 2020/06/20 11:32:35 cmd/convert.go:32:runConvert() [T] Custom path: /opt/gitea/bin/custom 2020/06/20 11:32:35 cmd/convert.go:33:runConvert() [T] Log path: /var/log/gitea Converted successfully, please confirm your database's character set is now utf8mb4 ``` Sorry for the duplicate issue and thanks for the quick help.
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 issue/duplicate
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#5599
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?