Completed Download Handling - QBittorrent - wrong path

Sonarr version (exact version):
2.0.0.5344

OS:
Windows

Some of my completed downloads are not processing. I have tracked it down and believe it to be a bug in Sonarr. Consider this torrent that is not being processed:

If I look at that torrent from the qBittorent API, I get this JSON returned:

[
{
"added_on": 1612199421,
"amount_left": 0,
"auto_tmm": false,
"availability": -1,
"category": "tv-sonarr",
"completed": 3148841883,
"completion_on": 1612199686,
"content_path": "D:\\qBittorrentComplete\\Legacies.S03E02.1080p.AMZN.WEBRip.DDP5.1.x264-KiNGS[rarbg]",
"dl_limit": -1,
"dlspeed": 306300,
"downloaded": 3155712592,
"downloaded_session": 3155712592,
"eta": 3587,
"f_l_piece_prio": false,
"force_start": false,
"hash": "9b387b68f94e1a5df4af59756b1dabd652f66b4a",
"last_activity": 1612199686,
"magnet_uri": "magnet:?xt=urn:btih:9b387b68f94e1a5df4af59756b1dabd652f66b4a&dn=Legacies.S03E02.1080p.AMZN.WEBRip.DDP5.1.x264-KiNGS%5brarbg%5d&tr=http%3a%2f%2ftracker.trackerfix.com%3a80%2fannounce&tr=udp%3a%2f%2f9.rarbg.me%3a2710&tr=udp%3a%2f%2f9.rarbg.to%3a2710&tr=udp%3a%2f%2fopen.demonii.com%3a1337%2fannounce",
"max_ratio": -1,
"max_seeding_time": 60,
"name": "Legacies.S03E02.1080p.AMZN.WEBRip.DDP5.1.x264-KiNGS[rartv]",
"num_complete": 67,
"num_incomplete": 12,
"num_leechs": 1,
"num_seeds": 0,
"priority": 0,
"progress": 1,
"ratio": 0.00002076741721224529,
"ratio_limit": -2,
"save_path": "D:\\qBittorrentComplete",
"seeding_time_limit": -2,
"seen_complete": 1612199686,
"seq_dl": false,
"size": 3148841883,
"state": "stalledUP",
"super_seeding": false,
"tags": "",
"time_active": 278,
"total_size": 3148841883,
"tracker": "udp://9.rarbg.me:2710",
"trackers_count": 4,
"up_limit": -1,
"uploaded": 65536,
"uploaded_session": 65536,
"upspeed": 0
}
]

Notice the name and the content path do not match (rartv vs rarbg at the end). The torrent download does exist at the content path (D:\qBittorrentComplete\Legacies.S03E02.1080p.AMZN.WEBRip.DDP5.1.x264-KiNGS[rarbg]), but in my Sonarr logs, is show this:

Notice, the logs have the wrong folder path. From looking at the logs, I believe Sonarr is putting together “save_path” and “name” which gives the wrong folder. Using the “content_path” would solve this issue.

I have never looked at the Sonarr source code, so I am guessing here, but do believe that to be the issue.

Thoughts?

https://forums.sonarr.tv/search?q=Qbittorrent%20path
Downgrade qbit, upgrade to sonarr v3, pick one.

How stable is sonarr v3 since I see it is in beta?

I was running qbit 4.2.5 (and having the issue) and tried upgrading it to 4.3.3 because they had an issue in their forum that said this the wrong path issue was solved. If I downgrade qbit, how far down?

Thanks for the reply

To be honest I’d just upgrade sonarr to v3. You’ll get so many new things and if shit breaks (looking at you, qbit), it get fixed on sonarr’s end.

Well, I updated to v3, but the service would not start. I searched the forum for “SingleInstancePolicy v3”, but came up empty. I verified the old “NZBDrone” windows service is gone and not running.

I found the exe and ran it by hand. Here is the output.

Any ideas?

I also rebooted to make sure everything was cleaned up

Which startup option did you choose when you installed v3?
Is the Sonarr service running?

I chose run as a service. The service would not start - it died almost immediately. I was able to get it to work. So, the issue was that I store my downloaded series on a different server. Those are set up using UNC as shown below:

image

I had to update the windows service to run as the proper user id, not localsystem for it to be able to access that path.

Suggestion, it might be helpful to put an error in the event log as to why the service crashed or that it cannot access a series folder or something like that.

Thanks for all the help. Love the new UI for v3!

UNC paths and windows service accounts are notorious for not working nicely together.

from what i remember the “workaround” was to;

  • manually login with the service account on the machine youre running sonarr (you may need to enable interactive login)
  • use windows file explorer to access the UNC path
  • enter the appropriate credentials and tick the “remember my credentials” option - that will then save those credentials into the account profile.
  • then reboot.

theoretically it should now be able to use those stored credentials to access the UNC path.

dont forget to disable interactive login

or you can do that :slight_smile:

Depends on the service account, localservice has no network share access, this is the default user for Sonarr v3.

Mapped Network Drives + Windows Services are entirely unsupported by MS and thus Sonarr, sometimes people manage to get them working, but they ultimately fail.

To be clear, I am not using a mapped drive (i.e. setting the T: drive to \server\share), I am specifying the UNC path directly inside of Sonarr as the print screen above shows. In that case, I just need to have the service run as a user that has access to that UNC.

Clearly not a common config that a normal user will use, but it can work.

Thanks for the help.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.