[rPi3B, Stretch Lite, Zulu Java (zulu126.96.36.199-jdk1.8.0_181-linux_aarch32hf), mosquitto, samba,
OH2.4.0-1 (apt-get), text-based config,
binding = expire1,fritzboxtr0641,mqtt1,weather1,astro,exec,network,ntp,systeminfo,logreader
ui = paper,basic,classic
persistence = rrd4j,mapdb
action = mail,mqtt
I migrated from OHv1 to OHv2 on Jan 1st, 2019, by installing a new machine and copying items, rules, etc. files to the new 2.4.0
Since then OHv2.4.0-1 sh!t itself twice = stopped working entirely.
[peaks in the graph reflect the required reboots]
01/01/2019 Started OHv2
28/01/2019 stopped working
14/04/2019 stopped working
Both time, the system was running all by itself; meaning no console, SSH, update, config activity of sort. I cannot find any hits in syslog, OH logs as to why the OH died.
Is there a way I can monitor OH (other than through OH) to send a message somewhere to have the system rebooted?
Well, the real questions are, — and based on what I read on the forum, that his seems to be a occurrence at a level not experienced on OHv1 — is the root cause known? Will it be fixed?
I could go back to OHv1, because I have the complete system decommissioned. Not what I want. But six weeks uptime for rPi running OH and MQTT is not a stellar uptime.
Any hints appreciated.