[Request]sonarr v3 package

[M0UL]

this maybe a bit early, i would like to request a sonarr v3 package for synology.
sonarr v3 will require a new package since it will not possible to update to v3 from the v2 webui.
it is possilbe to reuse the v2 database in v3.

more info can be found here

[ymartin59]

OK, noticed.

[Safihre]

I can take a look, once it is released for stable.

[Stanzilla]

A beta package would be nice for the time being

[AthAshino]

Any updates about sonarr v3 ? The beta seems to be really interesting

[M3rofio]

when it will be available on synology packages

[shanelord01]

I can take a look, once it is released for stable.

Hey @Safihre any chance a beta package can be released like SynoCommunity has done for the "Custom" packages that let you run a fork of your choice?

Thanks for you hard work.
Shane.

[icegunner]

So, it looks like some changes were made for v3 compatibility to the service-setup.sh script through commit 117650e. So, does this mean that v3 is now supported?

[dylanhughes15]

Any update on this yet?

[epheterson]

Would really love to try this, any ETA on support?

[Fringe09]

Same here. It would be great to have a v3 package to test at minimum.

[Rodnehh]

Me three

[Safihre]

The test-releases can be downloaded here:
https://github.com/Safihre/spksrc/releases/tag/sonarr-v3-build
To see which version you need:
https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model (Models that have (x64) listed can use the general x64 testing packages)

I've only uploaded the packages, in case of problems please report them at #3803 so @maxrogers can look at them 👍

[Rodnehh]

The test-releases can be downloaded here:
https://github.com/Safihre/spksrc/releases/tag/sonarr-v3-build
To see which version you need:
https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model (Models that have (x64) listed can use the general x64 testing packages)

I've only uploaded the packages, in case of problems please report them at #3803 so @maxrogers can look at them 👍

Thanks Safihre!

[simonwestenholz]

Thanks for making this available. I don't see an Avoton build, however. Is there a build I can use for a DS1815+?

[mcattle]

Thanks for making this available. I don't see an Avoton build, however. Is there a build I can use for a DS1815+?

@simonwestenholz: According to Safihre's post you can use the general x64 testing package.

[LwsBtlr]

I’ve installed this and trying to updated it using the Internet updater, but that seems to be failing (to 20200107-mumble)

[Safihre]

@LwsBtlr You need to be a bit more specific. Did you check the logs why it fails?

[LwsBtlr]

I reinstalled it and then it updated properly. ¯_(ツ)_/¯

[Stanzilla]

@Safihre any chance for a 88f6282 package?

[LwsBtlr]

Updated to 3.0.3-688 fine, if that is what you’re asking.

[Safihre]

@Stanzilla try the 88f6281 package, it's the same architecture so should work I think.

[Stanzilla]

Hrm, package failed to start, will try getting logs later

[Stanzilla]

alright, restart fixed it! Currently installed Mono version 5.8.0.108 is supported but has some known issues. Please upgrade Mono to version 5.20 do we have that somewhere?  
 

[hgy59]

@Stanzilla yes I have Mono 5.20 ready, but am waiting for #3852 to be merged.

[Stanzilla]

@hgy59 got a link to a test version or would you advise to not install it on a production system yet?

[Stanzilla]

Hrm not sure why but it suddenly broke:

Mon Feb  3 01:00:23 CET 2020
Starting nzbdrone command env PATH=/usr/local/mono/bin:/volume1/@appstore/nzbdrone/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin HOME=/volume1/@appstore/nzbdrone/var LD_LIBRARY_PATH=/volume1/@appstore/nzbdrone/lib /usr/local/mono/bin/mono /volume1/@appstore/nzbdrone/share/Sonarr/Sonarr.exe 
Cannot open assembly '/volume1/@appstore/nzbdrone/share/Sonarr/Sonarr.exe': No such file or directory.

Interesting, the files are just gone, probably something gone wrong during self-update?

[maxrogers]

@Stanzilla odd, do you have any more info? Sonarr logs?

Did this happen after you ran a Sonarr update? Had you run an update previously?

[Stanzilla]

Did not really touch it after installing updates, logs attached!

logs.zip

[maxrogers]

@Stanzilla It seems that it failed while updating because /tmp/sonarr_update/sonarr_backup wasn't empty:

