- Platform information:
- OS: Debian Bullseye
- Java Runtime Environment:
openjdk version “11.0.13” 2021-10-19 LTS
OpenJDK Runtime Environment Zulu11.52+13-CA (build 11.0.13+8-LTS)
OpenJDK 64-Bit Server VM Zulu11.52+13-CA (build 11.0.13+8-LTS, mixed mode) - openHAB version: 3.2.0
- Issue of the topic:
For whatever reason I receive the followign error message, which makes it not possible to use openHAB in the moment.
2022-01-04 08:56:35.464 [ERROR] [hab.core.audio.internal.AudioServlet] - bundle org.openhab.core.audio:3.2.0 (154)[org.openhab.core.audio.internal.AudioServlet(61)] : The activate method has thrown an exception
java.lang.ClassFormatError: Incompatible magic value 3405688510 in class file sun/security/ssl/KeyUpdate$KeyUpdateKickstartProducer
It all started with a failed JSON request yesterday,
2022-01-04 08:56:35.464 [ERROR] [hab.core.audio.internal.AudioServlet] - bundle org.openhab.core.audio:3.2.0 (154)[org.openhab.core.audio.internal.AudioServlet(61)] : The activate method has thrown an exception
java.lang.ClassFormatError: Incompatible magic value 3405688510 in class file sun/security/ssl/KeyUpdate$KeyUpdateKickstartProducer
Apparently, the system restartet, and started to throw this exception:
022-01-03 22:27:46.997 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'de_DE'.
2022-01-03 22:27:50.562 [ERROR] [hab.core.audio.internal.AudioServlet] - bundle org.openhab.core.audio:3.2.0 (154)[org.openhab.core.audio.internal.AudioServlet(61)] : The activate method has thrown an exception
java.lang.ClassFormatError: Incompatible magic value 3405688510 in class file sun/security/ssl/KeyUpdate$KeyUpdateKickstartProducer
I reviewed the syslog and found the follwoing:
Jan 3 22:27:29 zotac karaf[1208]: #
Jan 3 22:27:29 zotac karaf[1208]: # A fatal error has been detected by the Java Runtime Environment:
Jan 3 22:27:29 zotac karaf[1208]: #
Jan 3 22:27:29 zotac karaf[1208]: # SIGSEGV (0xb) at pc=0x00007f1a0c0eb794, pid=1208, tid=1927
Jan 3 22:27:29 zotac karaf[1208]: #
Jan 3 22:27:29 zotac karaf[1208]: # JRE version: OpenJDK Runtime Environment Zulu11.52+13-CA (11.0.13+8) (build 11.0.13+8-LTS)
Jan 3 22:27:29 zotac karaf[1208]: # Java VM: OpenJDK 64-Bit Server VM Zulu11.52+13-CA (11.0.13+8-LTS, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Jan 3 22:27:29 zotac karaf[1208]: # Problematic frame:
Jan 3 22:27:29 zotac karaf[1208]: # V [libjvm.so+0x855794] InstanceKlass::find_method_index(Array<Method*> const*, Symbol const*, Symbol const*, Klass::OverpassLookupMode, Klass::StaticLookupMode, Klass::PrivateLookupMode) [clone .constprop.332]+0x44
Jan 3 22:27:29 zotac karaf[1208]: #
Jan 3 22:27:29 zotac karaf[1208]: # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
Jan 3 22:27:29 zotac karaf[1208]: #
Jan 3 22:27:29 zotac karaf[1208]: # An error report file with more information is saved as:
Jan 3 22:27:29 zotac karaf[1208]: # /var/lib/openhab/hs_err_pid1208.log
Jan 3 22:27:29 zotac karaf[1208]: [thread 2452 also had an error]
Jan 3 22:27:29 zotac karaf[1208]: [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x00007f1a0c65ff52]
Jan 3 22:27:29 zotac karaf[1208]: #
Jan 3 22:27:29 zotac karaf[1208]: # If you would like to submit a bug report, please visit:
Jan 3 22:27:29 zotac karaf[1208]: # http://www.azul.com/support/
Jan 3 22:27:29 zotac karaf[1208]: #
Jan 3 22:27:29 zotac systemd[1]: openhab.service: Main process exited, code=killed, status=6/ABRT
Jan 3 22:27:29 zotac systemd[1]: openhab.service: Failed with result 'signal'.
Jan 3 22:27:29 zotac systemd[1]: openhab.service: Consumed 13min 47.916s CPU time.
Jan 3 22:27:34 zotac systemd[1]: openhab.service: Scheduled restart job, restart counter is at 1.
Jan 3 22:27:34 zotac systemd[1]: Stopped openHAB - empowering the smart home.
Jan 3 22:27:34 zotac systemd[1]: openhab.service: Consumed 13min 47.916s CPU time.
Jan 3 22:27:34 zotac systemd[1]: Started openHAB - empowering the smart home.
A proper restart of the openhab service wasn’t possible. The server required a full reboot.
Anyone any idea?