So I was actually able to repeat the failure. Next I tried downloading it again using SABnzbd, and it worked first time. Maybe the issue lies with NZBGet? I just thought I had something, same episode downloaded from different indexers, one failed and one successfully imported. Tried again on another episode and both failed to import. I'm stumped. Now is there some connection there?
I'm not by any means techy enough to work out what's wrong but that info might be useful to someone. Its definitely the random letters and numbers that are causing the issue. Where or how, I don't know. Anything that is properly named, works just fine. Anything obscure, doesn't work. I can manually import it with no problems through Sonarr, so I can't figure out how its a permissions issue.
When a file has a "normal" name everything works fine, so doesn't seem to be a permission issue. What are this "random number" file properties? Please report from File Station and from command line with stat. We will probably have to increase application verbosity and maybe collect strace or libtrace to get understanding of what happens behind the scene.
I can only guess that's something to do with the back ends the sites use. This is the properties of my latest failure. I also had a movie in Radarr with an obfuscated filename that didn't work in the exact same way.
Also have the stat of a file here, my nzb are coming from NZBFinder if that is relevant. Giving access right via sc-download does nothing for existing folders and files. You have to check what the owner of those folders and files are and add that owner to the group sc-download. Thx very much and sorry for the multiple post question I was hoping for a better chance of getting a solution!
I have found that if I go into FileStation, select the folder, right click, select properties, go to the permission tab, select SC-Download, click Apply to this folder and sub folders, this ends up working, and within a few seconds, Sonarr sees the file is complete and moves it. Does that help anyone figure out whats going on? Hi BenjV ,. Does adding the owner of the folders to sc-download fix this problem for future imports or only for current ones? Depend on how the files are created.
The file owner is the application that creates the files on the NAS. So if you put that owner in the group all new files will be fine. But normally files are created with the same privileges as the folder they are created in inherite privs unless the application explicite change those privs. So if the top folder and all subfolders are given access rights to the sc-download group normally all will be ok for new folders and files. I'm confused because some times downloads, transfert, all process go fine and sometimes everything goes wrong and sonarr can't process any download.
No nzbget does not change the inherited permissions unless you changed the umask which you should no do. You have to give the sc-download and sc-media groups permissions on the top level folder and set for existing folders and files this with FileStation recusively.
You cannot work with the users themself anymore. I don't undertand why some files are good and some are not. I had a kind of similar issue in the past and it's important to remember that it's not just an import automatic or manual. Depending of your configuration, it might be a copy, a move, an hardlink or even a move to trash if the file is an upgrade of another one. In my case, the account didn't had permissions on the recycle folder Right, i solved my problem.
I did these things: comment. I added the group sc-download to my movie and series folder and had to do so manually via Filestation. But sc-download didn't have RW rights to all those folders. Once i gave sc-download RW right to all sub folders sonarr started crunching releases. LtMarx Does this also work for new imports?
Does anyone can give us all the members in each group. Sorry to be a pain but could you give all relevant info on rights and owners for each folder maybe? Okay, I think I figured out the issue. RAR files maintain the permissions of whomever packaged the files, and uploaded to the Newsgroup.
These original permissions are what is causing issues with importing. After making these changes, all downloads, including the random character files began to correctly inherit the permissions of my "Completed" Directory, and Sonarr imported with no issues. Hope this helps! Hutsoncap It's a little early to say that's definitely fixed it for me but so far so good. Not had a failure since adding that switch. I did the following:.
The problem is that you did not convert the shared folder to support ACL's. Read this and especially the last part. Here's my config of docker. EnsureEpisodeFolder NzbDrone. EpisodeFile episodeFile, NzbDrone. Series series, Int32 seasonNumber, System. LocalEpisode localEpisode, System. MoveEpisodeFile NzbDrone. UpgradeEpisodeFile NzbDrone. Import System. It appears that within the sonarr app, you are directly referencing a folder within the array and not doing the path correctly to boot.
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. Restore formatting. Any other things to check? What do the debug logs show for imports? What does Activity: Queue show? And what reason do they say for not being imported? Again, hover over the icon on the left of each item. I had problem of files not being put away and found it was that i had used upper case letters in some of the paths and lower in other.
0コメント