Lots of errors in kodi.log


I was attempting to use one of my add-ons (SendToKodi - allows me to send/share YouTube, Vimeo and other videos straight to my Vero from my laptop, phone or tablet). In this particular case it wasn’t working for a particular video I wanted to share and prompted me to check the kodi.log for more details.

Checking the kodi.log I found what the issue was for what I was trying to do and then saw a heck of a lot of other unrelated errors. I tried to attach the full kodi.log for detail, but it wasn’t an allowed file type. But I have included below a couple of examples of the errors that I found in the kodi.log below:

2020-04-26 21:10:12.606 T:3404182240   ERROR: Traceback (most recent call last):
2020-04-26 21:10:12.606 T:3404182240   ERROR:   File "/usr/lib/python2.7/SocketServer.py", line 596, in process_request_thread
2020-04-26 21:10:12.607 T:3404182240   ERROR:     self.finish_request(request, client_address)
2020-04-26 21:10:12.607 T:3404182240   ERROR:   File "/usr/lib/python2.7/SocketServer.py", line 331, in finish_request
2020-04-26 21:10:12.607 T:3404182240   ERROR:     self.RequestHandlerClass(request, client_address, self)
2020-04-26 21:10:12.607 T:3404182240   ERROR:   File "/usr/lib/python2.7/SocketServer.py", line 654, in __init__
2020-04-26 21:10:12.607 T:3404182240   ERROR:     self.finish()
2020-04-26 21:10:12.607 T:3404182240   ERROR:   File "/usr/lib/python2.7/SocketServer.py", line 731, in finish
2020-04-26 21:10:12.607 T:3404182240   ERROR:     self.socket.sendto(self.wfile.getvalue(), self.client_address)
2020-04-26 21:10:12.608 T:3404182240   ERROR: error: [Errno 1] Operation not permitted


2020-04-26 20:45:30.321 T:4069122048   ERROR: GetString: error reading /sys/firmware/devicetree/base/buggymali
2020-04-26 20:45:30.334 T:4069122048   ERROR: GetString: error reading /home/osmc/.kodi/userdata/disp_cap
2020-04-26 20:45:30.334 T:4069122048   ERROR: GetString: error reading /sys/class/amhdmitx/amhdmitx0/vesa_cap


2020-04-26 20:48:38.766 T:3751514848   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.AttributeError'>
                                            Error Contents: 'module' object has no attribute 'isBTPlayerActive'
                                            Traceback (most recent call last):
                                              File "/usr/share/kodi/addons/service.osmc.btplayer/service.py", line 195, in onPlayBackStopped
                                                if xbmc.isBTPlayerActive() and self.btPlayer.isPlaying() and self.btPlayer.player:
                                            AttributeError: 'module' object has no attribute 'isBTPlayerActive'
                                            -->End of Python script error report<--

As far as I can tell and remember, these issues did not correspond to times that I was actually using my Vero…
Is anyone able to shed any light on this? Happy to provide full debug logs as well if they will help.

Thanks :slightly_smiling_face:

Complete logs will be much more useful than just these snippets.

1 Like

OK. Will do. I’ll turn on debug logs and reboot.
How long should I let it collect full debug logs before uploading here?

Idk how long it takes for the errors to manifest. Maybe let it log idle overnight?

1 Like

OK. Thanks. Will do :+1:

Was it a YouTube video you were trying to send? If so, is your YouTube add-on currently working? That add-on has had a bit of a rough go lately and the only way to get working reliably seems to be making your own api keys and configuring the YouTube add-on with them. I use a similar extension in Chrome (Play to Kodi) and this is what I had to do to get it working again after the YouTube problems started.

No it wasn’t a YouTube video. As far as I know the YouTube add-on works. But to be honest I don’t use it directly… I only go through my sendtokodi add-on.
That particular issue with the add-on didn’t work as the url I was attempting to share through the add-on wasn’t correct/didn’t have the required information.

As far as I know (isn’t very much :wink:) the other issues I noticed in the kodi.log aren’t related (but I could be wrong). Hopefully the debug logs I’m now collecting will shed some light on what’s causing them

So your saying that you had an issue, you determined that the error was not anything to do with OSMC/Kodi, but you noticed some ugliness in your logs so you want us to figure out things in your logs that are not actually manifesting problems with using Kodi? The problem with this is that not all errors are actually errors, for example…

2020-04-26 20:45:30.321 T:4069122048   ERROR: GetString: error reading /sys/firmware/devicetree/base/buggymali
2020-04-26 20:45:30.334 T:4069122048   ERROR: GetString: error reading /home/osmc/.kodi/userdata/disp_cap
2020-04-26 20:45:30.334 T:4069122048   ERROR: GetString: error reading /sys/class/amhdmitx/amhdmitx0/vesa_cap

None of these are errors. The first has to do with something that I don’t think has been implemented yet, and the other two are checks for optional configuration files that most people would not be using.

No offence but I think you need to identify a specific issue and ask for help with that including details on how someone else would go about reproducing it.

1 Like