December 28, 20232 yr Hey guys, I have the weirdest thing happening with my RR-container (sonarr, radarr, bazarr & prowlarr). They restart every 5 minutes. And even when I stop the containers, they start up at the same time again when they usually restarts. E.g 19:45, 19:50, 19:55 and so on... Can't find anything specific in the logs that helps me, but maybe you guys can? These are the only containers behaving like this. I have probably 20+ more containers just running fine. I've restarted docker 2-3 times and also rebooted the server twice today. Same isssue still. Please let me know what else I need to collect, and also maybe how to collect it. I've started a syslog-server. But not sure what to do else with it for now. mini-diagnostics-20231228-1956.zip Edited December 29, 20232 yr by mini_raid
December 28, 20232 yr Community Expert Are you sure you don't have something scripted to restart Docker service? Mover tuning, Appdata backup, something like that?
December 28, 20232 yr Author 13 minutes ago, trurl said: Are you sure you don't have something scripted to restart Docker service? Mover tuning, Appdata backup, something like that? I can't say 100% sure, but I can't find any user script, scheduler, mover or appdata backup scheduled for every 5 minutes for these 4 containers. But maybe somewhere where I dont know to look. I would hope that a log somewhere would tell if this was the case though?
December 29, 20232 yr Author 11 hours ago, trurl said: Does it happen if you boot in SAFE mode? Yes, just tried this and it behaves the same. Is it something else I can try or look at during safe mode? I've attached a new diagnostics. mini-diagnostics-20231229-1152.zip Edited December 29, 20232 yr by mini_raid
December 29, 20232 yr Author Solution So, I think I solved it... Stopped all containers, and started one at a time until I found that Rebuild-DNDC was looking like the bad guy. Obviously Rebuild-DNDC is the last one in my startup order too... so it took a while due to the 5 minutes wait time for each container 🤡 Rebuild-DNDC had cached all my *RR-containers for whatever reason, and tried a rebuild every 5 minutes triggered from the default configured CRON-job. I was not using any VPN-network for the *RR-containers. Probably something I've tested for a long time ago. Solution: Stop Rebuild-DNDC Delete all .tmp-files in Rebuild-DNDC /config-folder (in my case it was in "/mnt/user/appdata/rebuild-dndc" Start up Rebuild-DNDC Now it works like it should again. What still makes me annoyed is that I don't understand why there is no logs in the containers that "Rebuild-DNDC" tries to rebuild, or in the docker.log? Should be traceable some way that a container schedules a stop/start for other containers.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.