Since the latest update to NZBDrone, I’ve checked my SABnzbd queue to find up to 3 instances of the same episode downloading.
For example, moments ago, Supernatural S09E05 had 3 instances of the same download in the queue added by NZBDrone.
This is very frustrating as I’m wasting my monthly quota.
Drone does a number of checks to ensure that this doesn’t happen, with the latest release there were some changes to one of the checks to support blacklisting.
In order to track this down we’ll need to get trace logs of it occurring, you can enable trace logging on the general settings page. If you notice it happening again, please zip up your logs and PM me a link to download them.
In the meantime you can tell SAB to pause duplicate downloads instead of processing them.
/deleted
Sending the log now.
Thanks. It looks like drone is sending the nzb to SAB, but failing to update its history due to a failure processing the response from SAB. What version of SAB are you running? It doesn’t show the SAB response, but I believe the issue has to do with with the response not being in the proper format. The version of SAB will help me track down the respinse its sending as well as correct the issue.
Ummm, it’s in the title of the post, but I’ll say it anyway, SABnzbd v0.7.16
Sorry, missed that. Thats the same version that I’m using for testing, which does return the proper response.
Unfortunately we’re not logging the response from SAB before we try to parse it, I’ll get some logging in and pushed out so I can track it down.
Logging has been added to the develop branch, you can switch to that branch by following the steps here: https://github.com/NzbDrone/NzbDrone/wiki/Release-Branches
Once its going please grab a trace log of the issue and send it over, should help track this down.
Sorry, got caught up with other stuff and didn’t see the reply.
Did you still want me to go ahead and get that log to you?
Yeah, the logging is still in develop and I haven’t seen this behavior anywhere else.
ok, sending you a PM with the new log file, and further details.
Sorry @the1poet I messed up the logging and its not logging anything. Anything thats queued by drone should log the same error, so there shouldn’t be a need to wait for it to queue the episode multiple times.
Grabbing the latest update on either the develop or master branch will have the fix.
As in a fix to the problem I’m having? Or a fix to the logging? I’m using the develop branch and am running the latest version 2.0.0.853
Sorry I wasn’t clear, just a fix for the logging, 2.0.0.853 has it.
OK, sending another log from the newer version of nzbdrone.
I am seeing the same thing here. i will turn on logging to help out.
I see in version .868 the “Fixed” item is “Handling of unexpected responses from SABnzbd when adding releases”.
Is this for this issue?
Yeah, was an issue with that particular version, but the latest should have the issues resolved.
Am I right to switch back to the master branch in Nzbdrone?
It’s not fixed in master yet, just develop.