cloudreve/Cloudreve

运行期间无法上传文件报数据库锁死

Open

#2,917 opened on Sep 22, 2025

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Go (3,383 forks)batch import
backlogbughelp wanted

Repository metrics

Stars
 (21,463 stars)
PR merge metrics
 (Avg merge 2d 5h) (2 merged PRs in 30d)

Description

系统是乌班图24.04 LTS,前天刚搭好的,基本上一天就几个用户会下载文件,但是我今天上传文件的时候突然报错 并且在之后所有上传均报错,重启后却一切正常

[Info] 2025-09-22 09:15:02 [/home/vsts/work/1/s/pkg/crontab/crontab.go:64] Executing Cron task "entity_collect" with Cid "81d83359-6fe0-4d4a-914a-8b571b9c25e6" [Error] 2025-09-22 09:15:02 [/home/vsts/work/1/s/pkg/queue/queue.go:357] [Cid: 81d83359-6fe0-4d4a-914a-8b571b9c25e6 Cron: entity_collect] failed to transit Task status from to queued: failed to persist Task into DB: failed to create task: database is locked (5) (SQLITE_BUSY) [Info] 2025-09-22 09:15:02 [/home/vsts/work/1/s/pkg/queue/queue.go:360] [Cid: 81d83359-6fe0-4d4a-914a-8b571b9c25e6 Cron: entity_collect] Task 0 status changed from "" to "queued". [Error] 2025-09-22 09:15:02 [/home/vsts/work/1/s/pkg/filemanager/manager/recycle.go:55] [Cid: 81d83359-6fe0-4d4a-914a-8b571b9c25e6 Cron: entity_collect] Failed to queue entity recycle routine task: failed to transit Task status from to queued: failed to persist Task into DB: failed to create task: database is locked (5) (SQLITE_BUSY)

因为我日志记录的不够长所以只找到这一段报错,请问如何把日志打印到文件中以便查阅?我简单翻了文档,只有一个debug模式

Contributor guide

Research direction
Investigate the SQLite locking issue caused by concurrent write operations. Check if the upload handler and cron tasks are accessing the database simultaneously. Examine the database connection configuration (e.g., enable WAL mode, set busy timeout) and consider whether connection pooling is properly managed. Review logs to identify the exact pattern of the lock.
Tech stack
gosqlite
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70