Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
2 of 7 tasks
PinguTS opened this issue Jan 25, 2019 · 1 comment
Closed
2 of 7 tasks

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

PinguTS opened this issue Jan 25, 2019 · 1 comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug

Comments

@PinguTS
Copy link

PinguTS commented 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.

zeripath added a commit to zeripath/gitea that referenced this issue Feb 16, 2019
Fixes go-gitea#5854

Signed-off-by: Andrew Thornton <art27@cantab.net>
@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Mar 26, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Mar 27, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

No branches or pull requests

3 participants