Graylog can't connect ES - timeout


(berekese) #1

Hi

I recently update last version Graylog and I can’t connect ES, here logs:

Log graylog

2017-06-07T08:02:01.300+02:00 WARN  [BlockingBatchedESOutput] Error while waiting for healthy Elasticsearch cluster. Not flushing.
java.util.concurrent.TimeoutException: Write-active index didn't get healthy within timeout
        at org.graylog2.indexer.cluster.Cluster.waitForConnectedAndDeflectorHealthy(Cluster.java:226) ~[graylog.jar:?]
        at org.graylog2.indexer.cluster.Cluster.waitForConnectedAndDeflectorHealthy(Cluster.java:237) ~[graylog.jar:?]
        at org.graylog2.outputs.BlockingBatchedESOutput.flush(BlockingBatchedESOutput.java:121) [graylog.jar:?]
        at org.graylog2.outputs.BlockingBatchedESOutput.writeMessageEntry(BlockingBatchedESOutput.java:114) [graylog.jar:?]
        at org.graylog2.outputs.BlockingBatchedESOutput.write(BlockingBatchedESOutput.java:96) [graylog.jar:?]
        at org.graylog2.buffers.processors.OutputBufferProcessor$1.run(OutputBufferProcessor.java:191) [graylog.jar:?]
        at com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176) [graylog.jar:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
2017-06-07T08:02:01.315+02:00 INFO  [MongoIndexSet] There is no index target to point to. Creating one now.
2017-06-07T08:02:01.325+02:00 INFO  [IndexRetentionThread] Elasticsearch cluster not available, skipping index retention checks.

Log ES:

[2017-06-07 07:59:42,594][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:00:01,294][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:00:12,596][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:00:31,296][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:00:42,613][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:01:01,299][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:01:12,615][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:01:31,308][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:01:42,621][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:02:01,313][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:02:12,623][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]
[2017-06-07 08:02:31,325][DEBUG][action.admin.cluster.health] [Layla Miller] observer: timeout notification from cluster service. timeout setting [30s], time since start [30s]

I use same cluster_name and I can connect localhost to 9200

Thanks.


(berekese) #2

Solved. I upgraded to ES 2.X and I System -> Indices -> Default Index -> Maintenance -> Recalculate index ranges.


(system) #3

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