Updating Jackett, Radarr, and Sonarr Jails Breaks Them about iocage-plugin-index HOT 5 CLOSED

Seems to be what it is. I checked the version of Mono that Jackett is currently running with (6.8.0.105) and it's working fine. I wonder if I could do a pkg lock and keep this version? Or in the case of Sonarr and Radarr downgrade to the version from https://download.mono-project.com/sources/mono/mono-6.8.0.105.tar.xz? Although I do recall trying this back in June and I had to go back to mono520. Documented in #238. On the freshports page for mono6.8 is says:

If upgrading
* If you have installed any custom CAs using the cert-sync tool, you
must re-install them after upgrading Mono.

Is this the problem?

from iocage-plugin-index.

To my knowledge mono6.8-6.8.0.123 is evil and should be blacklisted. I managed to fix this in all three affected containers by using the package that was in the Jackett jail in /usr/local/migration/bin/mono-6.8.0.105.txz. I believe that you can also find this package here if you do not have a Jackett jail to copy it from. I just copied it some where (doesn't matter) and then mount pointed it into the jails as needed.

The rest was basically:
iocage update JAIL
iocage console JAIL
service PLUGIN stop
pkg lock PLUGIN
pkg install -f mono-6.8.0.105
service PLUGIN start
pkg unlock PLUGIN

I'm wondering about this mono6.8-6.8.0.123, it looks like Mono is unmaintained and the package hasn't been updated in over a year. Also Jackett, Radarr, and Sonarr seem to be it's only users. Maybe it would be a good idea to just pkg lock mono in all affected jails?

Since these three plugins are better suited to be updated through the webGUI would it not be better to just mark the version in the TrueNAS jail console as N/A? Or would this mess with updating the actual jail itself that the plugin runs inside?

Anyways problem solved I'll leave it up to whomever to close this.

from iocage-plugin-index.

@jasker5183 good point about the evil 👿 mono6.8-6.8.0.123 version. I was pretty puzzeled and stuck how this could be quickfixed with the updated and buggy version of mono for the jackett plugin I'm maintainer of.

I think I finally managed to add some (ugly) patches/quickfixes for this to downgrade the mono version to the bundled one (you mentioned), remove the expired certificate from the FreeBSD list of trust and finally run the cert-sync. Looks like it works just fine after that and Jackett can now reach sites with Let's Encrypt certificates again.

For more detail about the Jackett fixes see issue and comment in the Jackett repository here: fulder/iocage-plugin-jackett#4 (comment)

from iocage-plugin-index.

looks related to the following: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258709

from iocage-plugin-index.

When I was looking about what to do about the errors I keep getting in Radarr about them no longer supporting Mono and using .NET in the future a Servarr wiki page linked me to this page. There are instructions on how to build a Radarr jail using the .NET version, was thinking on trying to upgrade my existing jail when I get brave enough. There is also an experimental version of Jackett 0.18.475, besides being an old version would this not be a better option going forward since Mono looks to not be maintained any longer?

I guess Mono is still being maintained, it's just getting small patches to a version that hasn't been updated in a year (come December).

from iocage-plugin-index.