Unable to connect to NzbGet - The object was used after being disposed

Hi

NzbGet and Sonarr works good and so do the downloads.
I only got one type of error message showing in sonarr and it is this:

Unable to connect to NzbGet. The object was used after being disposed.: Unable to connect to NzbGet. The object was used after being disposed.

http://pastebin.com/C7Ha76QE

Can I fix this in any way?

Which version of Sonarr?
Which version of mono?
Which OS?

Please provide logs with mono running with the --debug switch, the current logs are missing the line numbers, which are required for troubleshooting.

Sonarr: Version 2.0.0.3357
Mono Version 3.2.8 (Debian 3.2.8+dfsg-4+rpi1)

mono --version gives me:
Mono JIT compiler version 3.10.0 (mono-3.10.0-branch/ce003f4 Tue Nov 25 20:18:29 UTC 2014)

Raspberry PI with OS:
Linux raspberrypi 3.18.16-v7+ #796 SMP PREEMPT Fri Jun 19 22:18:53 BST 2015 armv7l

System > Logs > Tables (Show errors)
There are no line numbers
http://postimg.org/image/7kic067sd/

Sonarr is reporting Mono Version 3.2.8 (Debian 3.2.8+dfsg-4+rpi1) on System: Status?

You should eliminate the old mono version as it appears to be conflicting with 3.10.

Yes, under System > About is showing:
Mono Version 3.2.8 (Debian 3.2.8+dfsg-4+rpi1)

That means the mono being used to start Sonarr is 3.2.8, check your initialization script as it appears to be using the wrong mono.

Thank you… I’ve done that and will see if that was the problem.

I still get this message after changing the path to mono:

“Unable to connect to NzbGet. The object was used after being disposed.”

(I only get it once per day or less. But I still get it. And I haven’t
even downloaded anything. I guess Sonarr uses the wrong mono when it
runs it tasks or something?)

I have now activated debug mode under settings.

Mono is only called when restarting Sonarr or on update, in both cases mono is called without a full path so whatever is available from PATH is used.

If mono 3.2.8 is still on the system you could remove it.

You’ll need to look at the log files to view debug logs.

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