Lidarr Jail Issue

Apps and Virtualization
1

I’m currently running Core 13.0-U6.2.

I have a jail running the previous version of Lidarr (2.3.3.4204) which has been upgraded via pkg upgrade many times without issue. For context, my config and database are stored outside the jail, and referenced via mount point.

However, when I try to upgrade to 2.4.3.4248 via pkg upgrade and restart the server, the application doesn’t appear. Instead, I get a browser message “Unable to Connect”.

I tried creating a new jail from scratch with the latest version of Lidarr without adding the mount point to my config / data, and this starts with no issue but obviously with a blank database. If I stop the application, add the mount point to the directory where my settings are stored, then restart the application, I get the same “Unable to Connect” message. I’ve also tried removing the mount point and copying the database file from the outside storage directly to the application config directory, overriding the blank database Lidarr created, I get the same “Unable to Connect” message.

Both the existing 2.3 version and the new 2.4 version are running the same version of sqlite3 (3.46) so I don’t think it’s database engine mismatch.

It almost feels like corrupt data, but the db is read correctly in the old version.

I’ve gone through the logs and nothing jumps out at me as to the source of the problem.

I’ve also run pkg info on both jails and everything matches except the version of lidarr. Both jails are running version 13.2-RELEASE-p11.

Has anyone run into something similar or have an idea of what’s going on?

Thanks

2

The highest fully supported jails (13.2) under TrueNAS Core 13.0-U6.2 are EOL.

You need to upgrade to TrueNAS Core 13.3-RELEASE, and use jails (and packages) based on FreeBSD 13.3+.

3

If that is the case, why would it work with a blank database, but crash when I try to use the existing database?

4

Have you checked their forums (if they have any) for any release notes about compatability and so forth?

I know nextcloud broke a while ago for a few people because mariadb updated the path to the socket, and the config file for nextcloud had to also be updated to reflect that.

5

I’ve checked a few places and haven’t found anything that looks like this issue. I’ll retry a new install when TN 13.3 is released

6

TrueNAS CORE 13.3-RELEASE is Now Available

7

Ok, thanks.

It’s not showing up as an available update in the dashboard