Java fatal error with elasticsearch and kibana

Elastic Stack Elasticsearch
1

I'm setting up the elk for the first time so it hasnt worked yet. I start up elasticsearch with no issues but when kibana starts up it crashes java at the same point every time. It looks like it is once the kibana index starts. Any ideas what could cause this?

Current setup on raspberry pi 2:
arch linux os:
linux alarmpi 4.1.20-3-ARCH #1 SMP Wed Mar 23 19:01:10 MDT 2016 armv7l GNU/Linux
Java:
jdk7-openjdk 7.u99_2.6.5-1
jre7-openjdk 7.u99_2.6.5-1
jre7-openjdk-headless 7.u99_2.6.5-1
elk:
elasticsearch-2.3.1
kibana-4.5.0-linux-x86
logstash-2.3.2

Here's the error I'm getting

2016-04-28 17:40:46,582][INFO ][node ] [Coachwhip] starting ...
[2016-04-28 17:40:47,457][INFO ][transport ] [Coachwhip] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}, {[::1]:9300}
[2016-04-28 17:40:47,507][INFO ][discovery ] [Coachwhip] elasticsearch/TWVnZ-xpQNKcAVIQ5tod_Q
(node:31526) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
[2016-04-28 17:40:50,817][INFO ][cluster.service ] [Coachwhip] new_master {Coachwhip}{TWVnZ-xpQNKcAVIQ5tod_Q}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2016-04-28 17:40:50,931][INFO ][http ] [Coachwhip] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}, {[::1]:9200}
[2016-04-28 17:40:50,933][INFO ][node ] [Coachwhip] started
[2016-04-28 17:40:51,288][INFO ][gateway ] [Coachwhip] recovered [1] indices into cluster_state
[2016-04-28 17:40:54,573][INFO ][cluster.routing.allocation] [Coachwhip] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana][0]] ...]).
log [17:41:00.448] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready
log [17:41:00.674] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [17:41:00.836] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready
log [17:41:00.865] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready
log [17:41:00.891] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready
log [17:41:00.914] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready
log [17:41:00.936] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready
log [17:41:00.962] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready
log [17:41:01.020] [info][listening] Server running at http://0.0.0.0:5601
log [17:41:01.435] [info][status][plugin:elasticsearch] Status changed from yellow to green - Kibana index ready

A fatal error has been detected by the Java Runtime Environment:

Internal Error (cppInterpreter_arm.S:2625), pid=31490, tid=620602480

fatal error: *** Unimplemented opcode: 232 =

JRE version: OpenJDK Runtime Environment (7.0_99) (build 1.7.0_99-b00)

Java VM: OpenJDK Zero VM (24.95-b01 mixed mode linux-arm )

Derivative: IcedTea 2.6.5

Distribution: Custom build (Fri Apr 1 06:35:21 MDT 2016)

Core dump written. Default location: /usr/share/elasticsearch/logs/core or core.31490

An error report file with more information is saved as:

/usr/share/elasticsearch/logs/hs_err_pid31490.log

If you would like to submit a bug report, please include

instructions on how to reproduce the bug and visit:

http://icedtea.classpath.org/bugzilla

2

Hi,

this already came up earlier: openJDK on ARM crashes Elastic

The problem is that your JVM implementation does not know what to do with a specific bytecode instruction (opcode 232). The funny thing is that the JVM specification does not define such an opcode so I guess bytecode parsing already tripped earlier (although this is really just a wild guess). You should either ask in an Icedtea forum or file a bug at the Icedtea bugzilla.

Daniel