![]() |
SOLVED: Jellyfin upgrade issue - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: SOLVED: Jellyfin upgrade issue (/t-solved-jellyfin-upgrade-issue) Pages:
1
2
|
Jellyfin upgrade issue - Abhishek Ranjan - 2024-11-17 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 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 ? RE: Jellyfin upgrade issue - TheDreadPirate - 2024-11-17 /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. RE: Jellyfin upgrade issue - Oddstr13 - 2024-11-17 It would be this block of code, presumably part of an old migration? https://github.com/jellyfin/jellyfin-packaging/blame/878d8e1d7f701393331cb5097fe93c8bbcb921bf/debian/jellyfin-server.preinst#L57-L60 sudo mv /var/lib/jellyfin/config{,~old} should be safe, and fix the issue. (moves config to config~old)
RE: Jellyfin upgrade issue - Pollo - 2024-11-18 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. RE: Jellyfin upgrade issue - guunter - 2024-11-18 (2024-11-17, 12:11 PM)Abhishek Ranjan Wrote: Hi folks, 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 RE: Jellyfin upgrade issue - Abhishek Ranjan - 2024-11-18 (2024-11-17, 11:04 PM)Oddstr13 Wrote: It would be this block of code, presumably part of an old migration?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. RE: Jellyfin upgrade issue - TheDreadPirate - 2024-11-18 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. RE: Jellyfin upgrade issue - Abhishek Ranjan - 2025-02-07 (2024-11-18, 08:36 PM)TheDreadPirate Wrote: 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 ? RE: Jellyfin upgrade issue - TheDreadPirate - 2025-02-07 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. RE: Jellyfin upgrade issue - Abhishek Ranjan - 2025-02-09 (2025-02-07, 07:50 PM)TheDreadPirate Wrote: Data directory - /var/lib/jellyfin 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.
|