Jellyfin Instability and Crashes

[TheDreadPirate]

Jul 23 20:56:35 Home kernel: br-094fb560e9be: port 2(vethf8ad51c) entered disabled state
Jul 23 20:56:35 Home kernel: veth087d5af: renamed from eth0
Jul 23 20:56:35 Home kernel: br-094fb560e9be: port 2(vethf8ad51c) entered disabled state
Jul 23 20:56:35 Home kernel: device vethf8ad51c left promiscuous mode
Jul 23 20:56:35 Home kernel: br-094fb560e9be: port 2(vethf8ad51c) entered disabled state
Jul 23 20:56:35 Home kernel: br-094fb560e9be: port 2(vethdfe6ef4) entered blocking state
Jul 23 20:56:35 Home kernel: br-094fb560e9be: port 2(vethdfe6ef4) entered disabled state
Jul 23 20:56:35 Home kernel: device vethdfe6ef4 entered promiscuous mode
Jul 23 20:56:35 Home kernel: br-094fb560e9be: port 2(vethdfe6ef4) entered blocking state
Jul 23 20:56:35 Home kernel: br-094fb560e9be: port 2(vethdfe6ef4) entered forwarding state
Jul 23 20:56:36 Home kernel: br-094fb560e9be: port 2(vethdfe6ef4) entered disabled state
Jul 23 20:56:37 Home kernel: eth0: renamed from veth9dfe8aa
Jul 23 20:56:37 Home kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethdfe6ef4: link becomes ready
Jul 23 20:56:37 Home kernel: br-094fb560e9be: port 2(vethdfe6ef4) entered blocking state
Jul 23 20:56:37 Home kernel: br-094fb560e9be: port 2(vethdfe6ef4) entered forwarding state

The time stamps for this message lines up with the last crash/restart. And nearly every time these messages appear correlates to the Jellyfin container restarting seconds later earlier in the day.

Jellyfin didn't restart every time these messages appeared. But every time Jellyfin restarted these messages happened seconds earlier.