Hoping for some clarification… In today’s update, rTorrent support was provided. This is awesome! My question is exactly how it’s working.
NOTE: My question is with a local Sonarr config using a remote Seedbox (rTorrent is NOT on the same machine or on the same network as Sonarr)
I was under the impression that Sonarr would:
Send the .torrent to the Seedbox and initiate the download <-- check, this works.
Monitor the download <-- check, this works.
Download the completed file into the Sonarr defined directory and “process” it <— problem
Is this the way it is supposed to work? If so, I’m getting an error from Sonar: “No files found are eligible for import in /home/disk11/pockit/torrents/downloads/”
I’ve gotten this to ‘work’ using Remote Path Management by mapping my Seedbox drive via SSHFS and adding that as an RPM. However, Sonarr doesn’t monitor the download from SB to Sonarr in the Queue (is this normal behavior?)
Your insight would help a very tired guy so, thanks!
Ok so, just to clarify, the rTorrent Download Client will NOT download a completed torrent to the local Sonarr installation without remote path mapping setup in the case of a remote seedbox/rtorrent installation?
I’m unclear here as well. In the SB the download is set with a label (in this case the default: tv-sonarr) which was defined in the Download Client configuration for my rTorrent client. Is that what you mean or is there a different label/category and/or am I misunderstanding?
The way I’m interpreting your response is that if that label/category on the SB matches the DL Client configuration, then Sonarr will monitor the download from .torrent to completed file and also completed file on SB to processed file on Sonarr?
3rd Question now: How does the Hard Link work in Media Management section. If I turn that on, what is the impact? Currently with the RPM configuration, it’s downloading the completed file but, deleting it from the RPM share once it’s renamed and put in the appropriate Sonarr folder. I’m interpreting the Hard Link as a way for it not to delete the file from the SB but, instead create a link to it. Hard = actually a full-sized copy on my Sonarr machine? If so, that’s fine BUT, what happens when I decide I’m done seeding that file on the SB and delete it from the SB? Does that hard link get impacted at all or is it just a copy or am I missing something here too?
Thanks again for your support here; I’m loving Sonarr and have an ‘issue’ with making everything perfect!
Correct. Also making the assumption that Sonarr is able to determine the series/episode for those torrents, if they are poorly named then Sonarr won’t do anything with them.
In your configuration, zero impact, hardlinking requires the source and destination of the files to be on the same volume. Its a method to have two handles to the same file, which appear as separate files, but take up the disk space once.
At this point I seem to have this working pretty smoothly.
A couple of things (possibly in my initial configuration). There were several times where Sonarr would delete the completed file from the RPM location. However, the last 10 downloads / transactions have not done that so, I’m guessing that’s was my fault. FYI anyway.
Do you have a recommendation for the RPM configuration in terms of protocol / utilities etc. Currently, I’m using SSHFS to mount the Seedbox folder and associate it with an RPM. This seems to work but, it seems to transfer the files one at a time. I know BTSync is an option (any thoughts on if that would be more efficient / speedy and/or drawbacks?), do you have any other thoughts to a difference configuration that would make this awesome?!
Sonarr shouldn’t remove files from the RPM, rTorrent support in Sonarr doesn’t include removing finished torrents because ratio groups aren’t supported and we don’t have a way to determine if a torrent has finished seeding. If the files were removed its possible its due to the torrent being stopped (not seeding, thus not read-only).
SSHFS is really the only option, BTSync would likely result in incomplete files being imported. Importing 1 at a time is normal and shouldn’t make too much of a difference since the internet connection is likely the bottleneck in downloading the files.
