Emby suddenly stop on unraid

[Przemek 70]

Hello, today at 13:16 my Emby server on unraid (docker) suddenly stop working. Other docker services work normal. Meybe someone will help me understand what happen.
Here is syslog from unraid:
 

Oct  5 12:30:19 unRAID emhttpd: spinning down /dev/sdf
Oct  5 13:15:05 unRAID kernel: veth1ce013d: renamed from eth0
Oct  5 13:15:05 unRAID kernel: docker0: port 17(veth0b1eb78) entered disabled state
Oct  5 13:15:06 unRAID kernel: docker0: port 17(veth0b1eb78) entered disabled state
Oct  5 13:15:06 unRAID kernel: device veth0b1eb78 left promiscuous mode
Oct  5 13:15:06 unRAID kernel: docker0: port 17(veth0b1eb78) entered disabled state
Oct  5 13:15:10 unRAID kernel: docker0: port 17(vethba71f46) entered blocking state
Oct  5 13:15:10 unRAID kernel: docker0: port 17(vethba71f46) entered disabled state
Oct  5 13:15:10 unRAID kernel: device vethba71f46 entered promiscuous mode
Oct  5 13:15:16 unRAID kernel: eth0: renamed from vethb044f3b
Oct  5 13:15:16 unRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethba71f46: link becomes ready
Oct  5 13:15:16 unRAID kernel: docker0: port 17(vethba71f46) entered blocking state
Oct  5 13:15:16 unRAID kernel: docker0: port 17(vethba71f46) entered forwarding state
Oct  5 13:16:02 unRAID kernel: docker0: port 3(veth099f601) entered disabled state
Oct  5 13:16:02 unRAID kernel: veth8cacb11: renamed from eth0
Oct  5 13:16:04 unRAID kernel: docker0: port 3(veth099f601) entered disabled state
Oct  5 13:16:04 unRAID kernel: device veth099f601 left promiscuous mode
Oct  5 13:16:04 unRAID kernel: docker0: port 3(veth099f601) entered disabled state
Oct  5 13:16:08 unRAID kernel: docker0: port 3(vethb29c169) entered blocking state
Oct  5 13:16:08 unRAID kernel: docker0: port 3(vethb29c169) entered disabled state
Oct  5 13:16:08 unRAID kernel: device vethb29c169 entered promiscuous mode
Oct  5 13:16:14 unRAID kernel: eth0: renamed from vethb9fd7fa
Oct  5 13:16:14 unRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb29c169: link becomes ready
Oct  5 13:16:14 unRAID kernel: docker0: port 3(vethb29c169) entered blocking state
Oct  5 13:16:14 unRAID kernel: docker0: port 3(vethb29c169) entered forwarding state
Oct  5 13:16:28 unRAID kernel: vethe666b0d: renamed from eth0
Oct  5 13:16:28 unRAID kernel: docker0: port 28(vethf85e5c7) entered disabled state
Oct  5 13:16:29 unRAID kernel: docker0: port 28(vethf85e5c7) entered disabled state
Oct  5 13:16:29 unRAID kernel: device vethf85e5c7 left promiscuous mode
Oct  5 13:16:29 unRAID kernel: docker0: port 28(vethf85e5c7) entered disabled state
Oct  5 13:16:32 unRAID kernel: docker0: port 28(vethed4e27c) entered blocking state
Oct  5 13:16:32 unRAID kernel: docker0: port 28(vethed4e27c) entered disabled state
Oct  5 13:16:32 unRAID kernel: device vethed4e27c entered promiscuous mode
Oct  5 13:16:38 unRAID kernel: eth0: renamed from veth3676e50
Oct  5 13:16:38 unRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethed4e27c: link becomes ready
Oct  5 13:16:38 unRAID kernel: docker0: port 28(vethed4e27c) entered blocking state
Oct  5 13:16:38 unRAID kernel: docker0: port 28(vethed4e27c) entered forwarding state
Oct  5 13:21:14 unRAID webGUI: Successful login user root from 12.253.22.134

 

embyserver-63832109021.txt

Edited October 5, 2023 by Przemek

[Luke 42078]

HI, please try removing these plugins:

	CoverArt 4.1.20.0
	Email Notifications 3.1.6.0
	Episode Refresh 1.0.0.1
	Playback Reporting 2.0.0.5
	Statistics 3.0.10.0

Then restart the server and let us know if it happens again. Thanks.

[Przemek 70]

2 hours ago, Luke said:

HI, please try removing these plugins:

	CoverArt 4.1.20.0
	Email Notifications 3.1.6.0
	Episode Refresh 1.0.0.1
	Playback Reporting 2.0.0.5
	Statistics 3.0.10.0

Then restart the server and let us know if it happens again. Thanks.

I will, try that. Thanks.