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

Exits without error when incorrect user owns directories #3165

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

Originally created by @coolaj86 on GitHub (Apr 9, 2019).

  • Gitea version (or commit ref): v1.7.5
  • Git version: v2.17.1
  • Operating system: Ubuntu 18.04.2 LTS
  • 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:
/opt/gitea/gitea --config /opt/gitea/custom/conf/app.ini
2019/04/09 21:42:48 [T] AppPath: /opt/gitea/gitea
2019/04/09 21:42:48 [T] AppWorkPath: /opt/gitea
2019/04/09 21:42:48 [T] Custom path: /opt/gitea/custom
2019/04/09 21:42:48 [T] Log path: /opt/gitea/log

Description

I copied my gitea v1.5.x installation over to a new server and ended up with folders having incorrect permissions.

I got the output above and then exit(1).

I figured it was something to do with users or permissions due to the move, but it seems like it should have panic()d or output some sort of error message.

Solution

sudo chown -R git:git /opt/gitea /srv/gitea /var/log/gitea

Screenshots

N/A

Originally created by @coolaj86 on GitHub (Apr 9, 2019). - Gitea version (or commit ref): v1.7.5 - Git version: v2.17.1 - Operating system: Ubuntu 18.04.2 LTS - 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: ``` /opt/gitea/gitea --config /opt/gitea/custom/conf/app.ini 2019/04/09 21:42:48 [T] AppPath: /opt/gitea/gitea 2019/04/09 21:42:48 [T] AppWorkPath: /opt/gitea 2019/04/09 21:42:48 [T] Custom path: /opt/gitea/custom 2019/04/09 21:42:48 [T] Log path: /opt/gitea/log ``` ## Description I copied my gitea v1.5.x installation over to a new server and ended up with folders having incorrect permissions. I got the output above and then exit(1). I figured it was something to do with users or permissions due to the move, but it seems like it should have panic()d or output some sort of error message. ## Solution ``` sudo chown -R git:git /opt/gitea /srv/gitea /var/log/gitea ``` ## Screenshots N/A
GiteaMirror commented 2025-11-02 05:02:31 -06:00
Author
Owner
Copy Link

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

There's a problem with logging pre-1.9 whereby the message that is sent with log.fatal doesn't get logged before the the program exits. I suspect therefore it does get logged but it disappears.

This is fixed in master (1.9)

@zeripath commented on GitHub (Apr 9, 2019): There's a problem with logging pre-1.9 whereby the message that is sent with log.fatal doesn't get logged before the the program exits. I suspect therefore it does get logged but it disappears. This is fixed in master (1.9)
GiteaMirror commented 2025-11-02 05:02:31 -06:00
Author
Owner
Copy Link

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

Could you try on master and see if you have the same result?

@zeripath commented on GitHub (Apr 9, 2019): Could you try on master and see if you have the same result?
GiteaMirror commented 2025-11-02 05:02:31 -06:00
Author
Owner
Copy Link

@coolaj86 commented on GitHub (Apr 10, 2019):

It appears to still be broken. I just tried upgrading from 1.7.5 to 1.9-dev and it keeps crashing without any error message (and that's will the permissions set correctly).

@coolaj86 commented on GitHub (Apr 10, 2019): It appears to still be broken. I just tried upgrading from 1.7.5 to 1.9-dev and it keeps crashing without any error message (and that's will the permissions set correctly).
GiteaMirror commented 2025-11-02 05:02:31 -06:00
Author
Owner
Copy Link

@coolaj86 commented on GitHub (Apr 10, 2019):

I was told that the logging behavior was changed in v1.7 so it was actually the issue of my config file being interpreted differently.

@coolaj86 commented on GitHub (Apr 10, 2019): I was told that the logging behavior was changed in v1.7 so it was actually the issue of my config file being interpreted differently.
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
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#3165
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?