ross87 12 Posted July 20, 2018 Posted July 20, 2018 Hello, For the past few days I have been having issues allowing Kodi to play more than 2 episodes in a row, before it is unable to connect to Emby. The only way around this is to use the Emby app on my phone, to restart the Emby server on my server. As soon as I have done this, I can play 2 episodes, before I have to restart Emby Server again. The only difference I can see in my setup is that Emby Server updated around the same time this issue started. Prior to this I had no issues for some time. My setup is as follows Server - Windows Home Server 2016 - Emby Server installed HTPC Front room - Windows 10 - Kodi 17.3 HTPC Bedroom - Windows 10 - Kodi 17.3 I have checked the server logs and found this error: *** Error Report *** Version: 3.5.0.0 Command line: C:\Users\***AppData\Roaming\Emby-Server\system\EmbyServer.dll -noautorunwebapp Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 8 Program data path: C:\Users\***\AppData\Roaming\Emby-Server\programdata Application directory: C:\Users\***\AppData\Roaming\Emby-Server\system System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at SocketHttpListener.Net.HttpConnection.Close(Boolean force) at EmbyServer.SocketSharp.WebSocketSharpListener.TryClose(HttpListenerContext ctx, Int32 statusCode) System.Net.Sockets.SocketException at SocketHttpListener.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at SocketHttpListener.Net.HttpConnection.Close(Boolean force) at EmbyServer.SocketSharp.WebSocketSharpListener.TryClose(HttpListenerContext ctx, Int32 statusCode) Any idea on how to fix this? Thanks in advance.Ross
Luke 42078 Posted July 20, 2018 Posted July 20, 2018 Hi there, why do you feel that you need to restart emby server?
ross87 12 Posted July 20, 2018 Author Posted July 20, 2018 I was just trying anything to get the streaming working again (using the age old IT method of if something doesn't work, turn it off and on again to see if it resolves the issue). Restarting the emby server via the app always brings it back for a couple of episodes.
Luke 42078 Posted July 20, 2018 Posted July 20, 2018 I would suggest attaching the emby for kodi log: https://emby.media/community/index.php?/topic/17599-how-to-report-a-problem/ Then once you've done that we'll see what @@Angelblue05 thinks. Thanks.
ross87 12 Posted July 20, 2018 Author Posted July 20, 2018 (edited) Thanks @@Luke - I've attached a log. @Angelblue05 - As far as I am aware, nothing on the network has changed in the last month or so. This issue appeared around Tuesday when I updated Emby Server - it's most probably just a coincidence, but I was struggling to understand the log to be honest. kodi.log Edited July 20, 2018 by rosslee
ross87 12 Posted July 20, 2018 Author Posted July 20, 2018 (edited) Right I've tried reading through it again and there's a mention of a caching error. Would this cause the cutting out? Used the same caching settings for the last 6 months, so it's bit odd to start erroring now. Will adjust it anyway to see if it helps. Edited July 20, 2018 by rosslee
ross87 12 Posted July 20, 2018 Author Posted July 20, 2018 Doesn't seem to be cache related. Removed the cache completely and it was still happening
Angelblue05 4132 Posted July 20, 2018 Posted July 20, 2018 Hey there. I've checked your log. If this path is correct, then it's not an issue with the add-on. Is this this file only? Like you said, Kodi is complaining about not being able to open your file cache. 18:28:16.052 T:10220 NOTICE: VideoPlayer: Opening: smb://HomeServer/Media/TV/Community/Season 1/Community - S01E02 - Spanish 101.mkv 18:28:16.052 T:10220 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED 18:28:16.052 T:10220 ERROR: DXVA::CProcessorHD::IsFormatSupported: Unsupported format 105 for 1. 18:28:16.053 T:5420 NOTICE: Creating InputStream 18:28:16.110 T:5420 ERROR: CFileCache::Open - failed to open cache 18:28:16.116 T:5420 ERROR: CVideoPlayer::OpenInputStream - error opening [smb://HomeServer/Media/TV/Community/Season 1/Community - S01E02 - Spanish 101.mkv] 18:28:16.116 T:5420 NOTICE: CVideoPlayer::OnExit() I would try the following cache settings. readfactor 100? Doesn't sound right to me... <advancedsettings> <cache> <memorysize>734003200</memorysize> <buffermode>2</buffermode> <readfactor>5</readfactor> </cache> </advancedsettings>
ross87 12 Posted July 20, 2018 Author Posted July 20, 2018 Thanks for getting back to me. It's all TV shows. It gets to the end of the show and goes back to the list of files. I then click on one of the files and the system cannot locate the files until I reboot Emby server. I'll try your recommended cache settings in the morning. Thanks.
ross87 12 Posted July 22, 2018 Author Posted July 22, 2018 Tried the cache amendment and it caused episodes to freeze for a while and then speedily catch itself up (like everything was in fast forward). It would then stop the episode. Trying buffermode back at 1 and readfactor 10 to see if that helps.
ross87 12 Posted July 26, 2018 Author Posted July 26, 2018 Unfortunately the issue is still present. It's not as frequent, but I have to exit Kodi and enter it again to be able to start it again (or restart emby server). I've attached the log - we'd watched a few episodes of Brooklyn 99 and when season 3, episode 23 and after that I was not able to continue watching. Any ideas? 1532635398810_kodi.log
ross87 12 Posted August 5, 2018 Author Posted August 5, 2018 @@Luke @@Angelblue05 Unfortunately the issue still persists. Sometimes I am able to watch an episode fine, but then others it is getting partway through and stopping. I then have to click on the show to get it to work again. This is happening on both of my HTPC's which have different hardware configurations (both stream from a HP Microserver, running Server 2016 in a different room). I've attached my most recent log. Any ideas? Thanks in advance kodi.log
Angelblue05 4132 Posted August 5, 2018 Posted August 5, 2018 Probably a samba issue. You are direct playing the file meaning Emby is not involved in the equation beyond providing the file path to Kodi. You'll have to enable Kodi debug and check if there's any smb errors.
ross87 12 Posted August 5, 2018 Author Posted August 5, 2018 Probably a samba issue. You are direct playing the file meaning Emby is not involved in the equation beyond providing the file path to Kodi. You'll have to enable Kodi debug and check if there's any smb errors. Thanks for coming back to me. Will get a debug log setup. On a different note, the error "ERROR: Got MSGQ_ABORT or MSGO_IS_ERROR return true" is mentioned in a MAC forum on Kodi.tv. It is mentioned that it is connected to the player in v17 and will not be fixed for v17, but is fixed in v18. Would this be the cause?
ross87 12 Posted August 11, 2018 Author Posted August 11, 2018 (edited) I've only just managed to use the htpc today and the issue reared its head. I've attached the debug logs. Any assistance would be greatly appreciated. 1534018357078_kodi.log Edited August 11, 2018 by ross87
ross87 12 Posted August 11, 2018 Author Posted August 11, 2018 @@Angelblue05 @@Luke I posted the log on the Kodi forums, just in case there was an issue with Kodi setup. One of the team pointed out this from the log as a possible cause: EMBY.websocket_client -> DEBUG:: Error: argument of type 'int' is not iterable 20:18:12.816 T:12500 NOTICE: EMBY.websocket_client -> DEBUG:: closed Any ideas? The server is a Gen 8 Microserver with a quad core processor and 16gb ram. Apart from the standard windows install, Emby Server is the only bit of software running.
Angelblue05 4132 Posted August 11, 2018 Posted August 11, 2018 Nope. That error is normal when closing websocket.
ross87 12 Posted August 11, 2018 Author Posted August 11, 2018 Nope. That error is normal when closing websocket. Thanks for the reply. Ah ok - I'm not too clued up on the logs, so have to rely on the advice of those more knowledgeable. Any ideas on what could be causing it to stop from logs? I've tried some ideas from Google searching the issue and so far not getting anywhere.
Angelblue05 4132 Posted August 11, 2018 Posted August 11, 2018 If I were you, I'd reset my local database, and resync using add-on playback mode instead. Then see if you still experience this issue or not. Then you'll know if it's samba related or something else.
ross87 12 Posted August 12, 2018 Author Posted August 12, 2018 Thanks @@Angelblue05. I'm trialling it now and I will feedback how it goes.
ross87 12 Posted August 12, 2018 Author Posted August 12, 2018 @@Luke @@Angelblue05 Unfortunately that doesn't seem to have resolved the issue. I've attached the log from Kodi - I can confirm I changed the file streaming to handled by Emby and reset the local database in Kodi. Any ideas? Thanks in advance. kodi.log
Angelblue05 4132 Posted August 12, 2018 Posted August 12, 2018 (edited) Sorry, can you confirm that in the add-on settings > playback, you have Force HTTP playback enabled? Thanks. Right now, it's still using smb, because I think that setting might be disabled. You can direct play in both scenario, however what I wanted you to try is direct stream where the file is provided to Kodi by Emby rather than Kodi getting the file directly via smb. Let me know. Edited August 12, 2018 by Angelblue05
ross87 12 Posted August 12, 2018 Author Posted August 12, 2018 Apologies I was being a pillock!! I misinterpreted it as using "playback mode add-on (default)" under sync options. I have just gone into Video playback and set Force HTTP to on (option slider set to the right and has gone from grey to white). I'll let you know how it goes.
ross87 12 Posted August 18, 2018 Author Posted August 18, 2018 @@Luke @@Angelblue05 Unfortunately the issue still seems to persist while allowing Emby to control the streaming. I've attached the most recent log. kodi.log
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