github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 12:46:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

error during dump command: Failed to dump database: no such table: user #2712

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

Originally created by @jryan128 on GitHub (Jan 5, 2019).

  • Gitea version (or commit ref): 1.6.2 built with: bindata, sqlite
  • Git version: git version 2.11.0
  • Operating system: Debian
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

git@gitea:~$` gitea dump -c /etc/gitea/app.ini
2019/01/05 20:38:55 Creating tmp work dir: /tmp/gitea-dump-249881383
2019/01/05 20:38:55 Dumping local repositories.../home/git/gitea-repositories
2019/01/05 20:38:56 Dumping database...
2019/01/05 20:38:56 Failed to dump database: no such table: user

Originally created by @jryan128 on GitHub (Jan 5, 2019). <!-- 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): 1.6.2 built with: bindata, sqlite - Git version: git version 2.11.0 - Operating system: Debian - 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 ## Description git@gitea:~$` gitea dump -c /etc/gitea/app.ini 2019/01/05 20:38:55 Creating tmp work dir: /tmp/gitea-dump-249881383 2019/01/05 20:38:55 Dumping local repositories.../home/git/gitea-repositories 2019/01/05 20:38:56 Dumping database... 2019/01/05 20:38:56 Failed to dump database: no such table: user
GiteaMirror added the type/bug label 2025-11-02 04:45:18 -06:00
GiteaMirror commented 2025-11-02 04:45:19 -06:00
Author
Owner
Copy Link

@mikescandy commented on GitHub (Jan 24, 2019):

Confirm the issue also with version 1.7.0 (also using SQLite)

@mikescandy commented on GitHub (Jan 24, 2019): Confirm the issue also with version 1.7.0 (also using SQLite)
GiteaMirror commented 2025-11-02 04:45:19 -06:00
Author
Owner
Copy Link

@Lord-Y commented on GitHub (Jan 25, 2019):

Got the same issue. In your app.ini if you change PATH = data/gitea.db by PATH = YOUR_FULL_PATH/data/gitea.db, it'll works.

@Lord-Y commented on GitHub (Jan 25, 2019): Got the same issue. In your app.ini if you change `PATH = data/gitea.db` by `PATH = YOUR_FULL_PATH/data/gitea.db`, it'll works.
GiteaMirror commented 2025-11-02 04:45:19 -06:00
Author
Owner
Copy Link

@jryan128 commented on GitHub (Jan 25, 2019):

Replacing relative path with absolute path in db.PATH does fix the issue for me.

@jryan128 commented on GitHub (Jan 25, 2019): Replacing relative path with absolute path in db.PATH does fix the issue for me.
GiteaMirror commented 2025-11-02 04:45:19 -06:00
Author
Owner
Copy Link

@msreedata commented on GitHub (Apr 13, 2019):

As @jryan128 mentioned, absolute path works fine.
Also if you do a pushd/cd to the gitea workdir and run the backup command (without changing the db.PATH to absolute path in app.ini), the backup goes through fine.

@msreedata commented on GitHub (Apr 13, 2019): As @jryan128 mentioned, absolute path works fine. Also if you do a pushd/cd to the gitea workdir and run the backup command (without changing the db.PATH to absolute path in app.ini), the backup goes through fine.
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#2712
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?