Hey buddy, keep calm!
Regarding the logs, I’m working on this.
IMHO, it will not be very helpful to flood the forum with a number of log entries without relation to the context where the crash happened, right? Thus, demanding for log files only sounds easy to be done on the 1st degree. But this is not true! Since OSMC does not have syslog or journald entries, there is only kodi.log which is not enough in my eyes. Who knows, if the last line in the log is the last line written? If some of the “it’s the PSU” trolls are right, nobody can guarantee, the last couple of lines are even in the logfile.
There is no evidence yet, that this is “unrelated” as you repeatedly tell us. I always get the “lost of skin settings” after the crashes I reported. So there in fact is a relation! You might have another point of view if this is a strong relation or not. That’s okay. That’s the reason I asked for getting my parts moved into a new topic.
If this is impossible I kindly ask for getting told that.
from all boxes to the same server. the server has a rsyslog filter rule to dispatch the incoming into different files. We’ll see the outcome soon…
Any idea regarding forwarding the kodi.log early before it’s written to a physical file?
I never used named pipes, but I could imagine, this is more reliable to get the last log line when a power dropout occurs. Would highly appreciate some hints…
Finally, can I get the power state information from Raspi somehow? The same that generates the yellow flash or the rainbow square if power is under the limits. Ideas?
You are most certainly incorrect here. Providing logs as directed in our wiki absolutely provides journalctl output.
Not necessarily… It could be possible that we see a glaring mis-configuration of your system that would easily explain your symptoms.
There is no relation. You are conflating two different issues and are assuming them to be the same. System crashes are a completely different issue to the skin changes being lost issue. The skin changes lost issue is addressed (previously in this thread as well as numerous other threads on the forum) as being solved and the solution is available for testing until our team is satisfied that it is appropriate and should pushed as an update to all users/platforms. I stand behind my direction provided in my last post.