Jump to content

Since 4.6.4.0 my emby server crash every days


Recommended Posts

Posted

Hi all, since the last update, I need to restart emby-server every day. I don't understand what is happening.

I have logs without debug and with debug and I don't understand the cause. Everything is fine in the log until something happend and here is the something :

Without debug :

2021-09-04 04:18:14.883 Error App: ArgumentException parsing message
        *** Error Report ***
        Version: 4.6.4.0
        Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
        Operating system: Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-2 (2021-06-21)
        Framework: .NET Core 3.1.13
        OS/Process: x64/x64
        Runtime: opt/emby-server/system/System.Private.CoreLib.dll
        Processor count: 4
        Data path: /var/lib/emby
        Application path: /opt/emby-server/system
        System.ArgumentException: System.ArgumentException: Status line is invalid. Insufficient status parts. (Parameter 'data')
           at Rssdp.HttpRequestParser.ParseStatusLine(ReadOnlySpan`1 data, HttpRequestMessage message)
           at Rssdp.HttpParserBase`1.Parse(T message, HttpHeaders headers, ReadOnlySpan`1 data)
           at Rssdp.HttpRequestParser.Parse(ReadOnlySpan`1 data)
           at Rssdp.SsdpCommunicationsServer.ProcessMessage(ReadOnlySpan`1 data, IPEndPoint remoteEndpoint, IPAddress receivedOnLocalIpAddress)
        Source: RSSDP
        TargetSite: Void ParseStatusLine(System.ReadOnlySpan`1[System.Char], System.Net.Http.HttpRequestMessage)

2021-09-04 04:18:14.892 Error App: FormatException parsing message
        *** Error Report ***
        Version: 4.6.4.0
        Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
        Operating system: Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-2 (2021-06-21)
        Framework: .NET Core 3.1.13
        OS/Process: x64/x64
        Runtime: opt/emby-server/system/System.Private.CoreLib.dll
        Processor count: 4
        Data path: /var/lib/emby
        Application path: /opt/emby-server/system
        System.FormatException: System.FormatException: The format of the HTTP method is invalid.
           at System.Net.Http.HttpMethod..ctor(String method)
           at Rssdp.HttpRequestParser.ParseStatusLine(ReadOnlySpan`1 data, HttpRequestMessage message)
           at Rssdp.HttpParserBase`1.Parse(T message, HttpHeaders headers, ReadOnlySpan`1 data)
           at Rssdp.HttpRequestParser.Parse(ReadOnlySpan`1 data)
           at Rssdp.SsdpCommunicationsServer.ProcessMessage(ReadOnlySpan`1 data, IPEndPoint remoteEndpoint, IPAddress receivedOnLocalIpAddress)
        Source: System.Net.Http
        TargetSite: Void .ctor(System.String)

 

 

 

 

With Debug :

 

2021-09-08 02:44:23.251 Error App: Error sending socket message from 0.0.0.0:1900 to 77.232.107.61:0
        *** Error Report ***
        Version: 4.6.4.0
        Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
        Operating system: Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-2 (2021-06-21)
        Framework: .NET Core 3.1.13
        OS/Process: x64/x64
        Runtime: opt/emby-server/system/System.Private.CoreLib.dll
        Processor count: 4
        Data path: /var/lib/emby
        Application path: /opt/emby-server/system
        System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (22): Invalid argument
           at Rssdp.SsdpCommunicationsServer.SendFromSocket(Tuple`3 socketTuple, Memory`1 messageData, IPEndPoint destination, CancellationToken cancellationToken)
        Source: System.Private.CoreLib
        TargetSite: Void Throw()

 

I already rebuilt the library.db file with things in this post, nothing changed => https://support.emby.media/support/solutions/articles/44002210894-corrupt-database

Do you have any ideas ?

Thanks in advance

 

Posted (edited)

My emby server just crashed again, without any logs this time... I don't understand what's happening...

 

it ends with :

2021-09-08 12:53:17.350 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml. UserAgent: Linux/4.19.0-5-amd64 UPnP/1.0 Cling/2.0
2021-09-08 12:53:17.367 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml. UserAgent: PlexMediaServer/1.24.1.4931-1a38e63c6
2021-09-08 12:53:17.489 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml. UserAgent: PlexMediaServer/1.24.1.4931-1a38e63c6
2021-09-08 12:53:17.590 Debug Server: http/1.1 Response 403 to 109.238.14.84. Time: 250ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml
2021-09-08 12:53:17.590 Debug Server: http/1.1 Response 403 to 109.238.14.60. Time: 340ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml
2021-09-08 12:53:37.828 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml. UserAgent: DAFUPnP
2021-09-08 12:53:38.165 Debug Dlna: Using default profile for: Accept=*/*, Accept-Encoding=gzip, Host=XXX.XXX.XXX.XXX:8096, User-Agent=PlexMediaServer/1.24.1.4931-1a38e63c6
2021-09-08 12:53:38.165 Debug Dlna: Using default profile for: Cache-Control=no-cache, Connection=Keep-Alive, Pragma=no-cache, Accept=text/xml, application/xml, Host=XXX.XXX.XXX.XXX:8096, User-Agent=DAFUPnP
2021-09-08 12:53:38.455 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml. UserAgent: PlexMediaServer/1.24.1.4931-1a38e63c6
2021-09-08 12:53:38.455 Debug Server: http/1.1 Response 403 to 109.238.14.146. Time: 0ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml
2021-09-08 12:53:38.785 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 957ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml
2021-09-08 12:53:38.907 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2021-09-08 12:53:38.908 Debug Dlna: Using default profile for: Cache-Control=no-cache, Connection=Close, Pragma=no-cache, Accept=text/xml, application/xml, Host=XXX.XXX.XXX.XXX:8096, User-Agent=Microsoft-Windows/10.0 UPnP/1.0
2021-09-08 12:53:39.111 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 204ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml
2021-09-08 12:53:39.352 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo240.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2021-09-08 12:53:39.785 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 433ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo240.png
2021-09-08 12:53:39.919 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo240.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2021-09-08 12:53:39.929 Debug Server: http/1.1 Response 500 to 178.170.49.41. Time: 22440ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/description.xml
2021-09-08 12:53:39.969 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 50ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo240.jpg
2021-09-08 12:53:39.971 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo120.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2021-09-08 12:53:40.019 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 48ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo120.png
2021-09-08 12:53:40.036 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo120.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2021-09-08 12:53:40.088 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 53ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo120.jpg
2021-09-08 12:53:40.109 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo48.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2021-09-08 12:53:40.109 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 1ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo48.png
2021-09-08 12:53:40.111 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo48.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2021-09-08 12:53:40.111 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 0ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/icons/logo48.jpg
2021-09-08 12:53:40.117 Debug Server: http/1.1 GET http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/contentdirectory/contentdirectory.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2021-09-08 12:53:40.364 Debug Server: http/1.1 Response 200 to 178.170.42.161. Time: 247ms. http://XXX.XXX.XXX.XXX:8096/dlna/681f6ff2-2841-4398-a991-e67f399a7d5b/contentdirectory/contentdirectory.xml

 

XXX is the ip address from my server

 

Do you have some hints ? And Emby is consumming all my ram.. strange

Edited by dfou2
Posted

Uninstall the DLNA plug-in and restart your server. If the problems continue then attach the full server logs, not snippets.

If you do need DLNA it can be reinstalled later and if your server crashes again also provide those logs as attachments for the devs to review.

 

Posted

Thank you for your answer

 

I've just follow your advices, see you tomorrow or later to see if the problem is solved

 

 

Posted

A better solution would be to put the dlna plugin back and close the ports on your server machine because it looks like you have every single port exposed on the internet.

  • Like 1
Posted

why are you saying that ?

here is the result of

$ sudo netstat -tulpn | grep LISTEN
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3589/nginx: master
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      555/named
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      562/sshd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      562/sshd
tcp        0      0 127.0.0.1:61209         0.0.0.0:*               LISTEN      23015/python3
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      555/named
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      32431/openvpn
tcp        0      0 127.0.0.1:1443          0.0.0.0:*               LISTEN      3589/nginx: master
tcp6       0      0 :::53                   :::*                    LISTEN      555/named
tcp6       0      0 :::21                   :::*                    LISTEN      562/sshd
tcp6       0      0 :::22                   :::*                    LISTEN      562/sshd
tcp6       0      0 ::1:953                 :::*                    LISTEN      555/named
tcp6       0      0 :::8096                 :::*                    LISTEN      28286/EmbyServer

 

Posted

Because it looks like your server is getting dlna traffic from random internet addresses, which would only be possible if that were the case.

You can treat the symptoms if you want and just remove the dlna plugin if you don't use dlna, but that's not the actual source of the problem.

Posted

dlna plugin was indeed the problem, thanks a lot !

Posted

You should still follow the advice from @Luke and make sure you server is secure. It did look like too many services are accessible from the internet.

Posted
15 hours ago, dfou2 said:

dlna plugin was indeed the problem, thanks a lot !

@dfou2 it was not the actual problem as I've mentioned above.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...