No Monitoring Data Found(cluster_stats not exist)

hello, when i visit kibana monitoring, No Monitoring Data Found is present, i found .monitoring-es-6-* indices doesn't have cluster_stats and es cluster master node show the java.lang.NullPointerException.

detail exception:

[2018-07-09T00:00:10,644][ERROR][o.e.x.m.c.c.ClusterStatsCollector] [esm3] collector [cluster_stats] failed to collect data
java.lang.NullPointerException: null
at org.elasticsearch.xpack.monitoring.collector.cluster.ClusterStatsCollector.doCollect(ClusterStatsCollector.java:119) ~[x-pack-6.1.2.jar:6.1.2]
at org.elasticsearch.xpack.monitoring.collector.Collector.collect(Collector.java:100) [x-pack-6.1.2.jar:6.1.2]
at org.elasticsearch.xpack.monitoring.MonitoringService$MonitoringExecution$1.doRun(MonitoringService.java:222) [x-pack-6.1.2.jar:6.1.2]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.1.2.jar:6.1.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_161]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_161]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:568) [elasticsearch-6.1.2.jar:6.1.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_161]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_161]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]

thanks advance!

Hi @laywin,

This is very strange. The code is failing at a simple check for the license to determine if we should be using means that we should warn about TLS being required (a static Cluster Alert):

For anything there to be null is very weird. Can you do a few things to explore this:

  1. GET /_xpack/license
  2. GET /_nodes/settings and search for security?

I have not heard of, nor seen this error before, so this is very odd.

Thanks,
Chris

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