[SOLVED] Z-Wave dongle makes openhab crash

Setup, Configuration and Use Beginners
, ,
21

Finally I got an error message! Only one line, but still. I searched for a “core.pid” file in the whole file system, but found none. However, if I manually ran java and openhab, I got this message:

/usr/lib/jvm/zulu-embedded-8-armhf/bin/java: symbol lookup error: /var/lib/openhab2/tmp/libNRJavaSerial_HF_root_0/libNRJavaSerial_HF.so: undefined symbol: __fdelt_chk

Does this say anything to you guys?

Perhaps it is of interest to know how I manually ran openhab. I simply copied the line from ps -ef, after starting it with sudo service openhab2 start. It’s a super long line. Here it is:

sudo /usr/lib/jvm/zulu-embedded-8-armhf/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/share/openhab2/runtime -Dopenhab.userdata=/var/lib/openhab2 -Dopenhab.logdir=/var/log/openhab2 -Dfelix.cm.dir=/var/lib/openhab2/config -Djetty.host=0.0.0.0 -Dorg.ops4j.pax.web.listening.addresses=0.0.0.0 -Dorg.osgi.service.http.port=8080 -Dorg.osgi.service.http.port.secure=8443 -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/share/openhab2/runtime -Dopenhab.userdata=/var/lib/openhab2 -Dopenhab.logdir=/var/log/openhab2 -Dfelix.cm.dir=/var/lib/openhab2/config -Djetty.host=0.0.0.0 -Dorg.ops4j.pax.web.listening.addresses=0.0.0.0 -Dorg.osgi.service.http.port=8080 -Dorg.osgi.service.http.port.secure=8443 -Djava.awt.headless=true -Djava.awt.headless=true -Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyS0:/dev/ttyS2:/dev/ttyACM0:/dev/ttyAMA0 -Djava.endorsed.dirs=/usr/lib/jvm/zulu-embedded-8-armhf/jre/lib/endorsed:/usr/lib/jvm/zulu-embedded-8-armhf/lib/endorsed:/usr/share/openhab2/runtime/lib/endorsed -Djava.ext.dirs=/usr/lib/jvm/zulu-embedded-8-armhf/jre/lib/ext:/usr/lib/jvm/zulu-embedded-8-armhf/lib/ext:/usr/share/openhab2/runtime/lib/ext -Dkaraf.instances=/usr/share/openhab2/runtime/instances -Dkaraf.home=/usr/share/openhab2/runtime -Dkaraf.base=/var/lib/openhab2 -Dkaraf.data=/var/lib/openhab2 -Dkaraf.etc=/var/lib/openhab2/etc -Dkaraf.restart.jvm.supported=true -Djava.io.tmpdir=/var/lib/openhab2/tmp -Djava.util.logging.config.file=/var/lib/openhab2/etc/java.util.logging.properties -Dkaraf.startLocalConsole=false -Dkaraf.startRemoteShell=true -classpath /usr/share/openhab2/runtime/lib/boot/org.apache.karaf.diagnostic.boot-4.0.8.jar:/usr/share/openhab2/runtime/lib/boot/org.apache.karaf.jaas.boot-4.0.8.jar:/usr/share/openhab2/runtime/lib/boot/org.apache.karaf.main-4.0.8.jar:/usr/share/openhab2/runtime/lib/boot/org.osgi.core-6.0.0.jar org.apache.karaf.main.Main
22

No, but this looks similar and there are some other posts in the forum. Maybe you need a newer glibc?
https://github.com/openhab/openhab-core/issues/111

Why not run start.sh?

Nmjavaserial causes java to crash when attempting to open /dev/ttyACM0
23

It appears you are correct! I have glibc 2.13. I tried to replace nrjavaserial with the patched one in the post, but I must be doing something wrong. I replaced the file in this directory:

/usr/share/openhab2/runtime/system/org/openhab/nrjavaserial/3.12.0.OH

It didn’t change anything, but also I noticed that I could remove the file completely with exactly the same behavior (I would expect some openhab error message instead). Is the addon actually used located somewhere else perhaps?

This is where it shows why I chose the beginner category for this question :slight_smile: Now I know, thanks!

24

Perhaps I should move my question above to the other thread. Now I know what the problem is, and worst case I have to update my debian to a newer version, so I’m marking this as solved!

Thanks to all of you!

25

I thought I read in the PR that you’d need to uninstall nrjavaserial (from Karaf, bundle:uninstall nrjavaserial should do it), then drop the jar with the patch into the Addons directory. Have you tried that?

We all have to start some place!

1 Like
26

Your suggestion worked! This saves me a lot of hassle updating the OS, so I’m very happy, thank you! I’ll give the detailed instruction to the git issue as well, in case somebody struggled like me.