Define the shortest useful reproduction
A useful Kodi debug log begins with a specific failure that another person can understand. Choose a short sequence, such as opening one known file or attempting one library update. Record the Kodi version, platform and relevant add-on version before enabling extra logging. Avoid mixing unrelated installation, scanning and playback problems into one long session.
Prepare any source credentials privately. A debug log can include paths, device information and details supplied by add-ons; do not assume every private value is automatically removed. Decide where you will keep the original log and how you will review a copy before sharing. Capturing evidence does not require publishing it immediately.
Enable the documented logging mode and restart normally
Kodi documents the GUI route under Settings, System settings and Logging, with the debug-logging control there. Enable it, then use Kodi’s normal power menu to restart the application as appropriate for the platform. Pulling the device’s power is not equivalent: a normal exit lets the application save settings and close files.
After restart, repeat only the selected failure. Keep the time of the attempt and the exact visible error. If the failure needs a particular account, item or audio track, use the same choice throughout the test. A comparison is much harder to interpret when the media source and application settings change together.
Preserve the session that contains the fault
Kodi’s current log is named kodi.log; the next startup moves the previous session to kodi.old.log. This rotation makes timing important. Copy the relevant file before multiple additional restarts replace the evidence you intended to preserve. Include the complete relevant session in a private working copy rather than keeping only a line that looks like the answer.
Review that copy for passwords, tokens and private addresses before any public submission. Preserve the surrounding sequence while redacting sensitive values consistently. If an official support process requests a full log, follow its current instructions and disclose the redaction. Avoid pasting an unreviewed log into an unrelated website simply because it offers an upload button.
Return the installation to ordinary logging
After the reproduction, disable debug logging unless an ongoing investigation requires it. Retain the reproduction steps, capture time and copied filename together. These details help distinguish a log from the failed session from a later session in which nothing was tested.
If the GUI cannot be reached, Kodi provides a separate advanced logging route; that is a different procedure and should be followed for the actual operating system. Do not improvise system-file locations from a tutorial for another device. A successful capture gives support the sequence it needs without claiming that the failure itself has been resolved.
Questions answered
Should I restart Kodi repeatedly before copying the log?
No. Kodi rotates the current and previous session logs. Copy the session containing the fault before later restarts replace it.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.