Jump to content

In Progress/Active Devices Issues


Recommended Posts

Posted (edited)

HIdeho

 

Problem with Active Devices from what is being caused by a time out error in the Kodi Log so I'm not overly sure if this is server side or an issue with Kodi looking for wrong info or something else entirely. Basically a device either won't show as connected (Kodi says connected to Emby) or In Progress status in the Active Devices will just be stuck at whatever value the media played back back from so will be Zero if played from the start or whatever other value and sits there.

 

In the Kodi log you get a timeout error as follows:

 

ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <class 'requests.exceptions.ConnectionError'>
                                            Error Contents: HTTPSConnectionPool(host='pathtoserver', port=443): Max retries exceeded with url: /emby/Sessions/Playing (Caused by ReadTimeoutError("HTTPSConnectionPool(host='pathtoserver', port=443): Read timed out. (read timeout=30)",))
                                            Traceback (most recent call last):
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\ga_client.py", line 24, in wrapper
                                                return func(*args, **kwargs)
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\player.py", line 216, in onPlayBackStarted
                                                self.doUtils(url, postBody=postdata, action_type="POST")
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\downloadutils.py", line 254, in downloadUrl
                                                response = self._requests(action_type, session, **kwargs)
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\plugin.video.emby\resources\lib\downloadutils.py", line 391, in _requests
                                                response = session.post(**kwargs)
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\sessions.py", line 535, in post
                                                return self.request('POST', url, data=data, json=json, **kwargs)
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\sessions.py", line 488, in request
                                                resp = self.send(prep, **send_kwargs)
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\sessions.py", line 609, in send
                                                r = adapter.send(request, **kwargs)
                                              File "C:\Users\Nerd\AppData\Roaming\Kodi\addons\script.module.requests\lib\requests\adapters.py", line 487, in send
                                                raise ConnectionError(e, request=request)
                                            ConnectionError: HTTPSConnectionPool(host='pathtoserver', port=443): Max retries exceeded with url: /emby/Sessions/Playing (Caused by ReadTimeoutError("HTTPSConnectionPool(host='pathtoserver', port=443): Read timed out. (read timeout=30)",))
                                            -->End of Python script error report<--
 
Things are running through Nginx normally but the issue is persistent if a device is connected direct via IP bypassing Nginx. Path substitution is setup to play direct over http but the issue remains even with playing through the addon. Web Interface and apps have zero issues- interface snappy, playback quick and smooth across the board and reports device and in progress correctly- it's only in Kodi itself. IT also isn't persistant- it does it one minute then not the next so is driving me up the wall!
 
In light of the timeout issue is it possible to increase the timeout somewhere in the plugin to test and rule that out as a problem?
 
I'm a bit hesitant to post full server logs as last time I did somebody tried to hack the server so you have people spying on logs here folks- be careful.
 
PS OOPS- forgot to say latest version from the emby beta repo, also tried from stable and the same. Currently on the latest dev server build but was the same in both latest stable and beta, emby sync queue is also on the very latest version if that makes any difference at all.
Edited by chiefnerd
Guest
This topic is now closed to further replies.
×
×
  • Create New...