Lately every time I turn on my TV I notice that the GUI on my OSMC installation has crashed. I’m still able to SSH in to reboot my Pi.
Here’s my log, thank you in advance for your assistance.
What are you using for a remote? When you think it has crashed have you tried plugging in a keyboard to see if it responds to that?
I’ve been using HDMI-CEC which it doesn’t respond to but I also have a keyboard connected that I can try next time.
Does OSMC timeout the display like a PC does?
There is some options in that regard but I was thinking more along the lines that maybe the TV just wasn’t always picking up the RPi as the active device and as such, is sometimes not trying to send CEC commands to it. I had a TV in the past that would do this sometimes and I would have to switch to a different input and back again to get the TV to forward CEC again. A keyboard should be a fairly straightforward option for trying to discern between Kodi freezing and a CEC control issue.
Another thing that may be a possibility is your MySQL setup. If the device that is hosting that database drops out for some reason then Kodi tends to get really bitchy about it. Sometimes you can just wait it out and Kodi will come back but other times Kodi will just sit there unresponsive even if the database host is currently active. I don’t have any insight into that from your logs though as they are not debug logs and I’m not sure if they contain the event in question or not.
Of course it worked great for 2 weeks after you responded but has failed again. I tried two different keyboards to no avail. Can I access the logs needed from the command line?
Also the MySQL server is hosted on the same raspberry pi.
grab-logs -A
-bash: grablogs: command not found
sorry typo, grab-logs -A
I have experienced this often over the last month or so as well, running on an OSMC box though.
Yatse works (as in, the box is not offline so the control endpoints answer) and I can turn on my receiver and TV via it.
I can SSH into the box as well, but the UI is frozen and I need to either cut power or restart the KODI systemd service via an SSH terminal.
It is pretty annoying.
Would suggest posting a log and some more details. Not sure how this is related to Raspberry Pi devices
I grabbed a log from the command line but it’s 55 MB.
I’ll try and grab some logs next time it happens, would that just be the file from .kodi/temp/kodi.log
Restart twice, wait for the issue to repeat, then upload logs.
Kodi’s log by itself doesn’t give a full picture of what is going on with the system. Optimal would be to connect to the command line and run the “grab-logs -A” command mentioned above (do note that command is case sensitive). Additional information can be found in the following…
Here you go. Thank you for looking at this