(2020-03-06, 18:36)bill_orange Wrote: kodi.log ends with:
2020-03-06 08:20:12.813 T:28386 NOTICE: CAddonMgr::FindAddons: xbmc.python v3.0.0 installed
2020-03-06 08:20:12.813 T:28386 NOTICE: CAddonMgr::FindAddons: xbmc.webinterface v1.0.0 installed
2020-03-06 08:23:11.910 T:28441 ERROR: CWebServer: unable to handle HTTP POST field
*Something* (I have no idea what) appears to be sending your Kodi client an HTTP request - are you using a remote control, or accessing kodi from a browser? Enable Webserver component debug logging as that may give more details. Perhaps this is causing Kodi to crash - you should have a crash log if so.
(2020-03-06, 18:36)bill_orange Wrote: I am at a loss on how to troubleshoot this.
In the usual way - with logs.
First of all, you need to be very clear whether the system is actually rebooting (unlikely) or Kodi is crashing/restarting (much more likely).
Enable debug logging (you can add
<loglevel>1</loglevel>
to advancedsettings.xml so that the debug overlay is not visible) then upload a crash log (assuming it is a crash not a reboot) once the issue has been reproduced. If the crash log is too large to send to a pastebin site, then please zip it up and upload it somewhere (dropbox, googledrive etc.). Alternatively, once the issue has been reproduced with debug logging enabled, just upload the latest zip file from the
Logfiles
Samba share.
(2020-03-06, 18:36)bill_orange Wrote: Is this a KODI problem? Is my SD past its prime? Is my receiver sending nonconforming packet that causes a KODI crash?
Your receiver is unlikely to be the problem. It could be your SD card, these have a limited lifespan, or it could also be a PSU issue (either of these issues _could_ be responsible for reboots, particularly if you have high-current devices hanging off the USB ports). It could also be a poorly coded add-on. Or some other background service using all the memory, causing an out of memory situation.
However without logs, it's impossible to even start diagnosing the issue.