My Openhab installation has been suffering from periodic restart the last couple of days.
I get this error - I think it’s related
cmdline: /usr/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 -Djava.library.path=/var/lib/openhab2/tmp/lib -Djetty.host=0.0.0.0 -Djetty.http.compliance=RFC2616 -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 -XX:+UseG1GC -Djava.endorsed.dirs=/usr/lib/jvm/java-1.8.0-openjdk-126.96.36.199.b12-1.el7_6.x86_64/jre/jre/lib/endorsed:/usr/lib/jvm/java-1.8.0-openjdk-188.8.131.52.b12-1.el7_6.x86_64/jre/lib/endorsed:/usr/share/openhab2/runtime/lib/endorsed -Djava.ext.dirs=/usr/lib/jvm/java-1.8.0-openjdk-184.108.40.206.b12-1.el7_6.x86_64/jre/jre/lib/ext:/usr/lib/jvm/java-1.8.0-openjdk-220.127.116.11.b12-1.el7_6.x86_64/jre/lib/ext:/usr/share/openhab2/runtime/lib/ext -Dkaraf.instances=/var/lib/openhab2/tmp/instances -Dkaraf.home=/usr/share/openhab2/runtime -Dkaraf.base=/var/lib/openhab2 -Dkaraf.data=/var/lib/openhab2 -Dkaraf.etc=/var/lib/openhab2/etc -Dkaraf.log=/var/log/openhab2 -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.2.2.jar:/usr/share/openhab2/runtime/lib/boot/org.apache.karaf.jaas.boot-4.2.2.jar:/usr/share/openhab2/runtime/lib/boot/org.apache.karaf.main-4.2.2.jar:/usr/share/openhab2/runtime/lib/boot/org.apache.karaf.specs.activator-4.2.2.jar:/usr/share/openhab2/runtime/lib/boot/org.osgi.core-6.0.0.jar org.apache.karaf.main.Main
uid: 989 (openhab)
What does java - version give you?
Is it a beta version of java?
Recommended is 32bit Zulu version 8 if ARM based even if the machine is 64bit.
openjdk version "1.8.0_191"
OpenJDK Runtime Environment (build 1.8.0_191-b12)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
That’s no error message.
And what’s your HW ?
#9, #10 of
Before you ask…
Community forum is NOT a helpdesk
Let’s put this in the front: nobody here works for openHAB. The community members are helping with an Open Source Project, not a commercial software.
Additionally, the forum is NOT dealing with general Home Automation topics, the focus is on openHAB. In some cases, various products or technologies which are not directly linked to openHAB can be discussed but with the proper
title, category or tag.
We are ALL volunteering our free time to help o…
Sorry I should be more precise:
reason: java killed by SIGABRT
time: Sat 12 Jan 2019 09:20:37 AM CET
Centos 7.0 64Bit on at Virtual Machine
openHAB 2.5.0 Build #1496
openjdk version “1.8.0_191”
SIGABRT means some other process or the kernel has killed your Java.
Dunno why that happens but it’s no openHAB issue then.
And your environment is so uncommon that any guesses on ‘why’ would be random.
Sorry you need to take the long route (check all of your OS logs, g**gle elsewhere etc).
What is the uncommon part?
I’ll check log files to if I can get somewhere.
your OS, even in VM, and OpenJDK
I’d move to Zulu.
I have thought moving to Zulu, would that be a difficult task?
I wouldn’t think so but obviously that depends more on your knowledge than on the task itself
I have no knowledge of that, I’ll dig into it and see if I can come up with an solution.
Note I don’t mean to say OpenJDK causes your problem.
Could as well be that Java/OH outgrows JVM’s mem limits, either because of a memory leak or because your limits are set too low (-Xmx option to java usually)
I changed my java version - As I can see this is the recommended
Ill have to see if this solves my problem
openjdk version "1.8.0_192"
OpenJDK Runtime Environment (Zulu 18.104.22.168-linux64) (build 1.8.0_192-b01)
OpenJDK 64-Bit Server VM (Zulu 22.214.171.124-linux64) (build 25.192-b01, mixed mode)
This is what was happening when PhantomJS runs amok on RPi.
@Nanna_Agesen, check the syslog and if it’s the kernel killing OH you will see it doing so there.
Also, are you running an older version of Grafana or a newer version with PhantomJS manually restored? I have seen where this causes exactly this problem on RPis, perhaps it’s a more universal problem.
I’ll go through my logs to see what’s going on - thanks for the hint