+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Logs spammed with the same Error (/t-solved-logs-spammed-with-the-same-error)
Pages:
1
2
RE: Logs spammed with the same Error - TheDreadPirate - 2025-01-10
Has anything changed today? The messages appear to have started after it initiated a transcode, but the input is from a web URL?
RE: Logs spammed with the same Error - arc. - 2025-01-10
That's interesting. A few weeks ago I tried to add internet radio to Jellyfin. I'll try to remove them and see if that sorts it.
RE: Logs spammed with the same Error - arc. - 2025-01-11
I have removed the web radios, but the error is still being printed in the logs.
I removed the radios by
- removing the tuner device
- deleting any .m3u files referring to a webstream
- rescanning the library which contained the .m3u file
- restarting Jellyfin
EDIT: I realised Jellyfin hands transcoding off to ffmpeg, which is unaffected by a Jellyfin restart. So to make it easy for myself I just restarted the entire Synology server and now the issue is resolved!
TLDR; Issue was caused by previous attempts to add internet radio streams. Removed these and restarted the entire device hosting Jellyfin and ffmpeg.