![]() 03:08:57,502::INFO:: Creating directories: /downloads/sabnzbd/incomplete/265 03:08:51,975::INFO:: No bonjour/zeroconf support installed 03:08:51,806::INFO:: Sending notification: SABnzbd - SABnzbd 3.3.0 started (type=startup, job_cat=None) 03:08:51,805::INFO:: Completed Download Folder /downloads/sabnzbd/complete is not on FAT So looking at the Sabnzbd logs I saw this and figured what happened is that a folder called /tv was created after downloading the test download and because there was already a folder called /tv which contained all the different tv series folders it just wiped it.Maybe? Here's a few lines from the log file Now I think the issue started when I set the Enable TV Sorting option in Sabnzbd after a test download (spitting image series 19 episode 2) was used to check my download settings, the file was downloaded but was not moved into the Spitting Image folder on my Synology Nas drive (something that has been happening for a while with some downloads but not all) Temporary Download Folder - /downloads/sabnzbd/incompleteĬompleted Download Folder - /downloads/sabnzbd/complete So looking at Sabnzbd the folders used are: Here are the folder locations which Sonarr and Radarr are using: So like a good little boy I set off to investigate and 'fix' the issues. You should not download to a root folder." "Download client Sabnzbd places downloads in the root folder /tv. "Download client sabnzbd places downloads in the root folder /movies. ![]() Synology Nas Drive running Sonarr, Radarr and Sabnzbd within Docker Containers.I just upgraded all three programs to the latest versions which resulted in a completely new redesign of Sonaar and Radarr and with that I started seeing warning messages such as: I can see how this would relate to the async import process for TransferProviders, since at any point during the import you can have a 'blocking issue', and with the proper infrastructure have it reported to the user.I hope someone can shed some light on this for me. It also means we could potentially deal with recurring issues (and thus repeated error log entries). This would allow the Condition to tackle reporting the issues, and specify how critical it is. So a if (_rootFolderPresentCondition.IsSatified(series.RootFolder. The Condition would obviously just invoke diskProvider, but then also be able to handle the error/issue reporting. RootFolderCheck would simply invoke 'RootFolderPresentCondition' for all series, import would do the same but then for one series. ![]() Move the actual diskprovider check away from the import logic into a separate 'Check'/'Verify'/'Condition'/something class that does the heavy lifting. ![]() Or better yet, have the error detection during import / series scan that checks whether the root folder exists report an 'Issue' so we can track it. That's easy to do with these attributes.īut we could implement a causing it only to recheck if the healthcheck failed previously. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |