Spksrc: [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

[scrytch]

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

[Stanzilla]

Sadly I cleared everything out when I reinstalled Sonarr (because of Mono) yesterday :(

[maxrogers]

@Stanzilla hmmm, roger that. Still good info, thx!

I will try to think of anything that relates to the synocommunity package that might have caused leftover data or permissions issues in /tmp/sonarr_update/

[sirjaymz]

Are we going to get this added as a pull request and get the sonarr/nzbdrone installation pkg updated?

EDIT - Been working perfectly. Been updating the app via the internal app-update functioning.. currently updated to ...
Version
3.0.3.741
Mono Version
5.18.0.240

[Fogest]

I have done the same as @sirjaymz and manually installed via the packages provided from @Safihre above. I have updated Sonarr V3 internally and also have it up to the same Sonarr version. My Mono version also matches.

Is there a reason this build is not pushed to the main sonarr update? It seems as though Sonarr suggests using v3 even though it's a beta.

[Safihre]

They suggest using v3, but it's still not official. The bulk of their users is still on v2.. (aka the regular Windows users that don't touch their automation setups). When they feel comfortable making v3 official, then so shall we 🥇

[NMe84]

In the mean time running the update for the package that was pushed recently (this week?) completely broke my setup. And just installing the package linked above again is not going to work either...

Current package version is 20200409-16. You cannot downgrade it to the older version 20191122-16.

What do I do to get Sonarr running again?

Edit: after several attempts at starting and restarting the software it suddenly worked again... Should I not be updating the package as long as it's not pushed officially?

[maxrogers]

@NMe84 typically when running a beta package via a manual install (like this one) you would want to wait for this package to be updated here rather than installing the prompted update in DSM Package Center. However, the v2 package in DSM Package Center (synocommunity repo) was updated for v3 compatibility and therefore should theoretically work. It sounds like it did in your case (eventually).

Out of curiosity, I attempted the same update (v2 package update via Package Center). Mine began the update and after a little while prompted that the update had failed. Package center then seemed to be in a strange state for several minutes as the Sonarr package showed a greyed out "updating" button where the install or upgrade button usually is. A minute or so later Sonarr was then “running” and it had updated properly.

I think in my case, because of a large database and long processing time to copy it back and forth from /tmp during the upgrade process, Package Center had timed out (perhaps due to a limit on how long an upgrade can take)... After accepting the error message, I was then left with the strange greyed-out "install" button I mentioned. Once the upgrade process completed entirely, my install was in fact upgraded and running properly again.

In other words, I also upgraded successfully via the v2 upgrade prompt in DSM. However, there was a confusing failed error message and a suspicious delay before it began running properly again. After the update showed up as running my Sonarr was still on v3 as expected and as it was before the package upgrade.

@Safihre I have updated the beta v3 PR to include the mono fixes included in the recent v2 update Would you mind building/updating/replacing the v3 beta packages you posted previously when you have a moment?

EDIT: Out of curiosity I just performed the update again via my new v3 beta package and the same thing happened (long upgrade, claims failure, button then shows up as "updating", a couple minutes later it is running and the upgrade is complete). So it sounds like it doesn't matter which update method is used to upgrade they will face the same cosmetic issue (perhaps only if they have a large database?)

Now my theory is that whenever Sonarr is upgraded and also has a large database that needs migration (version upgrade of sonarr executable) that a standard upgrade process times out while waiting for Sonarr to complete that? However, I am not sure that makes sense either because I would think that the package center would only need to see a running PID and I assume that would exist before sonarr upgrades it's database... I will have to research further

Perhaps more likely is that the mv command during the upgrade process (performed twice) is quite slow when there exists a large sonarr database (thus resulting in a timeout in package center while upgrading). However, I assume that mv would be quite quick or nearly instant (at least much faster than cp which is not used).

UPDATE: It seems it is a result of a large database being moved twice via ‘mv’ as part of the upgrade process. I manually did the mv commands on my library and the first move was quite quick but the move back took over a minute to complete. I don’t know that there is a good solution to this issue. Does anyone know if you can increase the package manager upgrade timeout?

[Fogest]

Okay just to clarify what should I be doing here? Should I be updating using via the DSM Package Center or should I wait for the updated PR from @maxrogers ?

[maxrogers]

@Fogest, I recommend waiting for an updated v3 package.

If you go the other route, I recommend first downloading a backup via the sonarr web-interface (just in case).

[maxrogers]

@Fogest see my edit/update above

[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 https://github.com/SynoCommunity/spksrc/pull/3865#issuecomment-607104044

[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: https://github.com/SynoCommunity/spksrc/pull/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!

[QuestionableBaboon]

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....

[killthewiseone]

@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.