2023-09-18, 05:05 AM
The first error message is unrelated, most likely. It's a slow HTTP response message that plagues all users who don't disable it.
The other errors are cryptic at best without more context. You'd have to provide more than scraps of the logs for us to take a look at. The first one just says a session Jellyfin expected to find when it was checking playback status was not present so it threw an error. The ffmpeg log looks...fine? It's opening the playlist file and the ts file at the same time which makes sense. It slows to a crawl near the end, gets an exit command from somewhere, then stops. Couldn't this be an issue with running out of disk space in your transcode directory? Or if you're using a RAMdisk, could you have allocated too little for that to be effective? I'm not sure how often the transcode directory is cleaned when viewing Live TV. Again more logs would be needed to do anything effective.
And a favor? Don't change your font to black...if anybody uses dark mode it makes things impossible to read.
The other errors are cryptic at best without more context. You'd have to provide more than scraps of the logs for us to take a look at. The first one just says a session Jellyfin expected to find when it was checking playback status was not present so it threw an error. The ffmpeg log looks...fine? It's opening the playlist file and the ts file at the same time which makes sense. It slows to a crawl near the end, gets an exit command from somewhere, then stops. Couldn't this be an issue with running out of disk space in your transcode directory? Or if you're using a RAMdisk, could you have allocated too little for that to be effective? I'm not sure how often the transcode directory is cleaned when viewing Live TV. Again more logs would be needed to do anything effective.
And a favor? Don't change your font to black...if anybody uses dark mode it makes things impossible to read.
Jellyfin 10.10.5 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage