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? …

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) 5월 26, 2025, 5:50오후 5

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?

글		댓글	조회수
Backup notifies failure on sidekiq restart, but backup succeeds Support	0	53	9월 23, 2025
Automatic backups are a hit or miss Support	11	1494	7월 8, 2018
Scheduled backup fails when Sidekiq is forcefully restarted Support	4	929	4월 3, 2018
Sidekiq is being paused, how can I discover why? Support	17	3423	9월 19, 2018
Sidekiq is consuming too much memory, restarting Self-hosting	38	9253	10월 13, 2020

백업이 여러 번 S3 업로드에 실패 - 결국 작동함

Related topics