The dockers have been working great for the past year but now both Sonarr and Radarr will not connect to any indexers or my NZBget. I also have Lidarr installed with the same configuration and that docker is connecting to the indexers and NZBget without any issues. I have updated all of my dockers to the latest versions, But I have not changed any configurations since I set it up a year ago. Could you provide some insight on how to get it working again please. 

 

Unraid v6.8.3

 

Sonarr Error - 2020-11-05 23:42:34,686 DEBG 'sonarr' stdout output:
[Error] ProxyCheck: Proxy Health Check failed

[v2.0.0.5344] System.Net.WebException: Error: ConnectFailure (Connection refused): 'http://services.sonarr.tv/v1/ping' ---> System.Net.WebException: Error: ConnectFailure (Connection refused) ---> System.Net.Sockets.SocketException: Connection refused

 

Radarr Error -  [v0.2.0.1504] NzbDrone.Core.Download.Clients.DownloadClientException: Unable to connect to NZBGet. Error: ConnectFailure (Connection refused): 'http://192.168.1.121:6789/jsonrpc' ---> System.Net.WebException: Error: ConnectFailure (Connection refused): 'http://192.168.1.121:6789/jsonrpc' ---> System.Net.WebException: Error: ConnectFailure (Connection refused) ---> System.Net.Sockets.SocketException: Connection refused

Solved

Edited November 12, 20205 yr by cicerojones
solved

Hello everyone, I am a recent convert from Windows to unraid for my server needs. I am working on getting my media automation setup and am running into issues with Radarr. I followed the videos from Spaceinvader (Thanks you!) and was able to get Sab and Sonarr working, but I cannot get Radarr to cooperate. 

 

The movie downloads properly into storage, but it does not move from the /DOWNLOADS/complete/movies/ directory into my media/movies directory. Attached is a copy of the Radarr log (with title redacted) and screenshots of my docker configs.  

 

I have no doubt I am missing something simple, but can't seem to wrap my head around it.

radarr.txt

 

 

Edit: was able to figure it out - I had secured the shares. Once I set them to public it was able to function. Is it possible to have the shares secured and have this function properly (either as a secured or private share?)

I have this warning in my dashboard:

 

V3 is a nice upgrade! 

Please upgrade to the .NET Core version of Radarr	

https://wiki.servarr.com/Radarr_System#update-to-net-core-version

 

On 11/24/2020 at 7:01 PM, Fiala06 said:

I have this warning in my dashboard:

 

V3 is a nice upgrade! 

Please upgrade to the .NET Core version of Radarr	

https://wiki.servarr.com/Radarr_System#update-to-net-core-version

 

binhex-radarr support v3?

4 hours ago, Damix21 said:

binhex-radarr support v3?

Not sure when but I logged in a few days ago for the first time in awhile and noticed it was V3. 

 

15 minutes ago, Fiala06 said:

Not sure when but I logged in a few days ago for the first time in awhile and noticed it was V3. 

 

How are you getting V3? The latest release in this repo is v0.2.

Are there ways to force the Binhex repo to update to V3? 

6 minutes ago, Force098 said:

Are there ways to force the Binhex repo to update to V3? 

No. You would need to switch dockers to one that includes betas. This one only provides the stable release.

Thanks, I've run into issues with Radarr not processing some movies when they finish downloading. The logs don't seem to indicate any failures, it just seems like the MovieService|Linking process isn't called for some. Discord recommended upgrading to V3, but now I think I'd like to figure out what the problem is to better understand the environment. 

21 hours ago, Force098 said:

Thanks, I've run into issues with Radarr not processing some movies when they finish downloading. The logs don't seem to indicate any failures, it just seems like the MovieService|Linking process isn't called for some. Discord recommended upgrading to V3, but now I think I'd like to figure out what the problem is to better understand the environment. 

I have the same problem (in Sonarr too, I upgraded to Sonarr-v3 and the problem is gone). Maybe it is the same problem: 

 

Just received an update to binhex-radarr and it wont start.  The log shows:

