Can't run up sonarr & radarr together?

[superloopy1]

Anyone know why not?

Doesn't matter which one comes up first the other fails to connect to webgui with a message along the lines of 'another instance is running'?? Sure this will be a simple fix but for a simple man it's proving extremely difficult, any ideas?

[Squid]

No reason you can't run them simultaneously, and many people do

 

Might help if you

 

Post a screen shot of your docker tab, and the exact message you're seeing

[superloopy1]

Thanks for the reply.

 

I this what you're after?

 

If i re-install radarr it seems to corrupt sonaar and the problem switches to that container, strange.

 

If it IS, as it is saying down to permissions then what needs to change? I have just gone with the existing defaults in each docker container.

 

 

2019-11-15 20:35:56,452 DEBG 'radarr' stdout output:
[Fatal] ConsoleApp: Address already in use. This can happen if another instance of Radarr is already running another application is using the same port (default: 7878) or the user has insufficient permissions

 

 

[superloopy1]

D'oh ... where have my screenshots gone?

 

How do i make them persistent?

[superloopy1]

Sonaar ...

Edited November 17, 2019 by superloopy1

[superloopy1]

Radaar

[Squid]

Can you click on show more settings for Sonarr

 

But, why are you running them both as network type Host.  They should be network type Bridge

[superloopy1]

Extra sonaar

Wont run up as bridge for the same reason.

 

 

[Squid]

2 minutes ago, superloopy1 said:

Wont run up as bridge for the same reason.

 

What do you mean

[superloopy1]

Switch it to bridge and the result is the same error message in the logs

 

2019-11-17 17:32:37,195 DEBG 'radarr' stdout output:
[Fatal] ConsoleApp: Address already in use. This can happen if another instance of Radarr is already running another application is using the same port (default: 7878) or the user has insufficient permissions

 

Attempts to connect

 

Firefox can’t establish a connection to the server at 192.168.1.15:7878

 

 

Edited November 17, 2019 by superloopy1

[Squid]

Post the docker run command https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345 for each of them

 

[superloopy1]

Switched back to host

[superloopy1]

Then over to bridge

[superloopy1]

With Radaar itself stopped and Sonaar switched to bridge the logs stil show the error message advising anothe instance running and unable to connect via webgui. Switch it back to host and all is available again

 

 

[Squid]

The template itself is messed up.  I would suggest making a note of your path mappings for each of them, then remove the apps.  Then from apps install them again (but NOT from previous apps) and add in the path mappings

[superloopy1]

Thanks.

 

I think the important part of your answer here could be 'NOT from previous apps', how is this achieved?

 

I have already deleted and reinstalled a couple of times and each time was more painful than the last as i needed to setup the whole application config again which i'm sure isnt really the way i should be doing it.

 

The odd occasion has just deleted and reinstalled over the top of the existing configs which, at the time, was just great but i cant remember how i set up the configs themeselves within each docker and if i lose them, wow!

Edited November 17, 2019 by superloopy1

[Squid]

29 minutes ago, superloopy1 said:

here could be 'NOT from previous apps', how is this achieved?

just search for binhex-sonarr and binhex-radarr

 

And you shouldn't lose anything as you'll be reusing the same appdata paths

Edited November 17, 2019 by Squid

[superloopy1]

Do i 'also remove image'?

 

[Squid]

won't hurt

[superloopy1]

I'm beaten!

 

Removed both dockers incl images and reinstalled firstly radaar ... couldnt get to webgui using ''bridge' but after changing to host COULD load and access.

 

Then reinstalled sonarr and same again using bridge. Changed to host and still couldnt connect with error message in log stating 'another instance is already runnin, blah de blah de bla'.

 

So ... it seems i can have one or the other as 'host' but not both at the same time using 'host'.

 

Using 'bridge' i get the same result, i can run one application but not the two of them ....

Edited November 17, 2019 by superloopy1

[itimpi]

26 minutes ago, superloopy1 said:

I'm beaten!

 

Removed both dockers incl images and reinstalled firstly radaar ... couldnt get to webgui using ''bridge' but after changing to host COULD load and access.

 

Then reinstalled sonarr and same again using bridge. Changed to host and still couldnt connect with error message in log stating 'another instance is already runnin, blah de blah de bla'.

 

So ... it seems i can have one or the other as 'host' but not both at the same time using 'host'.

 

Using 'bridge' i get the same result, i can run one application but not the two of them ....

Have you made sure when running as host that they are not trying to use the same port?

[superloopy1]

13 minutes ago, itimpi said:

Have you made sure when running as host that they are not trying to use the same port?

I get exactly the same result if i switch them to bridge though.

 

They dont 'use' the same port do they?

 

Which ports are you referring to?

 

Sonarr uses port 8989, radarr 7878, i'm assuming i dont need to change anything else although given that radarr is just sonaar under the hood i wouldnt be surprised if that could be the case.

Edited November 17, 2019 by superloopy1

[superloopy1]

Well now ... in both radaar AND sonaar logs i'm seeing the following

 

 

Sonaar

19-11-17 20:37:10.8|Info|OwinHostController|  http://192.168.1.15:8989/
19-11-17 20:37:10.8|Info|OwinHostController|  https://192.168.1.15:9898/
19-11-17 20:37:10.8|Info|OwinHostController|  http://localhost:8989/
19-11-17 20:37:10.8|Info|OwinHostController|  https://localhost:9898/
Radaar

19-11-17 20:42:24.7|Info|OwinHostController|  http://192.168.1.15:7878/
19-11-17 20:42:24.7|Info|OwinHostController|  https://192.168.1.15:9898/
19-11-17 20:42:24.7|Info|OwinHostController|  http://localhost:7878/
19-11-17 20:42:24.7|Info|OwinHostController|  https://localhost:9898/

 

Port 9898 is mentioned in BOTH logs  as https://localhost access port, surely this ISN'T correct???

[superloopy1]

Or am I clutching at straws here?

[superloopy1]

No more contributors to this one?

 

Can anyone confirm from their logs of sonarr and radarr that port 9898 also shows there, i will be able to rule that out as the reason for my problem.