Backups to S3 have been working for several years. Starting a month ago, I often get several notifications that the backup failed. Then it retries, and about an hour later fails again, so I get a second notification, and often up to six notifications in one day before it finally succeeds. The log f…

[圖片] markschmucker: [2025-05-20 07:34:28] EXCEPTION: Sidekiq::Shutdown Could you be running out of memory? That exception makes me think that Sidekiq (which runs the automatic backups) is either killed by the OS or crashes for some other reason. Did you try rebuilding the Docker container (.…

[圖片] gerhard: Could you be running out of memory? I don’t think so. The server is overkill for our community with 16GB RAM. top shows 11GB free memory, and that hardly changes if I manually trigger a backup. I’ll check /var/log/syslog tomorrow for anything about memory, kill, or OOM. (Can’t …

I do have this in /logs. This particular warning did not coincide with the backup- I’ll check for that in the morning (backups are done at night). But I didn’t realize Discourse its own memory check- I thought you were referring to the OOM killer. Can I increase the allowed memory size for Sidekiq? …

Indeed, I was referring to the OOM killer. I completely forgot that there’s a memory limit for Sidekiq. Did increasing memory for Sidekiq help?

I believe that fixed it- want to see a couple more clean nightly backups to be sure. Will post here.

Yes, it’s fixed. You can close this topic.

备份多次未能上传到S3，最终成功

支持

gerhard (Gerhard Schlager) 2025年五月26日 17:50 5

事实上，我指的是OOM杀手。我完全忘记了Sidekiq是有内存限制的。增加Sidekiq的内存有帮助吗？

話題		回覆	觀看
Backup notifies failure on sidekiq restart, but backup succeeds Support	0	57	2025年九月23日
Automatic backups are a hit or miss Support	11	1524	2018年七月8日
Scheduled backup fails when Sidekiq is forcefully restarted Support	4	935	2018年四月3日
Sidekiq is being paused, how can I discover why? Support	17	3448	2018年九月19日
Sidekiq is consuming too much memory, restarting Self-hosting	38	9337	2020年十月13日

备份多次未能上传到S3，最终成功

相關主題