I just migrated to openhab 3.1, and every now and then I noticed that some channels we’re having null values, which only happens when openhab is recently restarted.
Further investigation shows that the zwave binding is causing (perhaps indirectly) a total JVM crash:
$ kubectl -n openhab logs --previous --previous openhab-7bf475b69b-hxvsz [trunc'ed output] # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007ff7781c68f1, pid=106, tid=814 # # JRE version: OpenJDK Runtime Environment Zulu11.48+21-CA (11.0.11+9) (build 11.0.11+9-LTS) # Java VM: OpenJDK 64-Bit Server VM Zulu11.48+21-CA (11.0.11+9-LTS, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # j org.openhab.binding.zwave.handler.ZWaveControllerHandler.stopNetwork()V+120 # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /openhab/userdata/core.106) # # An error report file with more information is saved as: # /tmp/hs_err_pid106.log Could not load hsdis-amd64.so; library not loadable; PrintAssembly is disabled # # If you would like to submit a bug report, please visit: # http://www.azulsystems.com/support/ #
I have to note that I’m using my zwave dongle remotely using ser2net, but this is proven rock solid for multiple years with openhab 2.5.
Does this crash/error ring a bell for anyone?