SOLVED: Jellyfin upgrade issue

[Abhishek Ranjan]

Hi folks,
I keep running into this issue every time jellyfin does a new release.
My jellyfin is setup as a lxc using proxmox helper scripts.

Code:

root@jellyfin:~# sudo apt upgrade jellyfin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
jellyfin is already the newest version (10.10.2+deb12).
Calculating upgrade... Done
The following packages will be upgraded:
  jellyfin-server
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
29 not fully installed or removed.
Need to get 0 B/46.8 MB of archives.
After this operation, 22.5 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 24588 files and directories currently installed.)
Preparing to unpack .../jellyfin-server_10.10.2+deb12_amd64.deb ...
Stopping Jellyfin!
mv: cannot move '/var/lib/jellyfin/config' to '/etc/jellyfin/config': Directory not empty
dpkg: error processing archive /var/cache/apt/archives/jellyfin-server_10.10.2+deb12_amd64.deb (--unpack):
new jellyfin-server package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/jellyfin-server_10.10.2+deb12_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've been solving it so far by backing up my config directory, deleting it and then restoring the files after the upgrade.
Is there a better way to do the upgrades ?

[TheDreadPirate]

/var/lib/jellyfin/config and /etc/jellyfin/config aren't part of the standard Jellyfin directory structure. I am assuming they are not owned by Jellyfin. Regardless, they should not be present in either directory.

[Oddstr13]

It would be this block of code, presumably part of an old migration?
https://github.com/jellyfin/jellyfin-pac...st#L57-L60


sudo mv /var/lib/jellyfin/config{,~old} should be safe, and fix the issue. (moves config to config~old)

[Pollo]

I'm not sure if this is an issue or not, but after upgrading the web and build versions are still 10.10.1.

Right as I was typing this I ran the "jellyfin --help" command and it seemed to fix the issue. I'm not sure if this method is recommended, but this might be a 1 in a million situation for all I know.

[guunter]

Hi folks,
I keep running into this issue every time jellyfin does a new release.
My jellyfin is setup as a lxc using proxmox helper scripts.

Code:

root@jellyfin:~# sudo apt upgrade jellyfin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
jellyfin is already the newest version (10.10.2+deb12).
Calculating upgrade... Done
The following packages will be upgraded:
  jellyfin-server
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
29 not fully installed or removed.
Need to get 0 B/46.8 MB of archives.
After this operation, 22.5 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 24588 files and directories currently installed.)
Preparing to unpack .../jellyfin-server_10.10.2+deb12_amd64.deb ...
Stopping Jellyfin!
mv: cannot move '/var/lib/jellyfin/config' to '/etc/jellyfin/config': Directory not empty
dpkg: error processing archive /var/cache/apt/archives/jellyfin-server_10.10.2+deb12_amd64.deb (--unpack):
new jellyfin-server package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/jellyfin-server_10.10.2+deb12_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've been solving it so far by backing up my config directory, deleting it and then restoring the files after the upgrade.
Is there a better way to do the upgrades ?

When you use the helper-script you're supposed to just type update in console. You don't need to do sudo apt-get upgrade

[Abhishek Ranjan]

It would be this block of code, presumably part of an old migration?
https://github.com/jellyfin/jellyfin-pac...st#L57-L60


sudo mv /var/lib/jellyfin/config{,~old} should be safe, and fix the issue. (moves config to config~old)

Thank you for digging this in code.
So I had this jellyfin set up as a docker container before, and now it's in a LXC. When I moved it,I tried to keep the directories same as before.
It seems like even if you put all the directories as config variables properly, there are still hardcoded paths stored in the sqlite db, so had to manually fix those.

Since then, I've been running this as is. If someone can help me move this to a more standard configuration, I'd be happy to do it to avoid this problem every time i update.

[TheDreadPirate]

I'm assuming /etc/jellyfin/config and /var/lib/jellyfin/config are now empty. Since they aren't used in a non-Docker setup, you need to move them out of their respective directories.

[Abhishek Ranjan]

I'm assuming /etc/jellyfin/config and /var/lib/jellyfin/config are now empty.  Since they aren't used in a non-Docker setup, you need to move them out of their respective directories.

I think since I moved from docker to jellyfin web and tried to keep the config, the paths might have followed me to here. What are the standard jelly fin config and other paths ?

[TheDreadPirate]

Data directory - /var/lib/jellyfin
Config directory - /etc/jellyfin
Cache directory - /var/cache/jellyfin

If you simply removed or relocated /var/lib/jellyfin/config and /etc/jellyfin/config, the upgrade should succeed.

[Abhishek Ranjan]

Data directory - /var/lib/jellyfin
Config directory - /etc/jellyfin
Cache directory - /var/cache/jellyfin

If you simply removed or relocated /var/lib/jellyfin/config and /etc/jellyfin/config, the upgrade should succeed.

Thanks, I did these. Are there any sure shot ways to check by doing a upgrade ? I'm already on the latest. I did a sudo apt install --reinstall jellyfin-server and that worked well.