2024-07-29, 03:25 PM
Just the default "bridge" mode. To be fair its only crashed twice in the last 8 months so it's not that big of a deal, just hoping the logs might provide some info for the developers so they can resolve it.
2024-07-29, 03:25 PM
Just the default "bridge" mode. To be fair its only crashed twice in the last 8 months so it's not that big of a deal, just hoping the logs might provide some info for the developers so they can resolve it.
2025-02-19, 12:07 PM
So, same thing happened on 10.10.5 last night, crashing the docker.
There was no transcodes happening at the time, server had tons of free ram/disk space. There was a single client logged on who had got half way through watching a TV show and then paused it, it was in this paused state for a few hours. The TV show had fully transcoded, so that part can be removed from the equation. The logs seem to indicate its the same problem as what happened with my original post. Restarting the docker brings back jellyfin perfectly with no problems. https://text.is/3Z37R
2025-02-19, 02:49 PM
In your case it looks like your server lost network connectivity. Can you share your docker compose? And whether you are using a reverse proxy.
2025-02-19, 05:06 PM
Servers local network is fine, all the other services running at the time reported no errors and no logs on the router to say if the port had any issues or was dropped.
The docker (official) is created by the command line using "docker run -d -p 8096:8096 --name jelly --privileged --group-add="106" --device /dev/dri/renderD128 ![]() ![]() If the server lost connection to the client (uk>usa) then that could give the "no route to host" issue, but it shouldn't be allowed to bring down jellyfin.
2025-02-19, 05:17 PM
Can you try switching to host networking?
2025-02-19, 05:36 PM
I'll give it a shot next time i update the docker. The big problem with troubleshooting this, is it only happens once every 3-4 months.
|
|
|