Log file: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
No edit summary
Line 23: Line 23:
<big>* '''[[Log file/Advanced]] -'''</big>
<big>* '''[[Log file/Advanced]] -'''</big>
If your Kodi refuses to start, or crashes while attempting to start or while navigating the menu's, then use this method to create the Debugging Log.
If your Kodi refuses to start, or crashes while attempting to start or while navigating the menu's, then use this method to create the Debugging Log.
== Component-specific logging ==
For more extensive logging, several components can be selected to put in more detailed debug messages in Kodi's log file. Multiple components can be selected for extending the debugging of the
Kodi application.
[[File:Component-logging-selection.jpg|500px|Component logging selection window]]
==== Verbose logging for the SMB library ====
==== Verbose logging for the libcURL library (HTTP(S), DAV) ====
==== Verbose logging for the FFmpeg libraries ====
==== Verbose logging for the Audio component ====
==== Verbose logging for the Video component ====
==== Verbose logging for D-Bus calls ====
==== Verbose logging for JSON-RPC requests ====
==== Verbose logging for the Webserver component ====
==== Verbose logging for the Airtunes library ====
==== Verbose logging for the UPnP components ====
==== Verbose logging for the libCEC library ====





Revision as of 01:48, 20 January 2018

Home icon grey.png   ▶ Troubleshooting ▶ HOW-TO:Submit a bug report ▶ Log file


At some point during your foray into Kodi, you will likely come up against a problem that isn't made 100% clear from errors in the GUI. This is where the log file comes into play. Kodi writes all sorts of useful stuff to its log, which is why it should be included with every bug/problem report.


Important Notes

  • Do NOT post your logs directly in a forum. Always use a paste site like pastebin.com. Post the link to your pasted log in the forum. Details are in the following pages.
  • Provide FULL Logs only. No Partial logs or snippets. The only redactions should be personal information.
  • Be aware that the Logs are "Session Logs" only. The logs are written from Kodi startup to Kodi shutdown (or crash). The next time you start Kodi, the kodi.log is cleared, and a new log is created. The kodi.log that was there is renamed to kodi.old.log and the existing kodi.old.log is deleted. In effect you only ever have two logs available- the current one, and the previous one. Depending upon your situation and which of the following methods you use, be mindful of the following:
    • If you are going to restart Kodi to use the uploader app, you need to upload kodi.old.log
    • Before restarting, you can manually copy and paste the contents of the kodi.log to a pastebin site


Basic Method

* Log file/Easy - If Kodi is operational and you can still navigate through the menu system, use this method to create the Debugging Log.


Advanced Method

* Log file/Advanced - If your Kodi refuses to start, or crashes while attempting to start or while navigating the menu's, then use this method to create the Debugging Log.


Component-specific logging

For more extensive logging, several components can be selected to put in more detailed debug messages in Kodi's log file. Multiple components can be selected for extending the debugging of the Kodi application.

Component logging selection window


Verbose logging for the SMB library

Verbose logging for the libcURL library (HTTP(S), DAV)

Verbose logging for the FFmpeg libraries

Verbose logging for the Audio component

Verbose logging for the Video component

Verbose logging for D-Bus calls

Verbose logging for JSON-RPC requests

Verbose logging for the Webserver component

Verbose logging for the Airtunes library

Verbose logging for the UPnP components

Verbose logging for the libCEC library