Hi all,
Anyone experiencing this issue? There was a new update tonight so i updated, within the app. After the updated downloaded completed, i was presented with the app has been updated click here to reload the page. I reload the page and it never loads. I check the package.

I try to run the package, it says its starting but it never runs.

I try to refresh the page a min or two later just in case it actually did start.

The only way to fix this is to uninstall and start over from scratch again.
admin@Syno:/var/packages/radarr/scripts$ ./start-stop-status start
Starting Radarr ...
admin@Syno:/var/packages/radarr/scripts$
radarr@Syno:/var/packages/radarr/scripts$ ./start-stop-status start
Starting Radarr ...
radarr@Syno:/var/packages/radarr/scripts$
I try to start from SSH and this is what i am presented with.
In case someone wants to see the logs, not a lot of info /shrug

Hi, please can you confirm your current installed dsm version?

Same problem, DSM 6.0.2-8451 Update 9
https://github.com/SynoCommunity/spksrc/issues/2216
EDIT: @madvtak you should provide the actual logs of radarr not the install log that one is just for installation purpose... check the /usr/local/radarr/ folder not sure where exactly the logs are stored there but most likely they should be in var :/
Your logs should be in
/var/packages/radarr/target/var/.config/Radarr/UpdateLogs
for the updates and
/var/packages/radarr/target/var/.config/Radarr/logs
for the main log
@cytec since this installed originally without issue on both DSM 5 and 6, I don't think it is linked to #2216
yeah saw that on the second read too... nevermind than
Ok, so on my latest DSM 6 reboot actually helped but there is definitely conflict with Sonarr. I'm having issues with running both at the same time. If Sonarr is working, I can't connect to Radar. If I stop both and start firstly Radarr and then Sonarr - I can access Radarr but Sonarr rejects my connection. Odd.
@newkind sound's like something you should report upstream maybe? maybe thats something that comes from the "fork/renaming" stuff
They claim that SynoCommunity package is the culprit.
https://github.com/Radarr/Radarr/issues/663#issuecomment-278356094
hm... would be strange... afaik they don't use same ports or anything... can you run both apps on your local pc side by side?
I don't have idea, got them installed only on my NAS.
I can whip up a VM and try running them both side by side on both Windows and Ubuntu...
That said, I have both running side by side on my DSM 6 VM, but I have changed the ports on both (one uses 8081, the other 8083)
now im even more confused ^^
can't be package related and isn't an upstream problem then... might just reinstall those SPK`s and try again?
EDIT: @KaraokeStu little off topic but any chance you gonna share that VM ;)
Ok, I found the culprit. They changed the default port from 8989 (Sonarr) to 7878 (Radarr), but they forgot to switch the default SSL port on which Radarr operates. By default is 8989 so the same as Sonarr thus the conflict.
@newkind Nicely done! Good spot!
Good catch. The reason why I didn't see a conflict was because I don't use SSL (on either). I'll be sure to update those both when I change the defaults for the package.
There is a branch that addresses this issue. It is a blind fix, since I'm in an airport and just about to hop in to a plane (so can't test whether upgrade wipes your config or if it even compiles) I just wanted to get this started so I don't forget about it.
Any word on the port default changes making it back into the parent package?
I will create the PR as soon as I have a chance to test the changes properly. I was out of the country for a week with limited possibilities for testing the changes. That's why the PR is still pending.
Drop a message here when its done and I'll get the changes compiled and published ASAP - in the mean time, good work @ressu !
Most helpful comment
I will create the PR as soon as I have a chance to test the changes properly. I was out of the country for a week with limited possibilities for testing the changes. That's why the PR is still pending.