Anyhow, not sure where I should post this so if it’s in the wrong spot, I’dd appreciate someone correcting me.
So, about 2 months ago I Migrated my OH setup to a rpi2. Before I did this I didn’t have any issues with openhab crashing, now almost daily, but most days it will crash multiple times, other times it will run for a week or so without crashing.
this is what the terminal says:
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x7655a07c, pid=3404, tid=1946682480
JRE version: Java™ SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
Aborted
./start.sh: 34: ./start.sh: -Djava.compiler=NONE: not found
./start.sh: 35: ./start.sh: -Xrunjdwp:transport=dt_socket,address=8001,server=y,suspend=n: not found
Whilst I have little solid evidence to prove that this is a solution, I made the recommended changes regarding the tmpfs and reduced the overclock on my RPi2 and it’s been solid ever since.
I don’t understand, the “do not overclock” part, in raspi-config the max overclock setting is rpi2 1000mhz, isn’t this the correct setting for a pie 2?
and another followup question, if I install the oracle JDK will I need to remove the previous jdk?
and can you point me to a guide of doing so?
Thank You for your advice, I modified my tmpfs file, I left the overclock setting at rpi2 because it’s a pie 2, hopefully this works, only time will tell. but Thank you very much for you efforts.
$ 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)
Odd things can happen if you’re not at the standard clock settings. Possibly other causes for crashing, too. FTR, I never see JVM crashes on my RPi2 setups with openHAB.
OK, thank you very much for your help, I will clock it back to standard specs. It seems like it’s been solid since I modified my tempfs file, but I probably don’t really need the extra 100mhz rather be safe. Thanks again for your help