After new router, shows can't be added?

Version

2.0.0.5301

Mono Version

5.0.0

AppData directory

/config

Startup directory

/opt/NzbDrone

OS X Mojave 10.14.4, BUT Sonarr/Radarr/NZBGet are ALL running on Synology DS416Play with DSM 6.2.1 via Docker containers

Pastebin of last couple of days:

https://pastebin.com/M5CBhw2Y

Have got my network squared away after getting a new router. NZBget works perfectly, no issues, Radarr works perfectly, no issues. Sonar will grab CURRENT/NEW episodes of shows already added in my library, but if I go to add a NEW show, either by clicking “add” or “add and search” after the show is found in “add new series” field, the wheel will just spin, the show will not get added to library, and I can see no issue in the logs (although I am not a pro at reading them!)

Basically I can’t add new shows to Sonarr, but I have my current shows in my library already and Sonarr is grabbing new releases as it should.

Thanks for any and all help!

That’s an old version, upgrade to 5.18 to start.

Ok that makes sense, but what is the easiest way to do that? the mono I have installed on the Synology says 4.6.2-0096, but that’s the one authorized by synology package center…I know how to do a manual install in synology of files in the package center, so is that how I should do it?

Are you running Sonarr directly on the Synology or in a docker container? You said docker above which makes the version on the Synology irrelevant (and it doesn’t match what you said in your original post).

Assuming you’re using docker, you’ll need to update the container to one that includes an updated mono.

ok did I manual install from the package center from this site:

https://synocommunity.com/package/mono

after that I stopped and restarted all containers

in Sonarr it still says:
Version

2.0.0.5301

Mono Version

5.0.0
AppData directory
/config
Startup directory
/opt/NzbDrone

BUT in Radarr, it says:

Version
0.2.0.1293
Mono Version
5.18.0.240 (tarball Wed Jan 16 09:13:03 UTC 2019)
AppData directory
/config
Startup directory
/opt/radarr

Sonarr/radarr/nzbget in a docker container

That won’t update the mono version in the container, you need to pull down the latest image for Sonarr and rebuild the container.

Not sure if https://www.reddit.com/r/synology/comments/6put9m/update_docker_containerimage/ will help or not, if not look into how to update images.

Ok so last night BEFORE I posted this post, here’s what I did:

Went into docker panel in the Synology
Searched for nzb/radarr/sonarr
Clicked get latest
Image downloaded
Stopped each container one by one
Clicked clear for each container
Opened each container
Everything still worked after that so I THOUGHT i updated each container

This is the correct way to update containers with the Synology, correct?

Where do I see the current and correct version of sonarr/radarr that dockeris currently using to see if I have the latest one installed correctly?

Do I need to do this again because of the new mono that I installed later that night?

I’m working today but will try again as soon as I am home.

I’m not sure.

No, as I’ve said the version installed on the synology directly is irrelevant.

markus101…I think I get what you’re saying about mono. regardless of where I download it, I shouldn’t be doing anything with it via the Synology package center because the docker system is to using the Synology mono package, but it’s own package…is that right?

As far as I can tell, I have updated all my containers successfully via the link to reddit you posted.

Correct, it has it’s own mono package.

Which docker image are you using for Sonarr? It’s possible that it’s using an old mono version, the linuxserver.io image uses 5.18 though.

using the linuxserver.io one as thats the one I was told to use a couple of years ago.

I swear I followed the directions. stopped the container. Searched for it, grabbed the latest. Cleared the contents of the previous version. clicked start. works.

Do my paths look correct:

Besides /config they’re flexible, but they look fine.

That /config is supposed to point to the config.xml file, correct? Not the configs folder? Like I didn’t leave an ‘s’ off and it can’t find the config files, right?

No, it’s to the folder.

Should I change that folder to /configs to match /apps/configs/sonarr?

No, /config is what the ls.io image expects.

so I don’t need to change anything at all in my folder setups since they are all working and have been working, right?

this doesn’t say much but proves what you’re saying about it being out of date version

Then this happened:

And then this:

You don’t want to pull a mono docker image, you want to update the Sonarr docker image to the latest version and pulling a docker image for mono won’t upgrade the system mono version (the mono --version check you do won’t be any different having pulled that container).

Fixed.

Version

2.0.0.5301

Mono Version

5.18.0.240

AppData directory

/config

Startup directory

/opt/NzbDrone

I backed up my sonarr folder to a different location just in case and reinstalled latest then just set it up from scratch.

Thanks for all your help, markus101.

1 Like

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