February 7, 20242 yr Hi all! I left quite a few downloads running overnight and today woke up to sabnzbd's notifications stating "SQL command failed". I tried to open the logs within it and it just showed an error message, something .py related, didn't take a screenshot unfortunately. Both Radarr and Sonarr were also down. So I started to panic. I stopped all docker containers, checked the array and noticed the cache was almost full, probably 1.8TB used of 2TB. So I went in and manually deleted every single incomplete and complete usenet files. After a reboot, the docker containers all spun up, Radarr and Sonarr showed the root path was missing but it showed my previous root file (I changed yesterday all shares to the recommended by Trash-Guides for atomic/hardlinks as the imports were taking AGES). So, if my data share is set to cache -> array I assumed as it neared being full it'd be moved to the array automatically, or did it do that but the writing to the cache was quicker than the mover service? What I also assumed was that if the cache was full then the new files would be written to the secondary location (array) as I'm almost certain I read that? In fact, sabnzbd reports the array disk free space instead of the cache for some reason?! Even so, even if it was almost full, why would the database get screwed up like that? Any ideas? Is this expected behavior? Also, after changing the root path for both Sonarr and Radarr everything is now working properly. Is there a chance something was screwed up with this? I'm hoping not as setting everything up again would be a pain lool! Many thanks!
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.