20-2-2 03:30:41.4|Info|InstallUpdateService|Deleting old update files
20-2-2 03:30:42.9|Info|InstallUpdateService|Downloading update 3.0.3.690
20-2-2 03:30:46.5|Info|InstallUpdateService|Verifying update package
20-2-2 03:30:49.2|Info|InstallUpdateService|Update package verified successfully
20-2-2 03:30:49.3|Info|InstallUpdateService|Extracting Update package
20-2-2 03:31:24.9|Info|InstallUpdateService|Update package extracted successfully
20-2-2 03:31:26.6|Info|BackupService|Starting Backup
20-2-2 03:32:51.2|Info|InstallUpdateService|Preparing client
20-2-2 03:32:59.9|Info|InstallUpdateService|Starting update client /tmp/sonarr_update/Sonarr.Update.exe
20-2-2 03:32:59.9|Info|InstallUpdateService|Sonarr will restart shortly.
20-2-2 03:33:07.5|Info|SceneMappingService|Updating Scene mappings
20-2-2 03:34:36.5|Info|InstallUpdateService|Deleting old update files
20-2-2 03:34:40.5|Error|CommandExecutor|Error occurred while executing task ApplicationUpdate

[v3.0.3.688] System.IO.IOException: Directory /tmp/sonarr_update/sonarr_backup is not empty

Let me think about this more to try to figure out what might have happened. Look in /tmp/sonarr_update/ to see what you find there and maybe give us the output of ls -la for the items in that directory so that we can see permissions and ownership used there. I am guessing there might be a permissions/ownership issue for some reason...

Interestingly, I see a successful update in your prior logs here:

20-1-22 08:46:35.6|Info|InstallUpdateService|Downloading update 3.0.3.688
20-1-22 08:46:38.2|Info|InstallUpdateService|Verifying update package
20-1-22 08:46:41.2|Info|InstallUpdateService|Update package verified successfully
20-1-22 08:46:41.2|Info|InstallUpdateService|Extracting Update package
20-1-22 08:46:56.1|Info|InstallUpdateService|Update package extracted successfully
20-1-22 08:46:56.3|Info|InstallUpdateService|Branch [develop] is being redirected to [phantom-develop]]
20-1-22 08:47:00.6|Info|BackupService|Starting Backup
20-1-22 08:48:11.2|Info|InstallUpdateService|Preparing client
20-1-22 08:48:15.7|Info|InstallUpdateService|Starting update client /tmp/sonarr_update/Sonarr.Update.exe
20-1-22 08:48:15.8|Info|InstallUpdateService|Sonarr will restart shortly.
20-1-22 08:50:19.8|Info|Bootstrap|Starting Sonarr - /volume1/@appstore/nzbdrone/share/Sonarr/Sonarr.exe - Version 3.0.3.688
20-1-22 08:50:38.4|Info|Router|Application mode: Interactive
20-1-22 08:50:43.4|Info|MigrationLogger|*** Migrating data source=/volume1/@appstore/nzbdrone/var/.config/Sonarr/sonarr.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
20-1-22 08:50:48.6|Info|MigrationLogger|*** Migrating data source=/volume1/@appstore/nzbdrone/var/.config/Sonarr/logs.db;cache size=-10000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
20-1-22 08:50:49.2|Info|OwinHostController|Listening on the following URLs:
20-1-22 08:50:49.2|Info|OwinHostController|  http://*:8989/
20-1-22 08:51:03.2|Info|SonarrBootstrapper|Starting Web Server

[Fogest]

@maxrogers I updated via DSM and it updated quite quickly. Must be related to DB size as I do not have a huge library in Sonarr

[NMe84]

Seems like it. I have a database with over 23k episodes in it and had the same results as @maxrogers had above. It seems to be working fine now but it was a very confusing process.

[Fogest]

Unsure where you found out how many episodes you have, however I only have 78 series in Sonarr and some of them have minimal seasons/episodes.

[Safihre]

@maxrogers Updated the package in the link.

[Fringe09]

I installed the initial v3x package from here and have been updating via the built-in Sonarr updater since. I'm now running v3.0.3.754 which came out yesterday.

I have an update notice in DSM. It's v20200409-16. What Sonarr version does v20200409-16 map to?

Edit: I think the description should be updated to "Updated Sonarr to vX and add workaround for mono bug with armv5/88f6281". The previous package has the Sonarr version number.

[maxrogers]

I have an update notice in DSM. It's v20200409-16. What Sonarr version does v20200409-16 map to?

The v20200409-16 update in DSM is an update to the DSM package (wrapper). It will only upgrade the internal Sonarr executable if it contains a newer version of Sonarr than the one that you currently have installed. If you already have a newer version of the Sonarr installed then it will only upgrade the package (not Sonarr). In your case, since you are on v3, it will only upgrade the package.

[Fringe09]

I have an update notice in DSM. It's v20200409-16. What Sonarr version does v20200409-16 map to?

The v20200409-16 update in DSM is an update to the DSM package (wrapper). It will only upgrade the internal Sonarr executable if it contains a newer version of Sonarr than the one that you currently have installed. If you already have a newer version of the Sonarr installed then it will only upgrade the package (not Sonarr). In your case, since you are on v3, it will only upgrade the package.

Thank you for the explanation. Upgraded Sonarr and Mono without any issues.

