Kibana UI未启动,但容器已启动并正在运行

我正在将Elasticsearch以及Kibana从5.6.14升级到7.4.2

我的ES已启动并正在运行

在浏览器中命中http://localhost:9200/_cat/indices?v 给我下面的输出

health status index                    uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   .kibana_task_manager_1   joI0GprPTJaJX0h7CcEi8w   1   0          2            0     12.5kb         12.5kb
green  open   .apm-agent-configuration XJ2AF4NUQKivJ9gMZOHOfA   1   0          0            0       283b           283b
green  open   .kibana_2                2H66ezpOR7W5tTas3oxH1g   1   0          4            0     18.3kb         18.3kb
green  open   .kibana_1                IOEPzbfUSQO7u3sn-S7p6A   1   0          2            0      9.4kb          9.4kb

elasticsearch.yml的内容

http.host: 0.0.0.0
# Uncomment the following lines for a production cluster deployment
#transport.host: 0.0.0.0
#discovery.zen.minimum_master_nodes: 1
node.name: 'node-1'
discovery.seed_hosts: ["127.0.0.1","[::1]"]
cluster.initial_master_nodes: ["node-1"]
xpack.ml.enabled: false

试图启动kibana容器,容器已启动,但是在UI中  {“ statusCode”:404,“ error”:“ Not Found”,“ message”:“ Not Found”},有时kibana还没有准备好开始发送消息。

这是我的kibana.yml

server.host: "0.0.0.0"
server.basePath: "/clog"
server.rewriteBasePath: false
elasticsearch.hosts: [ "http://localhost:9200" ]
xpack.security.enabled: false
kibana.index: ".kibana"

我在日志中得到关注

log   [06:41:45.744] [info][status][plugin:oss_telemetry@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:45.747] [info][status][plugin:file_upload@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [06:41:45.752] [warning][encrypted_saved_objects] Generating a random key for xpack.encrypted_saved_objects.encryptionKey. To be able to decrypt encrypted saved objects attributes after restart,please set xpack.encrypted_saved_objects.encryptionKey in kibana.yml
  log   [06:41:45.755] [info][status][plugin:encrypted_saved_objects@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:45.787] [info][status][plugin:snapshot_restore@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [06:41:45.837] [info][status][plugin:kibana_react@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:45.840] [info][status][plugin:region_map@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:45.993] [info][status][plugin:timelion@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:46.000] [info][status][plugin:ui_metric@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:46.005] [info][status][plugin:markdown_vis@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:46.009] [info][status][plugin:metric_vis@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:46.013] [info][status][plugin:table_vis@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:46.018] [info][status][plugin:tagcloud@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:46.021] [info][status][plugin:vega@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:41:46.027] [warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection.
  log   [06:41:46.056] [info][status][plugin:elasticsearch@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.081] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: basic | status: active
  log   [06:41:47.089] [info][status][plugin:xpack_main@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.089] [info][status][plugin:graph@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.091] [info][status][plugin:searchprofiler@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.092] [info][status][plugin:ml@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.092] [info][status][plugin:tilemap@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.093] [info][status][plugin:watcher@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.094] [info][status][plugin:grokdebugger@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.094] [info][status][plugin:logstash@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.095] [info][status][plugin:beats_management@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.096] [info][status][plugin:index_management@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.097] [info][status][plugin:index_lifecycle_management@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.097] [info][status][plugin:rollup@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.098] [info][status][plugin:remote_clusters@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.099] [info][status][plugin:cross_cluster_replication@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.099] [info][status][plugin:file_upload@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.100] [info][status][plugin:snapshot_restore@7.4.2] Status changed from yellow to green - Ready
  log   [06:41:47.101] [info][kibana-monitoring][monitoring] Monitoring status upload endpoint is not enabled in Elasticsearch:Monitoring stats collection is stopped
  log   [06:41:47.127] [info][status][plugin:maps@7.4.2] Status changed from yellow to green - Ready
  log   [06:42:06.495] [warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart,please set xpack.reporting.encryptionKey in kibana.yml
  log   [06:42:06.513] [info][status][plugin:reporting@7.4.2] Status changed from uninitialized to green - Ready
  log   [06:42:06.683] [info][listening] Server running at http://0.0.0.0:5601
  log   [06:42:06.717] [info][server][Kibana][http] http server running at http://0.0.0.0:5601
  log   [06:42:06.725] [info][status][plugin:spaces@7.4.2] Status changed from yellow to green - Ready
  log   [06:42:06.732] [warning][telemetry] Error scheduling task,received [task:oss_telemetry-vis_telemetry]: version conflict,document already exists (current version [5]): [version_conflict_engine_exception] [task:oss_telemetry-vis_telemetry]: version conflict,document already exists (current version [5]),with { index_uuid="joI0GprPTJaJX0h7CcEi8w" & shard="0" & index=".kibana_task_manager_1" }
  log   [06:42:06.733] [warning][maps] Error scheduling telemetry task,received [task:Maps-maps_telemetry]: version conflict,document already exists (current version [5]): [version_conflict_engine_exception] [task:Maps-maps_telemetry]: version conflict,with { index_uuid="joI0GprPTJaJX0h7CcEi8w" & shard="0" & index=".kibana_task_manager_1" }

我在上面使用了node:10.15.2-alpine图像,并使用kibana-7.4.2-linux-x86_64添加了kibana7.4.2。 我也尝试使用docker.elastic.co/kibana/kibana:7.4.2仍然得到相同的错误日志。

请注意,我们没有使用x-pack的许可,因此我们需要在使用过x-pack的地方禁用它。我不知道错过了什么。任何帮助将不胜感激

you6251545 回答:Kibana UI未启动,但容器已启动并正在运行

我不确定这是否会有所帮助,但我认为我也遇到过类似的问题。您可以尝试像这样编辑elasticsearch.yml吗?

http.host: 0.0.0.0
# Uncomment the following lines for a production cluster deployment
#transport.host: 0.0.0.0
#discovery.zen.minimum_master_nodes: 1
node.name: 'node-1'
discovery.type=single-node
xpack.ml.enabled: false
本文链接:https://www.f2er.com/3139018.html

大家都在问