How To Check and Fix Kodi Log File Error

Hello guys, today we are going to share another Kodi errors based guide so you can enjoy your Kodi without any errors and this tutorial will help each and every Kodi users to fix the issue when they all ask for how to check Kodi log file on their streaming device.

Sometimes some Kodi users find that their Kodi device fails to play the media stuff where they got an error called “One or more items failed to play and check the Kodi log file for more details”. But people still don’t know where to find Kodi log file? And how they can access the Kodi log file?

Well, there are many ways to fix it but the working methods are very less so you need to follow only working methods are we are going to provide you 2 methods on how to do this. Well, the Kodi log file is stored inside your Kodi device in a format of text file, so every user can open it using a text editor. If you want to read the log file than you can read but you will not understand the issue.

So, how to check Kodi log file, well we are going to explain it below:

How to Check Kodi Log File Manually?

So if you have used Kodi for a short period of time, then you might got a message like this, “One or more items failed to play. Check the log file for details”.

At the time you got this message, you immediately start feeling like, where can I get this Kodi log file?

Well, below we have added the locations where you guys can check the Kodi log file, specific to the operating system that you are using. The Kodi log file is a simple text doc which you can open with any text editor such as Notepad on Windows.

All you need is to browse to this location of where you can get the log file on your respective device and simply open it.

  • Windows: C:\Users\{user_name}\AppData\Roaming\Kodi\kodi.log
  • Mac: /Users/{user_name}/Library/Application Support/Kodi/kodi.log
  • iOS: /private/var/mobile/Library/Preferences/Kodi/kodi.log
  • Android:{storage}/Android/data/org.xbmc.kodi/files/.kodi/temp/kodi.log
  • Linux: ~/.kodi/kodi.log
  • OpenELEC & LibreELEC: /storage/.kodi/kodi.log
  • OSMC: /home/osmc/.kodi/temp/kodi.log
  • XBian: /home/xbian/.kodi/temp/kodi.log

Each line in this Kodi log file explains the event which contains the data like the time of the event, the event’s severity level and a message describing the event.

There are different severity levels in the Kodi log and you need to focus on events of level WARNING and ERROR and read that event descriptions to try and try to identify the location of the issue.

Well most of the time event descriptions show the name of the addon or the filename where the real error originated. So below we have added some quick example of the log file that will show you the real error caused by a corrupted file in the addon called Covenant.

  • 14:23:06.600 T:8816 NOTICE: Running the application…
  • 14:23:06.600 T:8816 NOTICE: starting upnp client
  • 14:23:06.607 T:5804 NOTICE: ES: Starting UDP Event server on port 9777
  • 14:23:06.607 T:5804 NOTICE: UDP: Listening on port 9777 (ipv6 : true)
  • 14:23:06.739 T:11556 ERROR: EXCEPTION Thrown (PythonToCppException) : –>Python callback/script returned the following error<–
    • NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
  • Error Type: <type ‘exceptions.ImportError’>
  • Error Contents: cannot import name None
  • Traceback (most recent call last):
  • File “C:\Users\pc\AppData\Roaming\Kodi\addons\plugin.video.covenant\covenant.py”, line 61, in <module>
  • from resources.lib.indexers import _Xq7mc31Gnv

You need to understand the infected addon and it is the only and most important part of this problem, read a couple of lines around the error when looking for the cause.

You need to understand that having tons of addons installed might make this process harder, and if you are using the pre-loaded android box is highly advisable and you should re-install Kodi with some regular addons only.

What to Do When You Find an Error?

It is damn sure that whatever issue you found on Kodi, someone already deal with the same problem, and try to the find the fixing guide with some related keywords such as addon name, repository name or developer nickname.

Most of the addon developers have the way to communicate with the user of their addon and all users can connect with them on social media handles like Twitter, Facebook, Github or they have dedicated thread or a forum, where you find the information in a readme file inside the addons folder or in the addons information screen of Kodi.

So if you are planning to ask your issue on forums, github or the other alternatives then you need to do some things first.

It is very important to enable the debug logging option on Kodi, this will add extra information about the status of Kodi on the log file, the developers should have the information to identify and fix the issue.

  • First, open the Kodi and select Settings > System Settings > Logging tab and activate the Enable Debug Logging. You’ll see some text on the top of Kodi when the debugging is enabled.

Now this setting debug logging is enabled and now you need to restart Kodi and reproduce the error, this will generate the clean log file with the error description and the bugging information. Try going to follow steps that lead you to the error.

Log Viewer for Kodi Instructions

  1. Tap on Add-ons menu item within Kodi.
  2. Now open the package icon at the top of the menu on left-hand side.
  3. Tap install from repository.
  4. Click Kodi add-on repository.
  5. Tap on Programs add-ons.
  6. Click log viewer for Kodi and then click Install.
  7. This addon will now be available under your program addons category within Kodi and you may need to launch the Log viewer from there to view your information.

Final Verdicts

We hope you find this post helpful while looking for the solution on how to check Kodi log file error. If you like this posts than share it with you friends and family who use Kodi device. If you have any query than please drop your queries in the comment section below.

Leave a Reply

Your email address will not be published. Required fields are marked *