New ES 5.4.0 shows errors when starting with Docker


#1

I start ES 5.4.0 in Docker container with command

docker run -d --name elasticsearch --ulimit nofile=65536:65536 -p 9200:9200  \
    -e "bootstrap.system_call_filter=false" -e "xpack.security.enabled=false" \
    -v /opt/elasticsearch/data/:/usr/share/elasticsearch/data/ \
    docker.elastic.co/elasticsearch/elasticsearch:5.4.0

But in ES logs I can see the errors

[2017-05-11T16:33:34,312][INFO ][o.e.n.Node               ] [gquW_rz] started
[2017-05-11T16:33:34,883][ERROR][o.e.x.m.c.i.IndexRecoveryCollector] [gquW_rz] collector [index-recovery] failed to collect data
org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];
        at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:165) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.admin.indices.recovery.TransportRecoveryAction.checkGlobalBlock(TransportRecoveryAction.java:114) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.admin.indices.recovery.TransportRecoveryAction.checkGlobalBlock(TransportRecoveryAction.java:52) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction$AsyncAction.<init>(TransportBroadcastByNodeAction.java:256) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction.doExecute(TransportBroadcastByNodeAction.java:234) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction.doExecute(TransportBroadcastByNodeAction.java:79) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:170) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:142) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:84) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.client.node.NodeClient.executeLocally(NodeClient.java:83) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.client.node.NodeClient.doExecute(NodeClient.java:72) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:408) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.client.FilterClient.doExecute(FilterClient.java:67) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.xpack.security.InternalClient.doExecute(InternalClient.java:84) ~[?:?]
        at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:408) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.client.support.AbstractClient$IndicesAdmin.execute(AbstractClient.java:1256) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:80) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:54) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.ActionRequestBuilder.get(ActionRequestBuilder.java:69) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.xpack.monitoring.collector.indices.IndexRecoveryCollector.doCollect(IndexRecoveryCollector.java:65) ~[x-pack-5.4.0.jar:5.4.0]
        at org.elasticsearch.xpack.monitoring.collector.Collector.collect(Collector.java:83) [x-pack-5.4.0.jar:5.4.0]
        at org.elasticsearch.xpack.monitoring.MonitoringService$MonitoringExecution$1.doRun(MonitoringService.java:195) [x-pack-5.4.0.jar:5.4.0]

[2017-05-11T16:33:34,968][ERROR][o.e.x.m.c.i.IndexStatsCollector] [gquW_rz] collector [index-stats] failed to collect data
org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];
        at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:165) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.admin.indices.stats.TransportIndicesStatsAction.checkGlobalBlock(TransportIndicesStatsAction.java:70) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.admin.indices.stats.TransportIndicesStatsAction.checkGlobalBlock(TransportIndicesStatsAction.java:47) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction$AsyncAction.<init>(TransportBroadcastByNodeAction.java:256) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction.doExecute(TransportBroadcastByNodeAction.java:234) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction.doExecute(TransportBroadcastByNodeAction.java:79) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:170) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:142) ~[elasticsearch-5.4.0.jar:5.4.0]
        at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:84) ~[elasticsearch-5.4.0.jar:5.4.0]

[2017-05-11T16:33:41,360][INFO ][o.e.g.GatewayService     ] [gquW_rz] recovered [10] indices into cluster_state
[2017-05-11T16:33:46,538][INFO ][o.e.c.r.a.AllocationService] [gquW_rz] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.monitoring-data-2][0], [.monitoring-es-2-2017.05.10][0]] ...]).
[2017-05-11T16:33:51,238][INFO ][o.e.m.j.JvmGcMonitorService] [gquW_rz] [gc][24] overhead, spent [330ms] collecting in the last [1s]
[2017-05-11T16:34:27,904][INFO ][o.e.m.j.JvmGcMonitorService] [gquW_rz] [gc][young][59][18] duration [713ms], collections [1]/[1s], total [713ms]/[5.5s], memory [157.3mb]->[90.8mb]/[1.9gb], all_pools {[young] [65.7mb]->[15.7kb]/[66.5mb]}{[survivor] [8.3mb]->[6.9mb]/[8.3mb]}{[old] [83.2mb]->[83.8mb]/[1.9gb]}
[2017-05-11T16:34:27,907][WARN ][o.e.m.j.JvmGcMonitorService] [gquW_rz] [gc][59] overhead, spent [713ms] collecting in the last [1s]

But the same command works good for ES 5.3.0.
Did I miss anything when starting new version of ES?

Also, Monitoring page in Kibana shows

Fatal Error
Monitoring: Error 400 Bad Request: Cannot read property 'type' of null

Version: 5.4.0
Build: 15063

#2

It also says about Kibana version mismatch, though I am using 5.4.0 version for everything:

[2017-05-11T20:00:50,399][WARN ][o.e.x.w.e.ExecutionService] [gquW_rz] Failed to execute watch [aSpGYVC5RH2_C5Yh01RYwQ_logstash_version_mismatch_b316ecde-7279-4192-bdb3-d01b3d9da1da-2017-05-11T19:59:44.039Z]
[2017-05-11T20:01:20,013][ERROR][o.e.x.w.i.s.ExecutableSimpleInput] [gquW_rz] failed to execute [search] input for watch [aSpGYVC5RH2_C5Yh01RYwQ_kibana_version_mismatch], reason [java.util.concurrent.TimeoutException: Timeout waiting for task.]
[2017-05-11T20:01:20,526][INFO ][o.e.m.j.JvmGcMonitorService] [gquW_rz] [gc][8452] overhead, spent [343ms] collecting in the last [1.1s]
[2017-05-11T20:01:50,527][ERROR][o.e.x.w.i.s.ExecutableSimpleInput] [gquW_rz] failed to execute [search] input for watch [aSpGYVC5RH2_C5Yh01RYwQ_kibana_version_mismatch], reason [java.util.concurrent.TimeoutException: Timeout waiting for task.]
[2017-05-11T20:01:50,528][WARN ][o.e.x.w.e.ExecutionService] [gquW_rz] Failed to execute watch [aSpGYVC5RH2_C5Yh01RYwQ_kibana_version_mismatch_d5d9b42e-be4e-4eb1-8559-67fd5b20630c-2017-05-11T20:00:43.833Z]

(system) #3

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