[RPi2] OpenHab Crashes Several Times a Day

Hi All;

I seem to be facing an interesting situation here. I have openhab configured with readonly data from my EcoBee3 and SNMP gets from my router. The strange thing is that OpenHAB only runs for a few hours before it completely crashes. Sometimes the crash is so bad that it seems to take the system out with it to the point that I can no longer SSH into my RPi2.

As a new user I can’t upload any files so I will post some snippets of the latest hs_err file that got dumped by the crash:

# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x764ec06c, pid=1385, tid=1682343008 # # JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132) # Java VM: Java HotSpot(TM) Client VM (25.0-b70 mixed mode linux-arm ) # Problematic frame: # V [libjvm.so+0x16506c] CounterDecay::do_method(Method*)+0x4 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp #

System Information:

OS:PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)"

JVM Information:

pi@raspberrypi:/tmp $ java -version java version "1.8.0" Java(TM) SE Runtime Environment (build 1.8.0-b132) Java HotSpot(TM) Client VM (build 25.0-b70, mixed mode) pi@raspberrypi:/tmp $

OpenHab.log tail:

2016-01-17 23:43:35.943 [INFO ] [.service.AbstractActiveService] - Exec Refresh Service has been started 2016-01-17 23:43:39.899 [INFO ] [.service.AbstractActiveService] - SNMP Refresh Service has been started 2016-01-17 23:43:39.899 [INFO ] [.service.AbstractActiveService] - NTP Refresh Service has been started 2016-01-18 00:22:46.322 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 01:22:58.822 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 02:23:12.281 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 03:13:47.683 [WARN ] [inding.ntp.internal.NtpBinding] - couldn't establish network connection [host 'ptbtime1.ptb.de'] -> returning current sytem time instead 2016-01-18 03:23:25.706 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 04:23:39.729 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 05:23:53.165 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 05:58:54.845 [WARN ] [inding.ntp.internal.NtpBinding] - couldn't establish network connection [host 'ptbtime1.ptb.de'] -> returning current sytem time instead 2016-01-18 06:24:10.329 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 07:24:25.747 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 08:24:39.155 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error 2016-01-18 09:24:54.675 [WARN ] [g.openhab.io.net.http.HttpUtil] - Method failed: HTTP/1.1 500 Internal Server Error

Those logs are the Ecobee access token expiring every hour, as expected.

I run the same JVM on an RPi2 running Debian wheezy with no issues (openHAB 1.7.1 and recently 1.8.0 with several addons including ecobee). Does your microSD card have a lot of “mileage” – lots of writes over time? Unfortunately when an SD card fails, it can be hard to isolate it as the cause of the resulting issues.

I would consider trying a fresh microSD card, or a different RPi2, or re-imaging your current microSD card and building back up.

1 Like

Thanks for the quick response!

Good to know what those 500 errors are, at least I can rest easy about that one.

As far as the SD card goes, its relatively new and nothing with a lot of IO has been done to it minus a few formattings to test different RPi OS’s and such.

It is one of the Samsung 32GB Class 10 SDHC cards (http://www.amazon.com/Samsung-Class-Adapter-MB-MP32DA-AM/dp/B00IVPU786) so I was hoping that these would be a bit more relaible than most.

I can try going for a fresh formatting. Would you recommend stepping back to Wheezy to be sure that it isn’t OS related?

Did you overclock the RPi2? Could lead to odd behavior. Also, ample power for connected devices? No need I’m aware of to go back to wheezy.

Yea I actually did the provided overclock of 1000mhz through raspi-config. I didn’t seem to have issues with that before when i had a retropie installation and was playing emulated games and the like. But for now I suppose I’ll leave it stock since I’m not too sure the extra clock speed is going to gain me much on an openhab box.

Flashing a fresh jessie build now. Will keep you updated.

Thanks again for the quick responses. much appreciated

FYI So far so good, fresh install, fresh configuration. Openhab running with 13h uptime. knocks on wood. Thanks again for your help!!

Great! Hope it remains stable.