Kibana服务器尚未就绪

时间:2020-01-13 13:02:24

标签: elasticsearch kibana elk

我配置了弹性搜索,Kibana和日志存储群集。 弹性搜索工作正常,但是Kibana显示错误,指出Kibana服务器未就绪。

日志显示

> x .kibana_task_manager_1."}
Jan 13 12:50:05 kibana-csi kibana[28007]: {"type":"log","@timestamp":"2020-01-13T12:50:05Z","tags":["info","migrations"],"pid":28007,"message":"Creating index .kibana_1."}
Jan 13 12:50:05 kibana-csi kibana[28007]: {"type":"log","@timestamp":"2020-01-13T12:50:05Z","tags":["warning","migrations"],"pid":28007,"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_task_manager_1/4qj7_j5URN6TW2Pvr5qk7w] already exists, with { index_uuid=\"4qj7_j5URN6TW2Pvr5qk7w\" & index=\".kibana_task_manager_1\" }"}
Jan 13 12:50:05 kibana-csi kibana[28007]: {"type":"log","@timestamp":"2020-01-13T12:50:05Z","tags":["warning","migrations"],"pid":28007,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_task_manager_1 and restarting Kibana."}
Jan 13 12:50:35 kibana-csi kibana[28007]: {"type":"log","@timestamp":"2020-01-13T12:50:35Z","tags":["warning","migrations"],"pid":28007,"message":"Unable to connect to Elasticsearch. Error: Request Timeout after 30000ms"}
Jan 13 12:50:38 kibana-csi kibana[28007]: {"type":"log","@timestamp":"2020-01-13T12:50:38Z","tags":["warning","migrations"],"pid":28007,"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_1/LDkaYE3JQH2hhq4Xb4uDZw] already exists, with { index_uuid=\"LDkaYE3JQH2hhq4Xb4uDZw\" & index=\".kibana_1\" }"}

需要帮助! 我也尝试删除

curl -XDELETE 'http://ElasticsarchIP:9200/.kibana_1' --header "content-type: application/JSON" -u elastic -p

4 个答案:

答案 0 :(得分:4)

首先,尝试删除版本索引,然后按照上述建议重新启动:

curl -XDELETE http://localhost:9200/.kibana_1 

systemctl重新启动Kibana

如果它不起作用,请验证您是否已创建版本索引,例如字节数相同,依此类推。然后删除原始的.kibana:

curl -XDELETE http://localhost:9200/.kibana

然后为其别名:

curl -X POST "localhost:9200/_aliases" -H 'Content-Type: application/json' -d' { "actions" : [ { "add" : { "index" : ".kibana_1", "alias" : ".kibana" } } ] }'

然后重新启动kibana。

答案 1 :(得分:2)

这是由于Elastic Search和Kibana之间的版本不匹配引起的,请在设置Elastic.co记录的Elastic search和Kibana版本矩阵时使用以下版本

https://www.elastic.co/support/matrix#matrix_compatibility

答案 2 :(得分:1)

我只是遵循了错误附带的建议:

如果没有其他Kibana实例尝试迁移,则可以过去 通过删除索引.kibana_task_manager_1并重新启动此消息 基巴纳语。

curl -XDELETE http://localhost:9200/.kibana_task_manager_1

然后我重新启动了Kibana

答案 3 :(得分:0)

如果您不在乎丢失仪表板/vizu:

curl -XDELETE http://localhost:9200/.kibana*

这是唯一的解决方案,就像elasticsearch一样,如果没有快照,您永远无法恢复数据


如果已经有 .kibana_1 索引,请检查 .kibana 别名是否也存在,或者创建它:

curl -XPUT https://XXXXX/.kibana_1/_alias/.kibana

(任务管理器索引也是如此)。