[Stanzilla]

@Safihre looks like your packages do not include the typo fix from #3865 (comment)

[epheterson]

Slightly off topic, but Sonarr v3 is so great... Does anybody here know if there's a Radarr v3 package for Synology available (or is anybody here willing to make one for testing)?

I installed the Sonarr package from: #3803

[scottgshin]

I have a DS918+ so apollolake (x64) and am running DSM 6.2.3-25423. The general x64 builds are for 6.1. Is there a build I can install to get v3 of sonarr? Thanks

[Safihre]

The 6.1 ones should work just fine.

[scottgshin]

The 6.1 ones should work just fine.

Thanks @Safihre, V3 looks great!

[RaboonTheBaboon]

Nice work @Safihre

Looking forward to seeing your build on SynoCommunity in due time!

[sick-n-tired]

I am trying to update using your build, but I get an error that I can't downgrade. I have version 20200921-18 from SynoCommunity. How would I be able to update using your build? Thank you for any help.

[Forts117]

I am trying to update using your build, but I get an error that I can't downgrade. I have version 20200921-18 from SynoCommunity. How would I be able to update using your build? Thank you for any help.

I'm having the exact same issue....

[goodlucknow]

@sick-n-tired @Forts117 just take a manual backup, then uninstall the current package, install this build fresh and then restore your backup. this is what worked for me after seeing the same error.

[jsatk]

Any word on when Sonarr v3 will hit SynoCommunity?

[Safihre]

We kind of hoped they would finally release a stable version after so many years.. Then we can switch. Although if we knew it would take so many years, we would have made 2 versions at the beginning.

[jsatk]

Last night I just opted to bite the bullet and roll with an all Docker set up.

[ymartin59]

@Safihre You have all permissions required to review, accept, merge, build and publish packages.
@hgy59 @publicarray @th0ma7 So anyone volonteer to grab #3803 and test/publish it?

[Safihre]

@ymartin59 Just to be sure, we are not waiting anymore for V3 to become stable?
Since the package is renamed , are we keeping the NzbDrone package in the repo?

[tchirou]

My two cents I have used v3 on a docker set up on my ds418play and it is rock solid The tag and multi language features are awesome Le 17 janv. 2021 à 10:20, Safihre <[email protected]> a écrit :  @ymartin59 <https://github.com/ymartin59> Just to be sure, we are not waiting anymore for V3 to become stable? Since the package is renamed , are we keeping the NzbDrone package in the repo? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3443 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTPZ3HOMTNNLFOUGUC5JA3S2KTWZANCNFSM4FTUVSKQ> .

[ymartin59]

@Safihre No idea, I am not a Sonar user. Question is: do we expect users to move "smoothly" from Sonar v2 to Sonar v3 without complex operation to keep their existing configuration/database ? if yes, we should either keep package name as is (and confirm v3 is able to upgrade config/database from v2), or provide a wizard/tooling in Sonar v3 to grab configuration/data from installed v2 on system...
If answer is "we do not care", so a brand new package is an option... maybe with FAQ in wiki to explain how to transfer manually config/data from v2 to v3.

[Fogest]

I think a smooth upgrade is ideal. I was able to use the package provided on here to smoothly upgrade to v3 without losing anything and any future v3 updates Sonarr puts out update no problem right from within the applications own updater without issues.

[maxrogers]

@ymartin59 @Safihre I totally agree with moving to v3. FYI, I just updated the pull request with the latest version of Sonarr.

We previously had a lot of users who upgraded successfully via this package (v2 -> v3 upgrade) and they reported here that it worked properly. The only issue was for people that have large databases the upgrade can time out via the Synology interface. However, it does still complete the upgrade properly. In addition, I previously tested this package thoroughly and it upgraded from v2 to v3 just great. I have been running it for ages now.

That being said, it might be nice to have at least one person test the v2->v3 upgrade via this package because I added the updated sonarr v3.0.4.1091 (just to be sure that doesn't cause any upgrade issues).

NOTE: It has a warning added requesting that users back up their data via Sonarr interface before performing the upgrade as a failsafe.

[ccwillia]

@maxrogers I tried this weekend using nzbdrone_88f6281-6.1_20201116-19.spk for my ds211j. I installed the version of Mono 5.20.1.34-17 available in from synocommunity then the page mentioned above. The service would not start so looked at service-setup and noticed that the workaround that was created for arm5 has 88f8621 and 88f8622 listed in the if condition instead of 88f6281 and 88f6281. After making these modifications i was able to get the service to start. Navigating through the menu i noticed things like fetch updates weren't working as mentioned in this thread by mk2k https://forums.sonarr.tv/t/synology-ds212j-sonarr-failed-to-run-package-service/26172/8

[publicarray]

This was addressed in #3803