neik 873 Posted March 23, 2018 Posted March 23, 2018 (edited) Hi guys, I am having a problem when a specific client of mine connects to the server. Server: 3.2.70 on a x64-Ubuntu Client: Emby for Samsung (UE48H6470) First I thought it would be a rclone problem but apparently it is a Emby problem. The log attached is a snippet from the moment the specific client connects until the server crashes. No more clients were connected at that point to the server. To be honest I don't know what else to write! In case you need further information, I'll be here to answer. :-) Thanks! €dit: Has the SSL problem been fixed in the most recent versions of Emby? Unfortunately, when I updated to 3.3.x SSL stopped working. emby_crash_clean.txt Edited March 23, 2018 by neik
Luke 42077 Posted March 23, 2018 Posted March 23, 2018 I'm trying to hunt down when the ssl issues started. If I give you some build zips would you mind trying them? These would be builds that came after 3.2.70, to try and isolate where it started. thanks.
neik 873 Posted March 23, 2018 Author Posted March 23, 2018 Yeah, sure! But is it the SSL problem related to the Emby crash with this specific client?
Luke 42077 Posted March 23, 2018 Posted March 23, 2018 Well the best thing to do is get you updated to the latest version, but it's clear you don't want to do that for other reasons. Attached is 3.2.70.1. Please unzip this over your current install - well, except the .config files, don't overwrite those. so you might want to unzip to a different folder, and then copy everything else in. Thanks. Emby.Mono.zip
Luke 42077 Posted March 23, 2018 Posted March 23, 2018 If you're able to use ssl on that, then here is the next one to try, 3.2.70.6. Thanks. Emby.Mono.zip
neik 873 Posted March 23, 2018 Author Posted March 23, 2018 (edited) There are a lot of ddl-files but I am on Linux (Ubuntu). Where exactly would I need to replace those files? €dit: I wouldn't mind updating to 3.3.x but given that I am also accessing from outside I am not willing to give up SSL protection. Edited March 23, 2018 by neik
neik 873 Posted March 23, 2018 Author Posted March 23, 2018 Substituted the files in that folder and ended up with this error while starting emby now. Unhandled Exception: System.DllNotFoundException: libsqlite3.so at (wrapper managed-to-native) SQLitePCL.SQLite3Provider_sqlite3+NativeMethods:sqlite3_libversion_number () at SQLitePCL.SQLite3Provider_sqlite3.SQLitePCL.ISQLite3Provider.sqlite3_libversion_number () [0x00000] in <98e8b101383146ef85e758cb0be46bea>:0 at SQLitePCL.raw.SetProvider (SQLitePCL.ISQLite3Provider imp) [0x00008] in <73e712ea9d1b47d7be4afb0c91ae9225>:0 at MediaBrowser.Server.Mono.MainClass.SetSqliteProvider () [0x00005] in <9f983f0e5bb646f694dc44c8e9fa887a>:0 at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x0000a] in <9f983f0e5bb646f694dc44c8e9fa887a>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.DllNotFoundException: libsqlite3.so at (wrapper managed-to-native) SQLitePCL.SQLite3Provider_sqlite3+NativeMethods:sqlite3_libversion_number () at SQLitePCL.SQLite3Provider_sqlite3.SQLitePCL.ISQLite3Provider.sqlite3_libversion_number () [0x00000] in <98e8b101383146ef85e758cb0be46bea>:0 at SQLitePCL.raw.SetProvider (SQLitePCL.ISQLite3Provider imp) [0x00008] in <73e712ea9d1b47d7be4afb0c91ae9225>:0 at MediaBrowser.Server.Mono.MainClass.SetSqliteProvider () [0x00005] in <9f983f0e5bb646f694dc44c8e9fa887a>:0 at MediaBrowser.Server.Mono.MainClass.Main (System.String[] args) [0x0000a] in <9f983f0e5bb646f694dc44c8e9fa887a>:0
Luke 42077 Posted March 23, 2018 Posted March 23, 2018 I think you must have overwrote the .config files. See my note earlier about that.
neik 873 Posted March 23, 2018 Author Posted March 23, 2018 Well, I tried to identify the config files but I wasn't able to. Could you point out what files exactly I would need to overwrite or which ones I should avoid? Thanks! With restored backup it's working like a charm again.
neik 873 Posted March 23, 2018 Author Posted March 23, 2018 I can access my server with both beta versions via SSL and also stream. Do you need any logs?
Luke 42077 Posted March 23, 2018 Posted March 23, 2018 Well, the issue is that after some period of time you'll be unable to. So for those who can reproduce what i'm looking for is help in identifying what version this started with.
neik 873 Posted March 23, 2018 Author Posted March 23, 2018 Ok! I will then let it run until it crashes or something happened. Will report back!
neik 873 Posted March 24, 2018 Author Posted March 24, 2018 Hi Luke, I tried both versions you posted and both led to the same error as described in post #1. My other clients (FTVS with Emby for Kodi) don't lead to emby crashing. I can post logs in case you need them.
neik 873 Posted March 25, 2018 Author Posted March 25, 2018 Hi Luke, it apparently seems to be an issue the the Emby for SamsungTV client for the H-series. I streamed the exact same file with Emby for SamsungTV on a F-series TV and there it worked flawlessly. Both TV's have the Smart Hub set to the US region and my server is running 3.2.70 stable instead of the betas you provided. Any idea what it could cause the crash?
neik 873 Posted March 25, 2018 Author Posted March 25, 2018 Hi Luke, the server-log in post #1 is from the starting point of the stream until the crash of the server using the problematic client (H-series). Attached to this post is a server-log from the client not causing the crash (F-series). emby_log_clean.txt
neik 873 Posted March 26, 2018 Author Posted March 26, 2018 Hi Luke, I think I found the cause for the crash. Right before the Emby server crashed I ran the following lsof /mountpoint mono-sgen 5332 emby 89r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 98r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 99r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 105r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 109r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkv/mono-sgen 5332 emby 111r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 112r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 114r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 116r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 119r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 120r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 123r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 125r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 126r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 129r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 131r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 132r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 133r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 136r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 137r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 139r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 142r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 144r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 145r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 147r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 149r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 151r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 154r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 157r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 160r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 162r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkvmono-sgen 5332 emby 164r REG 0,44 7625311115 4836330163857162351 /mountpoint/testfile.mkv At that point there was only the H-series SamsungTV streaming one file but as you can see above the file is opened quite often. Why is that so? When I use other clients (for instance, Emby for Kodi or Emby for Android) there is only one entry in lsof /mountpoint per client and file being streamed.
neik 873 Posted March 26, 2018 Author Posted March 26, 2018 (edited) Nope, official Emby for Samsung from US store. €dit: Interesting enough the F-series does not do that. Edited March 26, 2018 by neik
Luke 42077 Posted March 27, 2018 Posted March 27, 2018 Ok I don't really have an answer for that one given that it's direct playing. Do you have any objection to a fresh install using our newer install package?
neik 873 Posted March 27, 2018 Author Posted March 27, 2018 As soon as the SSL problem in 3.3.1.0 is fixed I will update to the latest version on my "productive" system but in the meantime I am willing to set something up to give it a try on a test system so we can see if this problem is fixed with the newest version. I come back to you as soon as I have more information (might take a couple of days).
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now