OpenHAB 2.3.0 Release unexpected system restarts

Setup, Configuration and Use Runtime
,
1

Since I upgraded my RaspPi3 from OpenHAB 2.2.0 release to 2.3.0 the system started rule is fired from time to time without any reason. Nothing in the logs out of normal. It doesn’t seem that the system restarts really (I.e I don’t see the standard full system init getting up web sites, z-wave, etc), is like when I update a items/rules/sitemap file when system started rule is fired (and I receive a Telegram message notifying me) but not a complete openhab restart occurs

Does anybody have any idea where can I look for to figure out what’s causing it? It is the first time log files does not tell me anything of value

Openhab.log:
2018-06-17 14:10:23.873 [WARN ] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Unsupported multi instance command version: 0.
2018-06-17 14:10:23.874 [WARN ] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Unsupported multi instance command version: 0.
2018-06-17 14:10:23.876 [WARN ] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Unsupported multi instance command version: 0.
2018-06-17 14:10:23.877 [WARN ] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Unsupported multi instance command version: 0.
2018-06-17 14:11:45.982 [INFO ] [smarthome.model.script.General rules] - ##### System Started #####
2018-06-17 14:12:10.975 [INFO ] [class.ZWaveMultiInstanceCommandClass] - NODE 27: Received a multi instance encapsulation with a destination endpoint = 3.
2018-06-17 14:12:10.995 [INFO ] [class.ZWaveMultiInstanceCommandClass] - NODE 27: Received a multi instance encapsulation with a destination endpoint = 4.
2018-06-17 14:14:53.262 [INFO ] [ipse.smarthome.model.script.Lighting] - F2_Attic_Xiaomi_LightSwitch received update=OFF
2018-06-17 14:15:28.995 [INFO ] [class.ZWaveMultiInstanceCommandClass] - NODE 27: Received a multi instance encapsulation with a destination endpoint = 3.
2018-06-17 14:15:29.141 [INFO ] [class.ZWaveMultiInstanceCommandClass] - NODE 27: Received a multi instance encapsulation with a destination endpoint = 4.

Events.log
2018-06-17 14:11:28.749 [vent.ItemStateChangedEvent] - GF_Hall_Temperature changed from 26.9 to 27
2018-06-17 14:11:30.905 [me.event.ThingUpdatedEvent] - Thing ‘network:pingdevice:a63b705c’ has been updated.
2018-06-17 14:11:30.917 [vent.ItemStateChangedEvent] - network_pingdevice_a63b705c_online changed from OFF to ON
2018-06-17 14:11:41.722 [vent.ItemStateChangedEvent] - GF_LivingRoom_MotionSensor changed from ON to OFF
2018-06-17 14:11:41.729 [vent.ItemStateChangedEvent] - mihome_sensor_motion_158d0001ad4058_motion changed from ON to OFF
<<<<<<----- System started occurs here ----<<<<
2018-06-17 14:11:54.049 [vent.ItemStateChangedEvent] - SysMemoryUsedPercent changed from 41.4 to 41.6
2018-06-17 14:11:54.055 [vent.ItemStateChangedEvent] - systeminfo_computer_Home_memory_usedPercent changed from 41.4 to 41.6
2018-06-17 14:11:54.060 [vent.ItemStateChangedEvent] - SysCpuLoad changed from 3.9 to 8.0
2018-06-17 14:11:56.556 [vent.ItemStateChangedEvent] - network_pingdevice_192_168_0_250_lastseen changed from 2018-06-17T14:10:56.391+0200 to 2018-06-17T14:11:56.540+0200

2

This is “normal”. If you edit/modify a rules file, the System started condition will be satisfied and the rule will fire. There is no actual OH2 restart… This hasn’t changed since 2.2.

3

Hi Dim, I know it is normal behaviour when I edit/modify a file, but it was not the case, I was out of home at this moment, and other times it happens in the middle of the night. I meant it is the same as when I modify a file as OpenHAB does not reboot completely but system started rule if fired. With 2.2 I never had unexpected system starts if I was not touching the items/rules/sitemap files

… well, with 2.2 It was one instance of unexpected system start event, that continues happening on 2.3 and is when OpenHAB is really starting, it produces two or sometimes three system start events in 2 to 6 minutes period. I never was able to figure out why the second event was fired as there is no clue in the log files either. But this is other (I think unrelated) issue

4

oh ok.

There is an open issue that looks related: Rule “System started” runs twice · Issue #5188 · eclipse-archived/smarthome · GitHub

5

With version 2.3 i have exactly the same problem (manual installation…same config)
Java is crashing (hs_err_pidxxx.log is created) and openhab2 makes a restart.
This can happen after 2 hours, 2 days…no change to reproduce. Openhab.log/event.log do not give any information. System log files does not give any informations.

The only thing that i know for shure. It does not happen with version 2.1 and it is not depending on the java version.

@Dixon. Could you check if there is a java crash file created ?

6

In /var/log/openhab2 there is no other log file other than events.log, openhab.log and their rolling files

But as you said the error can happen after 2 hours or 2 days, there is no logic on it, and a couple of times it happened in the middle of the night where very little system activity as going on (just temp sensor updates and things like that).

@Dim, the issue 5188 seem very similar, but according to it the events occur one right after the other. In my case it use to take a couple of minutes, some times up to 10, so I’m not sure is exactly the same. As system works I will wait until 2.4 and pray it will be solved by itself as other minor issues I find in the logs that did not happen on 2.2.

7

@Dixon, could you please check at …openhab2/userdata for java crash files. For manual installation the crash files are under /opt/openhab2/userdata

8

In my system /opt/openhab2 do not exist. $OPENHAB_USERDATA points to /var/lib/openhab2 where I find backups cache config etc habmin jsondb persistence tmp zwave