Radarr: Failure connecting to Transmission initially every boot, works after 'Test'

Created on 4 Mar 2017  Â·  14Comments  Â·  Source: Radarr/Radarr

Description:

Every time I launch Sonarr or Radarr, I see this error:
Unable to communicate with Transmission. Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.

After that, if I go to Downloader settings and hit Test on Transmission, it works and resolves this issue, every time.

This pretty much means everytime I reboot my server I'm screwed until I dial in and hit Test each time.

Radarr Version:
0.2.0.375

Logs:

Details
Message
Unable to communicate with Transmission.: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.

Exception
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.
at System.Net.WebConnectionStream.EndWrite (System.IAsyncResult r) [0x000d3] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net/WebConnectionStream.cs:616
at System.Net.WebConnectionStream.Write (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x00059] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net/WebConnectionStream.cs:630
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000d9] in C:\projects\radarr-usby1\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:53
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000cc] in C:\projects\radarr-usby1\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:58
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x0007e] in C:\projects\radarr-usby1\src\NzbDrone.Common\Http\HttpClient.cs:63
at NzbDrone.Core.Download.Clients.Transmission.TransmissionProxy.ProcessRequest (System.String action, System.Object arguments, NzbDrone.Core.Download.Clients.Transmission.TransmissionSettings settings) [0x00072] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Transmission\TransmissionProxy.cs:260
at NzbDrone.Core.Download.Clients.Transmission.TransmissionProxy.GetTorrentStatus (System.Collections.Generic.IEnumerable`1[T] hashStrings, NzbDrone.Core.Download.Clients.Transmission.TransmissionSettings settings) [0x0007a] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Transmission\TransmissionProxy.cs:179
at NzbDrone.Core.Download.Clients.Transmission.TransmissionProxy.GetTorrentStatus (NzbDrone.Core.Download.Clients.Transmission.TransmissionSettings settings) [0x00000] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Transmission\TransmissionProxy.cs:153
at NzbDrone.Core.Download.Clients.Transmission.TransmissionProxy.GetTorrents (NzbDrone.Core.Download.Clients.Transmission.TransmissionSettings settings) [0x00000] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Transmission\TransmissionProxy.cs:43
at NzbDrone.Core.Download.Clients.Transmission.TransmissionBase.GetItems () [0x00000] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Transmission\TransmissionBase.cs:40
at NzbDrone.Core.HealthCheck.Checks.DownloadClientCheck.Check () [0x0003d] in C:\projects\radarr-usby1\src\NzbDrone.Core\HealthCheck\Checks\DownloadClientCheck.cs:32
Please use the search bar and make sure you are not submitting an already submitted issue.
Visit our Discord server for support or longer discussions.

bug stale

Most helpful comment

I have just tested and noticed that if the Sonarr/Radarr entries in rc.conf are after the Transmission entries, they will get the "Unable to communicate with Transmission" error after reboot.

As soon as I move the Sonarr/Radarr entries before the Transmission entries, all is right in the world after reboot.

All 14 comments

You said it does that with couchpotato too?

Sorry! Typo, I meant to say Sonarr or Radarr! I also have CouchPotato installed and it's not once reported an issue. Updated the text above.

You may want to cross post this issue with sonarrs issue page too.

Just want to add that I get this also - exactly as described.

I don't think I've cross posted to Sonarr if you'd like to file yours over there and relate.

Sent from my iPhone

On May 2, 2017, at 4:31 PM, Popsikill notifications@github.com wrote:

Just want to add that I get this also - exactly as described.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Version
0.2.0.778
Mono Version
5.0.1.1 (2017-02/5077205 Wed May 31 10:51:59 BST 2017)

I'm having the same issue. Transmission works, even without doing the test again, but everytime I restart my machine, I get that message in "Status" and need to Test it again in "Download client" option.

I thought about Radarr service being up before Transmission, but if I restart Raddar itself after this message, the problem isn't gone.

I have just tested and noticed that if the Sonarr/Radarr entries in rc.conf are after the Transmission entries, they will get the "Unable to communicate with Transmission" error after reboot.

As soon as I move the Sonarr/Radarr entries before the Transmission entries, all is right in the world after reboot.

Hello, any news on this?
I also have this "issue"in 2.0.0.5085.
I am running Sonarr in Debian and I don't find the /etc/rc.conf

This issue has been automatically marked as stale because it has not had recent activity. Please verify that this is still an issue with the latest version of Radarr and report back. Else this issue will be closed.

Well, I gave up and started using deluge. Since the post processing and such is done in radarr itself, no big deal, I just need to download the torrent.

Im unsubscribing from this thread since I'm now using deluge. Good luck!

This issue has been automatically marked as stale because it has not had recent activity. Please verify that this is still an issue with the latest version of Radarr and report back. Otherwise this issue will be closed.

This issue is still happening with the latest version of Radarr.

The only difference is the error is just displayed as Unable to connect

Was this page helpful?
0 / 5 - 0 ratings