KODI'S LOG FILE

Checking the log record

Kodi's log is a plain content record so you can open it with any word processor. In the event you are using Android you may need to use a File Explorer application, on a few frameworks.

Each OS utilizes various ways to store Kodi's records, playback failed check you can find the log document on the accompanying rundown.

 Windows Desktop:% APPDATA% \ Kodi \ kodi.log

 Windows Store:% LOCALAPPDATA% \ Packages \ XBMCFoundation.Kodi_4n2hpmxwrvr6p \ LocalCache \ Roaming \ Kodi \ kodi.log

 Linux: $ HOME / .kodi / kodi.log

mac OS: / Users / <user_name> / Library / Application Support / Kodi / kodi.log

Android: <data | sdcard | storage> /Android/information/org.xbmc.kodi/documents/.kodi/temp/kodi.log

 iOS: /private/var/portable/Library/Preferences/Kodi/kodi.log

OpenELEC: /capacity/.kodi/kodi.log

 OSMC: /home/osmc/.kodi/temp/kodi.log

 XBian: /home/xbian/.kodi/temp/kodi.log

Each line in the log record portrays an occasion, it contains information as well as the occasional seriousness level and a message depicting the occasion.

There are several seriousness levels in the Kodi log, and you can check out the wellspring of the issue.

Occasion depictions ordinarily demonstrate the name of the addon or the filename where the mistake began. Here is a case of the log document demonstrating a blunder caused by a defiled record in the addon Covenant.

14: 23: 06.600 T: 8816 NOTICE: Running the application ...

14: 23: 06.600 T: 8816 NOTICE: beginning upnp customer

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: genuine)

14: 23: 06.739 T: 11556 ERROR: EXCEPTION Thrown (PythonToCppException): -> Python callback / content restored the accompanying error <-

NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!

Blunder Type: <type 'exceptions.ImportError'>

Blunder Contents: can not import name None

Traceback (latest call last):

Document "C: \ Users \ pc \ AppData \ Roaming \ Kodi \ addons \ plugin.video.covenant \ covenant.py", line 61, in <module>

from resources.lib.indexers import _Xq7mc31Gnv

Recognizing the risky add-on is the most critical piece no stream kodi or this procedure, reading two or three lines around the blunder when searching for the reason.

Remember that having bunches or addons may make this procedure harder, on the off chance that you are using a pre-stacked android box is exceptionally prudent that you can reinstall Kodi with simply the addons you ordinarily utilize.

What to do when there is a blunder

There is an opportunity to manage a similar issue, take a stab at the blunder with some applicable catchphrases like addon name, storehouse name or engineer moniker.

Most addon engineers have an approach to twitter, facebook, github or they have a particular string on a discussion, you will presumably discover this data in a readme document inside the addon's organizer or in the addon's data screen on Kodi.

In the event you are planning on requesting help on discussions, github or alternate choices there are a few things you will need. It is essential to empower the investigative logging choice on Kodi, this will include additional data about Kodi's status on the log document, the engineers require this data and the issue.

Since investigate logging is empowered to restart Kodi and recreate the blunder, this will create a perfect log with the mistake portrayal and its separate troubleshooting data. Take a stab at experiencing the means that lead you to the blunder.

Log records may contain identifiable data like your gadget's username and hostname, some addons could uncover your IP address or passwords utilized on said addons. It's a smart thought to change all sensible data before sharing your log record.

When sharing your log document, it is viewed as a decent practice to utilize past or future comparative administration to transfer your record as a substance. Endeavor to portray the assumption of significant data as OS and Kodi variants and furthermore the addons you are utilizing.

Investigating Kodi addons is not a simple errand, once in a while it's smarter to simply reinstall the addon, this is usually the most straightforward arrangement.

There's a fantastic FAQ on Addons4Kodi's wiki, it's a must-have. The authority Kodi gathering not bolster informal spilling addons, do not post inquiries regarding hazy area addons on the official discussion.