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

Better logging of no space left on disk #3564

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

Originally created by @mjarkk on GitHub (Jul 10, 2019).

  • Gitea version (or commit ref): 1.7, 1.8, 1.8.3, 1.9 (Docker version)
  • Git version: (Unknown due to usage of docker container)
  • Operating system: CoreOS
  • 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: (This is a log from v1.8)
2019/07/10 09:14:46 [I] Gitea vbafa9ff built with go1.11.9 : bindata, sqlite, sqlite_unlock_notify
2019/07/10 09:14:51 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:51 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:51 [T] Custom path: /data/gitea
2019/07/10 09:14:51 [T] Log path: /data/gitea/log
2019/07/10 09:14:52 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:52 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:52 [T] Custom path: /data/gitea
2019/07/10 09:14:52 [T] Log path: /data/gitea/log
2019/07/10 09:14:53 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:53 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:53 [T] Custom path: /data/gitea
2019/07/10 09:14:53 [T] Log path: /data/gitea/log
2019/07/10 09:14:54 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:54 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:54 [T] Custom path: /data/gitea
2019/07/10 09:14:54 [T] Log path: /data/gitea/log
2019/07/10 09:14:55 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:55 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:55 [T] Custom path: /data/gitea
2019/07/10 09:14:55 [T] Log path: /data/gitea/log
2019/07/10 09:14:56 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:56 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:56 [T] Custom path: /data/gitea
2019/07/10 09:14:56 [T] Log path: /data/gitea/log
2019/07/10 09:14:57 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:57 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:57 [T] Custom path: /data/gitea
2019/07/10 09:14:57 [T] Log path: /data/gitea/log
2019/07/10 09:14:58 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:58 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:58 [T] Custom path: /data/gitea
2019/07/10 09:14:58 [T] Log path: /data/gitea/log
2019/07/10 09:14:59 [T] AppPath: /app/gitea/gitea
2019/07/10 09:14:59 [T] AppWorkPath: /app/gitea
2019/07/10 09:14:59 [T] Custom path: /data/gitea
2019/07/10 09:14:59 [T] Log path: /data/gitea/log
2019/07/10 09:15:00 [T] AppPath: /app/gitea/gitea
2019/07/10 09:15:00 [T] AppWorkPath: /app/gitea
2019/07/10 09:15:00 [T] Custom path: /data/gitea
2019/07/10 09:15:00 [T] Log path: /data/gitea/log
2019/07/10 09:15:01 [T] AppPath: /app/gitea/gitea
2019/07/10 09:15:01 [T] AppWorkPath: /app/gitea
2019/07/10 09:15:01 [T] Custom path: /data/gitea
2019/07/10 09:15:01 [T] Log path: /data/gitea/log
...
...

Description

Today i made a push to the server and noticed after that that the server stopped working.
After a way to long time debugging i found the problem being that the disk was 100% full.

Somewhere in a gitea issue i found a notice about not having not enough space and that's how i finally found why gitea crashed.

It would be great if gitea shows me that i've not enough space left on the disk because the current logging (see logging) doesn't help a lot.

If it's not possible to show that i don't have enough disk space it would be at least nice if there was some more verbose logging in the docker logs.

Screenshots

Gitea did not start So i only have a 503 proxy error what is not worth making a screenshot of.

Originally created by @mjarkk on GitHub (Jul 10, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) 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.7, 1.8, 1.8.3, 1.9 (Docker version) - Git version: (Unknown due to usage of docker container) - Operating system: CoreOS - 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: (This is a log from v1.8) ``` 2019/07/10 09:14:46 [I] Gitea vbafa9ff built with go1.11.9 : bindata, sqlite, sqlite_unlock_notify 2019/07/10 09:14:51 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:51 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:51 [T] Custom path: /data/gitea 2019/07/10 09:14:51 [T] Log path: /data/gitea/log 2019/07/10 09:14:52 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:52 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:52 [T] Custom path: /data/gitea 2019/07/10 09:14:52 [T] Log path: /data/gitea/log 2019/07/10 09:14:53 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:53 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:53 [T] Custom path: /data/gitea 2019/07/10 09:14:53 [T] Log path: /data/gitea/log 2019/07/10 09:14:54 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:54 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:54 [T] Custom path: /data/gitea 2019/07/10 09:14:54 [T] Log path: /data/gitea/log 2019/07/10 09:14:55 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:55 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:55 [T] Custom path: /data/gitea 2019/07/10 09:14:55 [T] Log path: /data/gitea/log 2019/07/10 09:14:56 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:56 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:56 [T] Custom path: /data/gitea 2019/07/10 09:14:56 [T] Log path: /data/gitea/log 2019/07/10 09:14:57 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:57 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:57 [T] Custom path: /data/gitea 2019/07/10 09:14:57 [T] Log path: /data/gitea/log 2019/07/10 09:14:58 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:58 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:58 [T] Custom path: /data/gitea 2019/07/10 09:14:58 [T] Log path: /data/gitea/log 2019/07/10 09:14:59 [T] AppPath: /app/gitea/gitea 2019/07/10 09:14:59 [T] AppWorkPath: /app/gitea 2019/07/10 09:14:59 [T] Custom path: /data/gitea 2019/07/10 09:14:59 [T] Log path: /data/gitea/log 2019/07/10 09:15:00 [T] AppPath: /app/gitea/gitea 2019/07/10 09:15:00 [T] AppWorkPath: /app/gitea 2019/07/10 09:15:00 [T] Custom path: /data/gitea 2019/07/10 09:15:00 [T] Log path: /data/gitea/log 2019/07/10 09:15:01 [T] AppPath: /app/gitea/gitea 2019/07/10 09:15:01 [T] AppWorkPath: /app/gitea 2019/07/10 09:15:01 [T] Custom path: /data/gitea 2019/07/10 09:15:01 [T] Log path: /data/gitea/log ... ... ``` ## Description Today i made a push to the server and noticed after that that the server stopped working. After a way to long time debugging i found the problem being that the disk was 100% full. Somewhere in a gitea issue i found a notice about not having not enough space and that's how i finally found why gitea crashed. It would be great if gitea shows me that i've not enough space left on the disk because the current logging (see logging) doesn't help a lot. If it's not possible to show that i don't have enough disk space it would be at least nice if there was some more verbose logging in the docker logs. ## Screenshots Gitea did not start So i only have a 503 proxy error what is not worth making a screenshot of.
GiteaMirror added the type/proposal label 2025-11-02 05:17:27 -06:00
GiteaMirror commented 2025-11-02 05:17:28 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Apr 28, 2023):

The logger system has changed a lot, maybe it could print better messages now?

Feel free to reopen if there is still something to be improved.

@wxiaoguang commented on GitHub (Apr 28, 2023): The logger system has changed a lot, maybe it could print better messages now? Feel free to reopen if there is still something to be improved.
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/proposal
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#3564
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?