Kibana 5.6.4 x-pack failing - seeing errors in elasticsearch when trying to create index in Kibana


#1

We are using Kibana 5.6.4, ES 5.6.4 with x-pack on CentOS 7.3+. We cannot see indexes in Kibana that we created successfully in ES. As soon as we try to create an index in Kibana, we see errors below. We confirmed ES is indexing our ingested data through transport-couchbase correctly. Anyone experienced this?

Thanks!

[2018-01-06T16:21:16,416][INFO ][o.e.t.c.CouchbaseTransportMetrics] type=TIMER, name=revsDiff, count=1278, min=0.244297, max=25.897516, mean=4.843903196518005, stddev=5.109436806398951, median=0.451525, p75=9.998834, p95=10.807771, p98=12.006713, p99=17.498394, p999=19.547207, mean_rate=1.3307003502628765, m1=1.1303357716837432, m5=1.1078391578898665, m15=0.8168468328140145, rate_unit=events/second, duration_unit=milliseconds
[2018-01-06T16:21:21,137][ERROR][o.e.x.w.t.s.ExecutableScriptTransform] [-hpDNhh] failed to execute [script] transform for [lauVDbv6SXm_gX7KBeD59g_elasticsearch_cluster_status_57c88ea1-c882-4e7b-b79e-8cc119061361-2018-01-06T22:21:21.128Z]
org.elasticsearch.script.ScriptException: runtime error
	at org.elasticsearch.painless.PainlessScript.convertToScriptException(PainlessScript.java:101) ~[?:?]
	at org.elasticsearch.painless.PainlessScript$Script.execute(def state = 'red';if (ctx.vars.fails_check){state = ctx.payload.check.hits.hits[0]._source.cluster_state.status;}if (ctx.vars.not_resolved){ctx.payload = ctx.payload.alert.hits.hits[0]._source;if (ctx.vars.fails_check == false) {ctx.payload.resolved_timest ...:767) ~[?:?]
	at org.elasticsearch.painless.ScriptImpl.run(ScriptImpl.java:133) ~[?:?]
	at org.elasticsearch.xpack.watcher.transform.script.ExecutableScriptTransform.doExecute(ExecutableScriptTransform.java:76) ~[x-pack-5.6.4.jar:5.6.4]
	at org.elasticsearch.xpack.watcher.transform.script.ExecutableScriptTransform.execute(ExecutableScriptTransform.java:60) [x-pack-5.6.4.jar:5.6.4]
	at org.elasticsearch.xpack.watcher.transform.script.ExecutableScriptTransform.execute(ExecutableScriptTransform.java:41) [x-pack-5.6.4.jar:5.6.4]
	at org.elasticsearch.xpack.watcher.execution.ExecutionService.executeInner(ExecutionService.java:408) [x-pack-5.6.4.jar:5.6.4]
	at org.elasticsearch.xpack.watcher.execution.ExecutionService.execute(ExecutionService.java:282) [x-pack-5.6.4.jar:5.6.4]
	at org.elasticsearch.xpack.watcher.execution.ExecutionService$WatchExecutionTask.run(ExecutionService.java:499) [x-pack-5.6.4.jar:5.6.4]
	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569) [elasticsearch-5.6.4.jar:5.6.4]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_152]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_152]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
Caused by: java.lang.NullPointerException
	at org.elasticsearch.painless.DefBootstrap$PIC.checkClass(DefBootstrap.java:138) ~[?:?]
	at org.elasticsearch.painless.PainlessScript$Script.execute(def state = 'red';if (ctx.vars.fails_check){state = ctx.payload.check.hits.hits[0]._source.cluster_state.status;}if (ctx.vars.not_resolved){ctx.payload = ctx.payload.alert.hits.hits[0]._source;if (ctx.vars.fails_check == false) {ctx.payload.resolved_timest ...:688) ~[?:?]
	... 11 more

(Thomas Neirynck) #2

hi @ataustin,

I'm not familiar with the error, but it seems like it is failing on a painless-script.

Are you trying to create an "index pattern" in Kibana and then see this error? Or is this after an upgrade from an earlier version?


#3

Thanks for your response. This is a fresh new install and I'm trying to create a new Kibana index that has a pattern that matches the one created in ES for transport-couchbase


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.