root is blank #1753

Closed
opened 2025-11-02 04:12:15 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @hzmsrv on GitHub (May 3, 2018).

  • Gitea version (or commit ref):newest
  • Git version: newest
  • Operating system: win10
  • Database (use [x]):
    • [X ] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • [X ] No
    • Not relevant
  • Log gist:

Description

visit every projects are showing 500 error
...
2018/05/03 00:51:01 [I] Log Mode: File(Info)
2018/05/03 00:51:01 [I] XORM Log Mode: File(Info)
2018/05/03 00:51:01 [I] Cache Service Enabled
2018/05/03 00:51:01 [I] Session Service Enabled
2018/05/03 00:51:02 [I] Migration: add lfs lock table
2018/05/03 00:51:04 [I] Migration: add reactions
2018/05/03 00:51:05 [I] Migration: add pull request options
2018/05/03 00:51:05 [I] Migration: add writable deploy keys
2018/05/03 00:51:06 [I] Migration: remove is_owner, num_teams columns from org_user
2018/05/03 00:51:06 [I] Migration: add closed_unix column for issues
2018/05/03 00:51:09 [I] Git Version: 2.17.0
2018/05/03 00:51:10 [I] Git config user.name set to Gitea
2018/05/03 00:51:10 [I] Git config user.email set to gitea@fake.local
2018/05/03 00:51:11 [I] SQLite3 Supported
2018/05/03 00:51:11 [I] Run Mode: Production
2018/05/03 00:51:12 [I] Listen: http://0.0.0.0:3000
2018/05/03 00:51:12 [I] LFS server enabled
2018/05/03 00:57:36 [...ules/context/repo.go:348 func1()] [E] RepoAssignment Invalid repo C:\Windows\system32\config\systemprofile\gitea-repositories\XXXX\XXXXX.git: no such file or directory

Screenshots

Originally created by @hzmsrv on GitHub (May 3, 2018). <!-- 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):newest - Git version: newest - Operating system: win10 - Database (use `[x]`): - [X ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X ] No - [ ] Not relevant - Log gist: ## Description visit every projects are showing 500 error ... 2018/05/03 00:51:01 [I] Log Mode: File(Info) 2018/05/03 00:51:01 [I] XORM Log Mode: File(Info) 2018/05/03 00:51:01 [I] Cache Service Enabled 2018/05/03 00:51:01 [I] Session Service Enabled 2018/05/03 00:51:02 [I] Migration: add lfs lock table 2018/05/03 00:51:04 [I] Migration: add reactions 2018/05/03 00:51:05 [I] Migration: add pull request options 2018/05/03 00:51:05 [I] Migration: add writable deploy keys 2018/05/03 00:51:06 [I] Migration: remove is_owner, num_teams columns from org_user 2018/05/03 00:51:06 [I] Migration: add closed_unix column for issues 2018/05/03 00:51:09 [I] Git Version: 2.17.0 2018/05/03 00:51:10 [I] Git config user.name set to Gitea 2018/05/03 00:51:10 [I] Git config user.email set to gitea@fake.local 2018/05/03 00:51:11 [I] SQLite3 Supported 2018/05/03 00:51:11 [I] Run Mode: Production 2018/05/03 00:51:12 [I] Listen: http://0.0.0.0:3000 2018/05/03 00:51:12 [I] LFS server enabled 2018/05/03 00:57:36 [...ules/context/repo.go:348 func1()] [E] RepoAssignment Invalid repo C:\Windows\system32\config\systemprofile\gitea-repositories\XXXX\XXXXX.git: no such file or directory ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/questionissue/stale labels 2025-11-02 04:12:15 -06:00
Author
Owner

@lunny commented on GitHub (May 4, 2018):

is directory C:\Windows\system32\config\systemprofile\gitea-repositories\XXXX\XXXXX.git exist?

@lunny commented on GitHub (May 4, 2018): is directory C:\Windows\system32\config\systemprofile\gitea-repositories\XXXX\XXXXX.git exist?
Author
Owner

@hzmsrv commented on GitHub (May 4, 2018):

no! even they exist. the project pages still show 500

@hzmsrv commented on GitHub (May 4, 2018): no! even they exist. the project pages still show 500
Author
Owner

@kip-13 commented on GitHub (May 4, 2018):

I think that the problem is related to permissions to read C:\Windows\system32 a system's folder, try change the value of Repository Root Path to another folder like C:\Users\{user}

@kip-13 commented on GitHub (May 4, 2018): I think that the problem is related to permissions to read `C:\Windows\system32` a system's folder, try change the value of `Repository Root Path` to another folder like `C:\Users\{user}`
Author
Owner

@hzmsrv commented on GitHub (May 31, 2018):

it is the database problem. some bug destroy the database

@hzmsrv commented on GitHub (May 31, 2018): it is the database problem. some bug destroy the database
Author
Owner

@lunny commented on GitHub (Jun 1, 2018):

@hzmnet any detail?

@lunny commented on GitHub (Jun 1, 2018): @hzmnet any detail?
Author
Owner

@daviian commented on GitHub (Jun 2, 2018):

@hzmnet I don't believe this is a database problem.
Reason: path of repository is determined by three factors. The root path from app.ini, the repo owner name and the actual repository name.

@daviian commented on GitHub (Jun 2, 2018): @hzmnet I don't believe this is a database problem. Reason: path of repository is determined by three factors. The root path from app.ini, the repo owner name and the actual repository name.
Author
Owner

@hzmsrv commented on GitHub (Jul 8, 2018):

it is the database 's problem. the repository in the database was broken or mixed. so when you restore those file from the database are not working.

@hzmsrv commented on GitHub (Jul 8, 2018): it is the database 's problem. the repository in the database was broken or mixed. so when you restore those file from the database are not working.
Author
Owner

@stale[bot] commented on GitHub (Jan 19, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 19, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1753