Emby service stopping/crashing

Troubleshooting
1

Hi Guys,

Recently had some trouble with diepi 6.16 running on an rpi3 where sickrage nuked itself with an update and was unrecoverable. I rebuilt it all and Emby that was working fine previously now crashes around about every 12 hours requiring either a reboot or a manual service start. Anyone come across this before?

I did suspect sonarr’s emby connection might have been causing that but I removed that connection and it still happens. I’ve just turned on committing logfiles to disk hoping to chase down the problem

Side note, Emby chromecast media from the RPI is unwatchable with constant freezing but works fine over DLNA

2

I’ve run Emby on XU4 and Z83 devices and on the whole very stable. I take it you have done a fresh install? If not maybe worth doing so with a new SD card?

John

3

yeyeyeye
Sickrage issue is known: https://github.com/Fourdee/DietPi/issues/2126

  • Regardless of DietPi version it will fail, due to many SiCKRAGE internal changes.
  • The problem is fixed with v6.17, but sadly too much changes to reliably apply all of them manually to v6.16, I guess :.

On which DietPi version you face the emby issues? If you can, check logs especially for permission issues, since this are the most obvious changes we did with the last updates.

If you want, test it on current beta, just release for public testing: https://github.com/Fourdee/DietPi/issues/2140

4

I replaced sickrage with Sonarr + jackett which has been good so far, I still can’t narrow down my issue with emby

The below error is coming up many times in emby’s own logs

Error Dlna: Error in BeginListeningForBroadcasts
	*** Error Report ***
	Version: 3.5.2.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_armhf.deb
	Operating system: Unix 4.14.71.7
	64-Bit OS: False
	64-Bit Process: False
	User Interactive: True
	Processor count: 4
	Program data path: /var/lib/emby
	Application directory: /opt/emby-server/system
	System.Net.Sockets.SocketException (98): Address already in use
	   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
	   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
	   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
	   at Emby.Server.Implementations.Net.UdpSocket..ctor(Socket socket, Int32 localPort, IPAddress ip)
	   at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket(String ipAddress, Int32 multicastTimeToLive, Int32 localPort)
	   at Rssdp.Infrastructure.SsdpCommunicationsServer.ListenForBroadcastsAsync()
	   at Rssdp.Infrastructure.SsdpCommunicationsServer.BeginListeningForBroadcasts()
	System.Net.Sockets.SocketException
	   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
	   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
	   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
	   at Emby.Server.Implementations.Net.UdpSocket..ctor(Socket socket, Int32 localPort, IPAddress ip)
	   at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket(String ipAddress, Int32 multicastTimeToLive, Int32 localPort)
	   at Rssdp.Infrastructure.SsdpCommunicationsServer.ListenForBroadcastsAsync()
	   at Rssdp.Infrastructure.SsdpCommunicationsServer.BeginListeningForBroadcasts()

Perhaps ‘auto update’ attempts are making the service die

5

Have you tried the Emby forum?

John