Kibana服务器还没有准备好

Question

我刚刚在RHEL 8上安装了Kibana7.3。Kibana服务处于活动状态（正在运行）。
当我卷曲到http://localhost:5601时，我收到了Kibana服务器还没有准备好消息。我的Elasticsearch实例在另一台服务器上，它正在成功响应我的请求。我已经用它更新了kibana.yml

elasticsearch.hosts：["超文本传输协议：//EXTERNAL-IP-ADDRESS-OF-ES： 9200"]

我可以从互联网上访问elasticsearch并回复：

{
  "name" : "ip-172-31-21-240.ec2.internal",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "y4UjlddiQimGRh29TVZoeA",
  "version" : {
    "number" : "7.3.1",
    "build_flavor" : "default",
    "build_type" : "rpm",
    "build_hash" : "4749ba6",
    "build_date" : "2019-08-19T20:19:25.651794Z",
    "build_snapshot" : false,
    "lucene_version" : "8.1.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

sudo systemctl status kibana的结果是：

● kibana.service - Kibana
   Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2019-09-19 12:22:34 UTC; 24min ago
 Main PID: 4912 (node)
    Tasks: 21 (limit: 4998)
   Memory: 368.8M
   CGroup: /system.slice/kibana.service
           └─4912 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-size>

Sep 19 12:46:42 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0>
Sep 19 12:46:42 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0>
Sep 19 12:46:43 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0>
Sep 19 12:46:43 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0>
Sep 19 12:46:43 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0>
Sep 19 12:46:44 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0

“sudo journalctl——kibana单位”的结果

Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"Unable to revive >
Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"No living connect>
Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","task_manager"],"pid":1356,"message":"PollError No Living connec>
Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"Unable to revive >
Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"No living connect>

你知道问题出在哪里吗？

Answer 1

可能不是这个问题的解决方案

在我的例子中，kibana和elasticsearch的版本与我使用docker的方式不兼容，我只是重新创建了这两个版本，但使用了相同的版本（7.5.1）

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

Answer 2

该错误可能与elastic有关。主机设置。以下步骤和步骤对我有效：

1. 打开/etc/elasticsearch/elasticsearch。yml文件并检查以下设置：

#网络。主机：本地主机

2.打开/etc/kibana/kibana。yml归档并检查设置并检查：

#elasticsearch。主持人：[”http://localhost:9200“]

问题是kibana无法在本地访问elasticsearch。

Answer 3

我曾在将Elasticsearch从v6升级到v7时遇到过同样的问题。

删除. kibana*索引修复了问题：

curl --request DELETE 'http://elastic-search-host:9200/.kibana*'