2020-11-29 18:19:20,658 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22513266745792 for <Subprocess at 22513267025856 with name radarr in state STARTING> (stdout)>
2020-11-29 18:19:20,658 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22513267026576 for <Subprocess at 22513267025856 with name radarr in state STARTING> (stderr)>
2020-11-29 18:19:20,658 INFO exited: radarr (exit status 2; not expected)
2020-11-29 18:19:20,658 DEBG received SIGCHLD indicating a child quit
2020-11-29 18:19:23,663 INFO spawned: 'radarr' with pid 67
2020-11-29 18:19:23,673 DEBG 'radarr' stderr output:
Cannot open assembly '/usr/lib/radarr/Radarr.exe': No such file or directory.

Seems the executable does not exist.  I am not sure how to fix it, any suggestions?

Hello, I am  having the same problem, can't start Radarr.

 

Thanks.

 

2020-11-29 09:03:53,562 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23149522694640 for <Subprocess at 23149522974704 with name radarr in state STARTING> (stdout)>
2020-11-29 09:03:53,562 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23149522975904 for <Subprocess at 23149522974704 with name radarr in state STARTING> (stderr)>
2020-11-29 09:03:53,562 INFO exited: radarr (exit status 2; not expected)
2020-11-29 09:03:53,562 DEBG received SIGCHLD indicating a child quit
2020-11-29 09:03:56,566 INFO spawned: 'radarr' with pid 67
2020-11-29 09:03:56,576 DEBG 'radarr' stderr output:
Cannot open assembly '/usr/lib/radarr/Radarr.exe': No such file or directory.

2020-11-29 09:03:56,581 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23149523378080 for <Subprocess at 23149522974704 with name radarr in state STARTING> (stdout)>
2020-11-29 09:03:56,581 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23149522740944 for <Subprocess at 23149522974704 with name radarr in state STARTING> (stderr)>
2020-11-29 09:03:56,581 INFO exited: radarr (exit status 2; not expected)
2020-11-29 09:03:56,581 DEBG received SIGCHLD indicating a child quit
2020-11-29 09:03:57,583 INFO gave up: radarr entered FATAL state, too many start retries too quickly

 

Same issue for me, exact same log information posted above.  Just updated a couple minutes ago 

 

Could be related, but I aso just updated DelugeVPN, and I can't open that either.  Sonarr was not updated, and that's opening just fine. 

Edited November 29, 20205 yr by kennygunit

I managed to start Radarr using the console and it seems to have updated to v3.  The new binary does not have an .exe extension and is in a new directory called bin.  I have stopped it for now and will await an update to the docker instance.

Getting the same as above after the update

Okay, glad it's not just me then.

I'm guessing you're on the case! Thanks!

yes same here

 

020-11-29 13:09:26,807 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22735375843824 for <Subprocess at 22735376123888 with name radarr in state STARTING> (stdout)>
2020-11-29 13:09:26,807 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22735376125088 for <Subprocess at 22735376123888 with name radarr in state STARTING> (stderr)>
2020-11-29 13:09:26,807 INFO exited: radarr (exit status 2; not expected)
2020-11-29 13:09:26,807 DEBG received SIGCHLD indicating a child quit
2020-11-29 13:09:29,811 INFO spawned: 'radarr' with pid 68
2020-11-29 13:09:29,823 DEBG 'radarr' stderr output:
Cannot open assembly '/usr/lib/radarr/Radarr.exe': No such file or directory.

2020-11-29 13:09:29,828 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22735376527264 for <Subprocess at 22735376123888 with name radarr in state STARTING> (stdout)>
2020-11-29 13:09:29,829 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22735375890128 for <Subprocess at 22735376123888 with name radarr in state STARTING> (stderr)>
2020-11-29 13:09:29,829 INFO exited: radarr (exit status 2; not expected)
2020-11-29 13:09:29,829 DEBG received SIGCHLD indicating a child quit
2020-11-29 13:09:30,830 INFO gave up: radarr entered FATAL state, too many start retries too quickly

 

It looks like v3 has now dropped and therefore I need to modify some bits and pieces to to get the image working again. I shall take a look at this tonight.

Sent from my CLT-L09 using Tapatalk

Thanks a lot mate, you're a legend!

19 minutes ago, binhex said:

It looks like v3 has now dropped and therefore I need to modify some bits and pieces to to get the image working again. I shall take a look at this tonight.
 

Thanks, much appreciated!

 

I'm guessing that similar might be happening with Sonarr soon too then?

21 minutes ago, binhex said:

It looks like v3 has now dropped and therefore I need to modify some bits and pieces to to get the image working again. I shall take a look at this tonight.

