github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Silent fail/crash when no access to log files #2816

New Issue
Closed
opened 2025-11-02 04:49:27 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:49:27 -06:00
Owner
Copy Link

Originally created by @PinguTS on GitHub (Jan 25, 2019).

Gitea silently crashes on startup, when the user has no access (read/write) to the log files.

  • Gitea version (or commit ref): 1.6.0+rc1-221-g9863591dc
  • Git version: 2.18.0
  • Operating system: Debain Linux i386
  • 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:

Description

The log files are not placed within the gitea directory structure but at /var/log/gitea/, like all other log files. The directory and the files within had only root access. Then the gitea web silently crashes. There is no information or indication about the problem to find in the console.

Originally created by @PinguTS on GitHub (Jan 25, 2019). Gitea silently crashes on startup, when the user has no access (read/write) to the log files. - Gitea version (or commit ref): 1.6.0+rc1-221-g9863591dc - Git version: 2.18.0 - Operating system: Debain Linux i386 - Database (use `[x]`): - [ ] 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 The log files are not placed within the gitea directory structure but at `/var/log/gitea/`, like all other log files. The directory and the files within had only `root` access. Then the `gitea web` silently crashes. There is no information or indication about the problem to find in the console.
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 04:49:28 -06:00
GiteaMirror commented 2025-11-02 04:49:28 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 26, 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 (Mar 26, 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.
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/confirmed 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#2816
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?