Episodes No Longer Showing in Queue (CDH Enabled)

Since Sonarr updated to Sonarr Ver. 2.0.0.3469 develop, episodes haven’t been showing in the queue any more. I noticed on the list of changes for the latest dev update that episodes wouldn’t show in queue if CDH was disabled. But in my case CDH is enabled. My download client is rtorrent. I am using sshfs with remote folder mapping.

They won’t show in the queue if CDH is disabled and the file completes.

Please Hastebin trace logs.

Ok, I will turn on trace logging and post logs soon. CDH is enabled.

Update: I enabled trace logging and searched, grabbed and downloaded a missing episode. These are the respective logs.

I don’t see any calls to rTorrent to get the details, a couple minutes more of logs should cover what we need.

Weird, episodes suddenly started showing up in the queue. I will add updated logs to this post in a few minutes.

Update: Logs
Update2: Actually I spoke too soon, just some episodes that can’t be located (for some reason rtorrent didn’t unpack some of the episodes) are showing up but not ones that are in good standing.

Is the issue with downloading or completed items? or both?

I don’t see anything that indicates an issue, but the rTorrent logs aren’t quite as nice as other clients (in how we log the response).

Looking at the code again nothing stands out that would cause any issues either, if CDH is disabled AND the download is completed we hide it.

The issue is with downloading items. When items are downloading they don’t appear in the activity queue. I don’t see any purple badges indicating items are downloading. I do have CDH enabled. It’s not a big deal because everything under the hood is working. I just thought that some change since the last update may have caused this because before the update all of those aspects that I mentioned were working. I didn’t really make any other changes.

So the latest commit didn’t fix this for me. I tried to clean out rTorrent so there are very few torrents in it to make troubleshooting a little easier. Here are some logs that show me searching, grabbing and downloading a torrent. The torrent shows up in the queue and reports correctly for a short time. But after it is finished downloading it shows that it is paused in the torrent client even though it is not paused (it is seeding). At this point if I look in tasks I can see that the check for finished downloads is stuck and no longer running every minute. It doesn’t always happen this way. Sometimes instead of showing the torrent being paused it just continues to show that the torrent is downloading, the purple bar remaining in what ever position it was in when the check for finished downloads last ran.

Update:
So I had another occurrence of this issue. One episode was downloaded first and was being copied. As soon as the copy started the CDH process froze. While that one was being copied another episode downloaded. When the first one finished downloading I noticed that the CDH process managed to cycle at least once but immediately froze up again as soon as the other one started copying over the sshfs mount. If you look at these logs the CDH process unfroze around 18:15 and then froze again shortly after.

So I can confirm now that my issue is not with rTorrent. I just tried using deluge with the same results. When sonarr starts copying the episode over the sshfs mount CDH freezes and no longer reports information to the activity queue. Here are the logs with deluge as that torrent client.

@markus101 it’s fairly simple actually. He has a slow downlink, about 1.5mbit/s, so it takes over an hour to copy/import, during which CDH won’t run.
We can’t deal with that till we get the IO pipeline in v3, kinda like https://github.com/Sonarr/Sonarr/issues/282.

Yeah, I realized what the issue was (or at least what I thought it was), but didn’t have a chance to confirm it, makes sense.

fyi, he flashed his router with OpenWRT instead of stock firmware, and now has 6.5mbit/s… yay. YES, ppl, firmware can make that much a difference.

@taloth The change you mentioned that would prevent Sonarr from grabbing dupes in a period of an hour doesn’t seem to be working for me. I was working on the server that Sonarr runs on so it was down for a few hours and when I turned it on it had some catching up to do. Well even in one rss run, it pulled 9 sets of dupes. Screenshot

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