I have some sort of issue with my Vero V that makes it sometimes regularly (perhaps every 15-30m) send some sort of signal to my TV that makes the TV switch to the Vero input (away from Chromecast mode or whatever). Irritating in the middle of an F1 race…
I sort of suspected it might be rebooting spontaneously but when I ssh:d in to investigate it turns out it uses systemd (binary logs is not the brightest of ideas…) and apparently only keeps the logs from the latest boot, so I can’t see how to find out how often it reboots without logging in regularly and checking the logs start at that time.
How do I get the Vero to preserve the boot/kernel logs for at least the 10 latest boots?
Unfortunately you need kernel messages from previous boots which are disabled by default with OSMC. To activate and provide such information, please, follow the steps below:
login via SSH to the OSMC device, user osmc, password osmc
cd /var/log
sudo journalctl --rotate
sudo journalctl --vacuum-time=1s
sudo mkdir journal
(from now, kernel messages are written to new directories for every boot)
sudo shutdown -r now
now wait for the issue/event which is the problem of this topic
once it happens again and you are forced to reboot the OSMC device or it rebooted automatically, you’ve to identify the right kernel message log:
9.a) login via SSH and invoke sudo journalctl --list-boots --no-pager
9.b) the lines start with an index id like 0, -1, -2, etc. and contain the date and time when log was started
also, upload the appropriate full log using sudo journalctl -o short-full -b <identified index> --no-pager|paste-log
(replace <identified index> with the real index id, see above)
provide the returned URLs here
don’t forget to remove the created journal directory otherwise your system’s root file system gets filled
12.a) login via SSH
12.b )cd /var/log
12.c) sudo rm -R -f journal && sudo reboot (repeat this line if you get a ‘cannot remove’ error until it works and your ssh connection gets lost by the reboot)
Mon 2025-06-30 15:17:01 CEST alcide CRON[3407]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
If it’s not the PS, look at /etc/cron.hourly/ and see what scripts/executables you find there. I have only a single script in this folder named fake-hwclock.