- #Sabnzbd remove quotes folder zip file
- #Sabnzbd remove quotes folder full
- #Sabnzbd remove quotes folder code
- #Sabnzbd remove quotes folder download
Of course, others like yourself, would like to see the failed downloads removed from the queue for cleaner aesthetics. I know there are users that would like to see the failed downloads in the queue so they can see at a glance what failed and if any reasoning was behind it. I've generally taken the approach that I don't want to be removing items from other clients or manipulating them too much, in order to avoid excessive problems. Something like that I'm at a loss for usually as I don't run docker at all, so I'm a bit distant from some of the convo and troubleshooting specifics.Īs far as the Failed downloads, It would probably be a feature request - albeit not quite sure of a timeline when something like that could/would be implemented. I'm glad you were able to figure it out regardless. Is that something that Mylar should be doing that I'm not seeing? Or is this a feature request?
#Sabnzbd remove quotes folder full
Sonarr/Radarr detect these and generally wipe them from SAB so that SAB's log doesn't get full of failed downloads.
#Sabnzbd remove quotes folder download
When a comic fails to download in SAB, it seems to stick around even though Mylar sees it failed and tries again later. And a great program.ĮDIT: One other thing I wanted to mention that I noticed. Thanks so much for the speedy replies and trying to help out. Wanted to at least report on what I went through in case someone else runs into this too.
Maybe it's just better not to mix images from different repos. Maybe that's it? As far as I can tell, everything is the same as it was with the Hot.io image: permissions, settings, folders, etc. Perhaps the new image? The SAB image I was using was also from linuxserver. I tried a few more comics just to make sure and it's all copacetic now. And it worked! Moved the comic and deleted the parent folder. Once I got it all setup, I tried that comic again. I tried to exactly replicate what I had before. Either way, I had to go through and setup everything again. Probably due to rebuilding of the bindings? I'm not sure. Unfortunately, it wiped my config when it updated the container. So, I updated my Docker Compose file to use that image. I thought that I might try the image from linuxserver instead. I mentioned before that I was using the Docker image from Hot.io. The error that I see in the logs seems to be a catch-all at the end of all the code.
#Sabnzbd remove quotes folder code
Perhaps adding some additional logging for such a case? I saw in the code that this particular piece of code didn't have it's own try/catch even though most everything else in there did. I saw this in some of the code when I was troubleshooting. In a stack, they should see each other easily (and they do for the most part).
Perhaps if I was running them as independent containers, I could see having to specify they're on different machines (different networks, file systems, etc.). Once I did that, it wouldn't even find the file much less attempt to move it. I even tried to check the box for SAB on a different machine and that actually made it worse. The error in question is being thrown because the shutil.rmtree (which is a bundled python module) is failing for some reason, none of which seems to be logged unfortunately - so we need to figure out why the function is failing to remove (which could be for any reason really).
We might be able to decipher what's going on from the logs and the attached files.
#Sabnzbd remove quotes folder zip file
It will generate a zip file containing your db, environment, and cleaned logs & ini. You can generate a carepackage from the configuration page (button is in the upper right corner). The only other thing you can try to do is generate a carepackage which will hold all the relevant data and we can look more into it (there are a few docker experts that hang around). We usually say tell individuals running dockers to make sure that the ownership/perms are fully open to both users running Mylar and SABnzbd to the SABnzbd completed download folder and to point the Completed Download Location for SABnzbd (within the Mylar program) to the accessible folder location from within the given docker. So because Mylar is in docker and SABnzbd is in docker, it's considered to be on different machines - this is more from a general standpoint that one specific to your exact install. So within the directory that it's trying to delete, what are the permissions / ownership like therein? Is there just the cbz file or are there additional files in there as well (I'm talking about a individual download location, not the root of the SABnzbd completed download location btw).
0 kommentar(er)
