Open jr253 opened 2 weeks ago
jellyfin-bot
commented
2 weeks ago Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
SnX85
commented
2 weeks ago I have exactly the same issue! Clean install Ubuntu Server 24.04, JellyFin 10.9.1 and 10.9.2 produce the same problem (not using containers or virtualisation). JellyFin 10.8 on Ubuntu Server 23.10 using the same library folders worked fine. For me oom kills the process ffprobe for eating up all 32gb ram when scanning the library. As shown image below 1.9gb ram usage before library scan and when scanning you see it going up until oom kills the process.
Changing Limit concurrent library scanning tasks and Limit simultaneous image encodings from 0 (let JellyFin decide) to something else stops oom killing the process but scanning library still hangs. Turned on debug logging (see attachment). Hope it helps both problems. Log.txt
devpatf
commented
1 week ago Many seem to have issues with locked database. See #11608 #11589 #11638
Hunter-Clipper
commented
1 week ago I am also having this issue, I can dump my logs if needed.
MoonOverMiami
commented
1 week ago Same. Scan and Search for missing data both hang. Only the first few hundred get set up then it just stops. 10.9.2 is rough. Please release a fix.
jcaust
commented
1 week ago how does this keep getting worse ! ever since the change from channel name human readable to channel id it's been downhill . ive wasted hours renaming channels in metadata . and now using jf plugin for tubearchivist , it doesn't even work! the docs to setup for Synology doesn't make sense and if you follow others guides they are all different . seriously , if one is using Synology docker, you would think there is an install that just works.
soakes
commented
1 week ago Hi @jr253, I am experencing the exact same issue on 10.9.2 using a fresh install with a k8s deploymnet.
This restarted 5+ times while scanning large(ish) library, infact it never finishes, just keeps restarting.
I have now reverted back to 10.8.13, zero issues with same library, sucessfully scanned and no restarts.
I suspect its the same issue, db's getting busy and causing lock ups like 10.9.1 was as you can make it do it even more if you add in some additional plugins like subtitles, it will fallover quicker.
10.9.2
10.8.13
MoonOverMiami
commented
1 week ago Is the process to downgrade simply deleting the 10.9.2 container then finding 10.8.13 (where?) and installing it?
soakes
commented
1 week ago Is the process to downgrade simply deleting the 10.9.2 container then finding 10.8.13 (where?) and installing it?
Unfortunately no, the db etc gets upgraded and is not compatiable with previous versions.
A clean install is whats required, or grabbing a copy of 10.8.13 db etc before your upgrade (assuming you upgraded), then you would just need the older version on top.
MoonOverMiami
commented
1 week ago So how are all the users who have issues with 10.9.2 getting 10.8.13 to work? Pardon my ignorance.
On Sat, May 25, 2024, 3:41 PM Simon Oakes @.***> wrote:
Is the process to downgrade simply deleting the 10.9.2 container then finding 10.8.13 (where?) and installing it?
Unfortunately no, the db etc gets upgraded and is not compatiable with previous versions.
A clean install is whats required, or grabbing a copy of 10.8.13 db etc before your upgrade (assuming you upgraded).
— Reply to this email directly, view it on GitHub https://github.com/jellyfin/jellyfin/issues/11728#issuecomment-2131434256, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4YHONMOTGRF5XXYY7VIGADZEDZPHAVCNFSM6AAAAABH55MMRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGQZTIMRVGY . You are receiving this because you commented.Message ID: @.***>
soakes
commented
1 week ago @MoonOverMiami in my case, I am just changing the version number in my manifest as the linuxserver.io jellyfin docker image has the previous versions available. I still have had to rebuild all the jellyfin data/configs (hence fresh/clean install).
However on another machine (non k8s) which im moving bits from, to my new k8s clusters. I used a previous backup of 10.8.13 when I had to revert back after I upgraded to 10.9.1. As this version was "quite" broken and time to find the issue as well as for the devs to fix it, I had to revert back to 10.8.13 until 10.9.2 come out. For this, I restored an old VM which had 10.8.13 installed.
I have since upgraded to 10.9.2 but still having issues, not half as bad, but still crashing quite oftern. This is why ive now decided to rebuild 10.8.13 from scratch and will stay on that for a few more versions in 10.9.x comes out so the bugs can be squshed before moving over.
MoonOverMiami
commented
1 week ago Is the process to downgrade simply deleting the 10.9.2 container then finding 10.8.13 (where?) and installing it?
Unfortunately no, the db etc gets upgraded and is not compatiable with previous versions.
A clean install is whats required, or grabbing a copy of 10.8.13 db etc before your upgrade (assuming you upgraded), then you would just need the older version on top.
Sorry, wasn't clear. That's what I meant. A clean install. If I delete the 10.9.2 Jellyfin container I assumed all the data would be deleted including the db.
Where is the previous version repository?
soakes
commented
6 days ago Sorry, wasn't clear. That's what I meant. A clean install. If I delete the 10.9.2 Jellyfin container I assumed all the data would be deleted including the db.
Depends how you have it setup, but typiclaly you have persistent volumes for the db/config, so deleting the container would not touch your db/data/configs etc, only the application/os/container itself.
Where is the previous version repository?
It doesn't exist, you need to build it from source, all the files are in the main git repo. However, if your using docker, you have a couple options:
docker pull linuxserver/jellyfin:10.8.13
docker pull jellyfin/jellyfin:10.8.13
lxne
commented
5 days ago I am not entirely sure, but Jellyfin seems to have issues with some special characters in folder and file names since 10.9.x (e.g. '&' or '–', not '-'). In my case, If a folder contains any of those, it won't show up. Or if a file in a folder contains any, the folder shows up as empty, even when there are other files without those special characters.
MoonOverMiami
commented
5 days ago Where are the 'persistent volumes' located and how do I delete them to nuke my JF and install 10.8.13? I'm done with this update. Just want Jellyfin to work.
lxne
commented
4 days ago I am not entirely sure, but Jellyfin seems to have issues with some special characters in folder and file names since 10.9.x (e.g. '&' or '–', not '-'). In my case, If a folder contains any of those, it won't show up. Or if a file in a folder contains any, the folder shows up as empty, even when there are other files without those special characters.
I've found a solution for this. For me, an env variable persisted that should not be there in 10.9.x https://forum.jellyfin.org/t-solved-issues-with-special-charakters-since-update
Please describe your bug
I just started with Jellyfin last weekend. This issue has been occurring on 10.9.1 and now 10.9.2. I did a clean install of 10.8.9 and it does not exhibit the problem. I simply install jellyfin in Container Manager following the instructions from Jellyfin. I go to ip address:8096 and follow the setup wizard. I add a library. Jellyfin starts scanning the library and eventually fails. I have tried this several times from a totally clean install. Tried to work through the issue on the Troubleshooting section of the forum and was recommended to post an issue here. The troubleshooting thread is here: https://forum.jellyfin.org/t-playback-error-on-every-video I had to cut out a chunk of the log to fit it here, but the entire thing is on the forum.
Reproduction Steps
Jellyfin Version
10.9.0
if other:
10.9.2
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct