Adding Sabnzbd Download Client - Error - Input string was not in a correct format

Help & Support
#1

Sonarr version (exact version): 2.0.0.4472
Mono version (if Sonarr is not running on Windows): 4.2.3 (Stable 4.2.3.4/832de4b Wed Mar 16 13:19:08 UTC 2016)
OS: Ubuntu 16.04.1 x64
((Debug logs)):http://pastebin.com/9u1i2JBP
Description of issue:
Error when connecting to Sabnzbd - “Test was aborted due to an error: Input string was not in a correct format.”. CouchPotato works with the same IP / API Key.

#2

Which version of SAB are you running?

It looks like a problem with the version bumber, could be a bad version number or a problem with how mono is handling that version number.

((Trace logs)) would be helpful to see what SAB is returning to Sonarr.

#3

Thanks for the response. Will get the requested info ASAP.

#4

Sabnzbd version looks like it’s the problem. The version number on the config page is:
1.1.x [unknown] .

I’ll examine the trace logs but that version number looks like a pretty good candidate.

Thanks.

#5

1.1.x is what they are reporting if you’re using their in progress releases I believe, as long as they are reporting 1.1.x on the API Sonarr should handle it properly, but may have issues depending on the mono version.

Are you running Sonarr in a docker container?

#6

Yes, Sonarr is running in a container.

#7

Here’s the trace: http://pastebin.com/45xDpTTS
It looks like it is breaking at the version number.

#8

I had some time to do some digging. I believe I’ve found the problem.

Sabnzbd.cs attempts to parse the version number after connecting to the Sabnzbd host.
Line 301 tries to convert the patch number and if Sabnzbd returns ‘x’ it replaces it with String.Empty (or even worse “”). Converting an empty string generates a FormatException.

Screenshot here: http://pasteboard.co/l0dIgvr0u.png

#9

Yeah, that’s it, funny enough we have tests to cover this, except I looked and the tests don’t actually seem to cover it, oops! Shouldn’t be too hard to get that fixed up.

#10

Can’t wait for live unit testing in VS2017 :slight_smile: Thanks for your help Markus.

1 Like
#11

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