-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Sonarr to v3 #3803
Update Sonarr to v3 #3803
Conversation
I would like to test. Not sure how to access the package. |
So sorry I didn't see this last week! To the build machine! 🤖 🖥 The releases can be downloaded here: I've only uploaded the packages, in case of problems please report them here so @maxrogers can look at them 👍 |
Thanks @Safihre |
I have never updated Sonarr via spk file before. Will this package detect v2x and upgrade to v3x automatically? |
@Fringe09, yes it should do just that. Complete a manual backup via Sonarr web-interface (and download a copy) before attempting (just in case.) |
hi @Safihre |
|
Wanted to chime in that I updated to v3 with the "nzbdrone_x64-6.1_20191122-16.spk" package on my Synology DS415+ and everything went smooth as butter! Thanks so much :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some improvement proposals
Wanted to mention I used |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @maxrogers
May you please investigate if it may be possible to rename package with comfort for users?
@ymartin59 Yes, I will look into this as soon as I have some free time. |
@ymartin59 I have made a package that successfully upgrades while also renaming from nzbdrone to sonarr. However, the method is too crude and I do not think it is worth doing it just to change the internal naming of the package (from For example: Here are the errors that I get when trying both: synopkg stop nzbdrone I tried adding Because the installer does not allow us to use synopkg during an install we have to manually kill processes and then manually delete the package from Additionally, the package installs as a new install (not an upgrade) therefore to keep the same port number we have to install the package with a different port number and then modify three files to use the correct port number. In addition, there are a few other issues that require adding more complexity to service-setup.sh to address the issue of introduced by performing upgrade tasks in the install portion (due to the package installing as a new install not an upgrade). NOTE: I also attempted to do the package name change via an upgrade of the nzbdrone package. However, that method introduces potential user permission issues and will also require a second follow-up package to fully rename the package to |
Stumbled upon this, since I had issues with v2. So, just did the update on my DS918+ with the "generic x64"-package - worked like a charm! Asked for an extra minor update - and then just got to work. Thanx! While I am at it - am I missing that there is a Radarr v.3 lurking on github somewhere as well? Could not find any when I searched? Kudos to all you guys who have the skills (and time) to do this! |
@maxrogers Thanks for looking into this. But now how to proceed? Seems we have to wait for Sonarr to officially stop with V2 before we can push this package, since it will replace the V2 package. |
Thanks a lot guys, was struggling with V2 and language filter problems. Found this. Migration worked like a charm on DS713+ ! |
Any tips for getting this version to function fully on an RTD1296 processor? |
Mono 5.20 is broken on rtd1296. Apparently 5.8 might work, or you can sideload docker and work around it that way. It won't be long before minimum Sonarr mono version is 5.20 :/ |
@Chrisophogus try 5.8 from here |
If you're feeling brave you can install docker with these instructions https://wiki.servarr.com/Docker_ARM_Synology |
Thanks both for the pointers. Rolling back to Mono 5.8 was the immediate fix. I think the long term is going to be the docker solution. Thanks again for that link, an actual easy to understand process to install Docker on this thing. |
@Wuszek @houndtt @ta264 I've created a wiki entry since this has come up a lot: https://github.com/SynoCommunity/spksrc/wiki/Radarr-Sonarr-Lidarr-Jackett. Would you mind updating it with the package versions that work for you or anything else that could help users or has been repeated here elsewhere? Thanks |
@publicarray sure. In case of Sonarr, that still requires mono in v3, (at least for now), indeed I need to use mono v5.8, because there is some bug related with https/ssl certificate in newer versions, if I can remember correctly. |
* Update Sonarr to v3-stable * Sonarr: remove busybox * Sonarr: fix file doesn't exists and file exists errors * Add https Co-authored-by: Sebastian Schmidt <[email protected]> * change to PKG_NAME Co-authored-by: hgy59 <[email protected]> * Sonarr: Smooth migration from nzbdrone Framework: add install_replace_packages, install_break_packages and checkport Note: In the future (DSM7) prereplace and postreplace scrips should be used instead * Revert "Sonarr: Smooth migration from nzbdrone" This reverts commit 4d88fa9. Co-authored-by: Sebastian Schmidt <[email protected]> Co-authored-by: hgy59 <[email protected]>
@ Christophogus @Wuzek |
@GandulfM Sonarr phantom branch latest update works fine with NZBGeek for me on DS420j with Mono 5.8. I just have the general error that 5.8 is not supported. |
Sonarr phantom is dead and out of date. Two main versions have been released since phantom was killed |
Your right, i'm on main, 3.0.6.1196
…On Sat, Apr 10, 2021 at 6:21 PM bakerboy448 ***@***.***> wrote:
Sonarr phantom is dead and out of date. Two main versions have been
released since phantom was killed
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3803 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADKFYM2UTXOUXURLRFFWL3TID2TLANCNFSM4JMJAV5Q>
.
|
Oh but I've been updating via the Sonarr UI, haven't updated via DSM in a while. |
I've been trying to update to Sonarr v3 but just noticed the new package doesn't support the evansport architecture of my DS214Play. Just wondering if my NAS is too old and not supported anymore? (Radarr v3 does does still seem to be supported) |
This is what i just did for my DS418: |
bit stuck with the new update to Sonarr V3 on my DS218play - RTD1296 processor.
[v3.0.5.1144] System.Net.WebException: Error: TrustFailure (One or more errors occurred.): 'https://drunkenslug.com/api?t=caps&apikey=(removed) ---> System.Net.WebException: Error: TrustFailure (One or more errors occurred.) ---> System.AggregateException: One or more errors occurred. ---> System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> anyone have any ideas or dealing with similar issue? |
That's the issue I had.
Revert back to 5.8 by downloading the package directly from
https://synocommunity.com/package/mono
Sonarr is complaining it's on 5.8 but it's working fine.
…On Wed, 14 Apr 2021 at 09:41, origami-army ***@***.***> wrote:
bit stuck with the new update to Sonarr V3 on my DS218play - RTD1296
processor.
Had Sonarr v2 with mono 5.8 and seemed to work with indexers (did
encounter the bug with 5.20 few months back and had to revert)
- Radarr updated to V3 and seemed to work well with mono 5.8
- Wanted to try Sonarr V3 and updated - indexers stopped working
unfortunately - thought it was related to mono 5.8 so updated to 5.20 but
now still stuck with errors connecting:
[v3.0.5.1144] System.Net.WebException: Error: TrustFailure (One or more
errors occurred.): 'https://drunkenslug.com/api?t=caps&apikey=(removed)
---> System.Net.WebException: Error: TrustFailure (One or more errors
occurred.) ---> System.AggregateException: One or more errors occurred.
---> System.Security.Authentication.AuthenticationException: A call to SSPI
failed, see inner exception. --->
anyone have any ideas or dealing with similar issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3803 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIJKXMG7UPCWR56PTKXCX3TIVIMZANCNFSM4JMJAV5Q>
.
|
Hmm - was having issue with V3 & 5.8 mono prior to updating but I'll try reverting again. Do you know of a way of doing this without uninstalling Sonarr? |
Download last backup from Sonarr (zip package by ssh if you can't download it from web Sonarr interface), reinstall packages and upload backup |
Wow that was unexpected - thanks for the help, resolved now. Reinstalling with mono 5.8 (even though I was originally on 5.8 when it first stopped working) allowed indexers to work again. Restore now doesn't require SSH to upload so was able to do it seamlessly from the Sonarr settings |
Hi guys,
I advice to download the 5.8 version to your computer and then manually install to your Synology.
And download to your computer and manually install this version.
I understand from #3803 (comment) they are working on a version of Sonarr that doesn't need Mono to run, like already is the case with Radarr. |
Thanks for the information @GandulfM. We do have a wiki entry, and you are welcome to add to it: https://github.com/SynoCommunity/spksrc/wiki/Radarr-Sonarr-Lidarr-Jackett |
@publicarray, for my DS418 I manually installed https://github.com/Safihre/spksrc/releases/download/sonarr-v3-build/nzbdrone_rtd1296-6.1_20201116-19.spk However, after a restart of my diskstation Sonarr was running again! Edit: Today, after checking dates and times, it appeared Sonarr had not stopped running but just only the interface. A restart of my diskstation made the interface visible again. |
I get the problem that Sonarr and radar says
The services is stopped and when i try to start it its gets backed to stopped state. Tried to follow @GandulfM steps above but when I am trying to roll back but when i manually install Mono it says current package version is 5.20.1.34-16. You cannot roll back to the older version 5.8.0.108-11. I am unable to uninstall Mono since it says Sonarr and Radarr is dependent on it. How do i solve this? I noticed some say i can download the backup file, i were considering doing that and moving do Docker but were can i find the backup files for Sonarr and Radarr? |
What you need to do is uninstalling Mono, Sonarr and Radarr. |
Do i need to take a backup first? If so how? or will the data remain on my drives even if i uninstall and when i reinstall they will use the data that is already there? |
@Segelfeldt |
I'm locking this issue, this is not the place (anymore) for instructions how to get it running. |
Checklist
all-supported
completed successfullyI just did a successful upgrade from Sonarr v2 to this package (v3) with no issues. It would be great to get a few experienced users to test and share their success/results going from v2 to v3 with this package. @Safihre can you make packages for people to test with? Thank you!
Motivation: To add a v3 Sonarr package
Reference: #3518 (comment)