Sent from my CLT-L09 using Tapatalk
 

Has stable been upgraded to v3?

Same problem here. Thanks for looking into this. Love this App. Makes life so much easier.

Many thanks for looking into it. 

 

I thought I would post my error log incase it helped in any way (not much info to be fair). 

 

Quote

2020-11-29 13:10:36.101866 [info] System information Linux 2a083dfe5ebb 5.8.18-Unraid #1 SMP Mon Nov 2 07:15:12 PST 2020 x86_64 GNU/Linux
2020-11-29 13:10:36.158054 [info] OS_ARCH defined as 'x86-64'
2020-11-29 13:10:36.213705 [info] PUID defined as '99'
2020-11-29 13:10:36.279693 [info] PGID defined as '100'
2020-11-29 13:10:36.432132 [info] UMASK defined as '000'
2020-11-29 13:10:36.487372 [info] Permissions already set for volume mappings
2020-11-29 13:10:36.545230 [info] Deleting files in /tmp (non recursive)...
2020-11-29 13:10:36.603967 [info] Starting Supervisor...
2020-11-29 13:10:36,896 INFO Included extra file "/etc/supervisor/conf.d/radarr.conf" during parsing
2020-11-29 13:10:36,897 INFO Set uid to user 0 succeeded
2020-11-29 13:10:36,901 INFO supervisord started with pid 6
2020-11-29 13:10:37,906 INFO spawned: 'radarr' with pid 55
2020-11-29 13:10:37,907 INFO reaped unknown pid 7 (exit status 0)
2020-11-29 13:10:37,934 DEBG 'radarr' stderr output:
Cannot open assembly '/usr/lib/radarr/Radarr.exe': No such file or directory.

2020-11-29 13:10:37,946 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22765397516736 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stdout)>
2020-11-29 13:10:37,946 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22765397519520 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stderr)>
2020-11-29 13:10:37,946 INFO exited: radarr (exit status 2; not expected)
2020-11-29 13:10:37,947 DEBG received SIGCHLD indicating a child quit
2020-11-29 13:10:38,951 INFO spawned: 'radarr' with pid 59
2020-11-29 13:10:38,980 DEBG 'radarr' stderr output:
Cannot open assembly '/usr/lib/radarr/Radarr.exe': No such file or directory.

2020-11-29 13:10:38,991 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22765397921696 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stdout)>
2020-11-29 13:10:38,991 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22765397284656 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stderr)>
2020-11-29 13:10:38,992 INFO exited: radarr (exit status 2; not expected)
2020-11-29 13:10:38,992 DEBG received SIGCHLD indicating a child quit
2020-11-29 13:10:40,998 INFO spawned: 'radarr' with pid 63
2020-11-29 13:10:41,026 DEBG 'radarr' stderr output:
Cannot open assembly '/usr/lib/radarr/Radarr.exe': No such file or directory.

2020-11-29 13:10:41,037 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22765397238256 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stdout)>
2020-11-29 13:10:41,037 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22765397519520 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stderr)>
2020-11-29 13:10:41,038 INFO exited: radarr (exit status 2; not expected)
2020-11-29 13:10:41,038 DEBG received SIGCHLD indicating a child quit
2020-11-29 13:10:44,045 INFO spawned: 'radarr' with pid 67
2020-11-29 13:10:44,074 DEBG 'radarr' stderr output:
Cannot open assembly '/usr/lib/radarr/Radarr.exe': No such file or directory.

2020-11-29 13:10:44,085 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22765397921696 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stdout)>
2020-11-29 13:10:44,085 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22765397284560 for <Subprocess at 22765397518320 with name radarr in state STARTING> (stderr)>
2020-11-29 13:10:44,086 INFO exited: radarr (exit status 2; not expected)
2020-11-29 13:10:44,086 DEBG received SIGCHLD indicating a child quit
2020-11-29 13:10:45,087 INFO gave up: radarr entered FATAL state, too many start retries too quickly
2020-11-29 13:10:45,087 INFO gave up: radarr entered FATAL state, too many start retries too quickly

 

58 minutes ago, binhex said:

It looks like v3 has now dropped and therefore I need to modify some bits and pieces to to get the image working again. I shall take a look at this tonight.

Sent from my CLT-L09 using Tapatalk
 

Thank you for your job.