Login at Kodi Home

ullms · 2015-01-16, 19:57

I keep getting this error (Client AcceptCallback error) on ServerWMC. It usually happens when not used for some but has happen when deleting a recorded show & during LiveTV playback. I have reloaded ServerWMC and it does the same thing. Only way to get serverwmc and kodi to reconnect is to stop/start serverwmc.

Please help

Serverwmc Log
http://pastebin.com/sZvd9hpP

krustyreturns · 2015-01-16, 20:23

According to the log something on your client machine is killing the connection, here is the exception:

2015/01/16 06:34:07.467 SocketServer>AcceptCallback: System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndAccept(Byte[]& buffer, Int32& bytesTransferred, IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndAccept(IAsyncResult asyncResult)
at ServerWMC.Worker.SocketServer.AcceptCallback(IAsyncResult ar)
2015/01/16 06:41:45.435 MaintenanceTimer> callback at 6:41 AM

Do you have this problem with kodi running on the swmc machine?

ullms · (This post was last modified: 2015-01-16, 23:25 by ullms.)

I have Kodi Running on the swmc machine without any issues until this happens. I'm just unsure which remote host is forcibly closing. I have one windows(nuc) running pvrmc client and two amazon fire tvs. This error stops connections on all 3 clients

krustyreturns · 2015-01-17, 01:18

I will look at the code and see if I can figure out why swmc doesn't recover from the error. The only way you have found to recover after this error is to restart swmc right? or does everything need to be restarted?

ullms · 2015-01-17, 02:03

Correct, I only need to restart swmc to fix the connection.

krustyreturns · 2015-01-17, 18:03

Can you grab another log after the error occurs and confirm that you get the same exception I posted above? I just want make sure that this one isn't a fluke. So far I cannot find why this error brings down the socket server, so I just to make sure I'm not looking in the wrong place.

ullms · 2015-01-17, 18:24

I will definitely get you another log. The error has been the same in every log I have checked after the error. I'm thinking its my AFTV that is hooked up via WIFI that is causing the issue. I just uninstalled swmc again and made sure this time that every folder and file of swmc was removed before re-installing. I have since removed the AFTV that had the pvr addon installed and have not had the error re-occur but I'm going to try the AFTV again when I get home this afternoon. I will report back.

krustyreturns · 2015-01-17, 18:26

You don't need to post the log again, so long as you are looking at them and seeing the same error each time, that's good enough. If you see something different, then post the log. I will continue to stare at the code when I can.

ullms · 2015-01-18, 20:35

Must have just been something with one of my aftv boxes. I ended up factory resetting the whole box and now it doesn't crash swmc. Strange.

Thanks for looking into it.

krustyreturns · 2015-01-18, 20:43

Please keep me posted if you get more info on it.

ullms · 2015-01-23, 17:25

Same error started happening again. It only seems to happen when my AFTV are connected to the swmc. Not sure if it has something to do with the AFTV going to sleep or that it is registering with swmc as localhost. Is there a way that you know of to change the hostname of the AFTV(rooted) to something more appropriate. I've be looking for a solution to the hostname to test but can't seem to get the change to stick on reboot.

Here is a updated log.
http://pastebin.com/ApEsZqu0

krustyreturns · 2015-01-23, 19:35

Is there someway to make the aftv not go to sleep (obvious, I know)? I don't think the localhost name the aftv uses should be confusing swmc. When the error occurs you still have to reboot swmc again to get it to work again?

ullms · (This post was last modified: 2015-01-23, 20:47 by ullms.)

Yes I can make the Aftv not sleep. Have not tried that yet and is not ideal but I'll try for testing purposes. Yes just a restart of swmc fixes the issue. Until the next time.

krustyreturns · (This post was last modified: 2015-01-23, 21:04 by krustyreturns.)

Ok. I guess I need to figure out why it is you need to restart swmc after all. And yeah, just try the no-sleep thing for testing.

Is it still true that after you get this error, swmc is stuck with an error message on the status tab?

krustyreturns · 2015-01-23, 21:18

I was able to get swmc's socket server to hang where I think it is hanging for you, by throwing an exception intentionally. I think I have a fix too, can you run a test build and see if solves the problem? (it won't solve the connection problem, it will just make it so swmc can continue if it happens).