[BUG] 数据库写入

[RekinChiang]

Please confirm the following

• I have read and agree to AGPL-3.0 Section 15 .
  The program is provided "as is" without any warranties; you bear all risks of using it.

• I have read and agree to AGPL-3.0 Section 16 .
  The copyright holders and distributors are not liable for any damages resulting from the use or inability to use the program.

• I confirm my description is clear, polite, helps developers quickly locate the issue, and complies with community rules.

• I have read the OpenList documentation.

• I confirm there are no duplicate issues or discussions.

• I confirm this is an OpenList issue, not caused by other reasons (such as network, dependencies, or operation).

• I believe this issue must be handled by OpenList and not by a third party.

• I confirm this issue is not fixed in the latest version.

OpenList Version (required)

v4.1.0

Storage Driver Used (required)

SQLite

Bug Description (required)

Docker版的数据库写入似乎有问题, data.db-wal一直在增长, 但是data.db一直没有写入任何数据, 停止/重启容器, 也尝试过重新部署, 一直都不写入. 请尽快修正此Bug.

Configuration File Content (required)

默认配置

Logs (optional)

No response

Reproduction Link (optional)

No response

[github-actions]

感谢您联系OpenList。我们会尽快回复您。
Thanks for contacting OpenList. We will reply to you as soon as possible.

[jyxjjj]

请在备份数据后，尝试手动执行
PRAGMA wal_checkpoint(TRUNCATE);
PRAGMA wal_checkpoint(RESTART);
后重启容器，看是否依然复现此问题

[jyxjjj]

并检查文件权限

[RekinChiang]

@jyxjjj 权限没问题. 操作如下:

docker exec -it OpenList sh

sqlite3 /opt/openlist/data/data.db "PRAGMA wal_checkpoint(FULL);"

sqlite3 /opt/openlist/data/data.db "PRAGMA wal_checkpoint(RESTART);"

提示: sh: sqlite3: not found

安装:

apt update

apt install -y sqlite3

则顺利执行, 但是重启后, 任何操作和变动, 只会写入data.db-wal, 不会自动合并至data.db.

在X86和ARM下均是如此.

[jyxjjj]

重启和创建容器用的命令提供一下。
这边测试仅在强杀进程的情况下出现此问题。
是否因为驱动过多或其他原因导致在停止时超过Docker停止超时限制被强杀？

[RekinChiang]

@jyxjjj "docker restart OpenList", "docker run -d --restart=unless-stopped -v /etc/openlist:/opt/openlist/data -p 5244:5244 -e PUID=0 -e PGID=0 -e UMASK=022 --name="OpenList" openlistteam/openlist:latest"

没有被杀, 除了更新最新版外都没做过其它操作.

[Alien-Et]

可能你没安装sqlite3

[jyxjjj]

@xrgzs @j2rong4cn 我觉得不然就启动的时候直接强制刷新一下？

---

PS: 用MySQL/MariaDb就不会有这个问题了

[devnakx]

+1，我也遇到这样的情况，我记得以前 alist 用docker stop退出后会在日志里打印closed server之类的日志，然而我刚刚试了下把 openlist 用docker stop后并没有出现相关日志，感觉 openlist 进程没有收到docker stop发送的 SIGTERM 信号而被是被直接强杀了，导致数据库没有正常关闭

[devnakx]

是不是entrypoint.sh里的更改的原因？我看 alist 用的是su-exec，而 openlist 改用了runsvdir

[devnakx]

d0c22a1 应该是这个 commit 导致的，而且还更改了默认 UID 和 GID，我就说怎么前两天更新最新 bata 镜像后无法访问挂载的宿主机路径了，临时把宿主机上 openlist 的路径给 777 权限后才能访问

[RekinChiang]

@devnakx 我7月从Alist切OpenList后, OpenList就再也没正常写入过数据, 应该迁移的时候进行了某些改动导致的.

[devnakx]

无论如何，看起来都像是 openlist 没有收到 docker 发送的终止信号，导致无法优雅地退出，数据库没有正常关闭退出，被直接强杀了

[devnakx]

应该可以下定论了，就是没有收到 SIGTERM 信号，我进入容器手动kill openlist的主进程（kill 命令默认发送 SIGTERM），日志里是有打印退出日志的