为了账号安全,请及时绑定邮箱和手机立即绑定

kibana启动报错 连接elasticsearch

/ 猿问

kibana启动报错 连接elasticsearch

慕圣7574856 2019-08-08 14:21:57

log   [05:40:32.521] [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   [05:40:32.524] [info][status][plugin:encrypted_saved_objects@7.2.1] Status changed from uninitialized to green - Ready

  log   [05:40:32.559] [info][status][plugin:snapshot_restore@7.2.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch

  log   [05:40:32.564] [info][status][plugin:data@7.2.1] Status changed from uninitialized to green - Ready

  log   [05:40:33.403] [info][status][plugin:timelion@7.2.1] Status changed from uninitialized to green - Ready

  log   [05:40:33.412] [info][status][plugin:ui_metric@7.2.1] Status changed from uninitialized to green - Ready

  log   [05:40:37.011] [info][status][plugin:elasticsearch@7.2.1] Status changed from yellow to green - Ready

  log   [05:40:37.353] [error][status][plugin:xpack_main@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.354] [error][status][plugin:graph@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.356] [error][status][plugin:spaces@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.356] [error][status][plugin:searchprofiler@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.357] [error][status][plugin:ml@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.358] [error][status][plugin:tilemap@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.358] [error][status][plugin:watcher@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.359] [error][status][plugin:grokdebugger@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.360] [error][status][plugin:logstash@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.361] [error][status][plugin:beats_management@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.362] [error][status][plugin:maps@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.363] [error][status][plugin:index_management@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.364] [error][status][plugin:index_lifecycle_management@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.365] [error][status][plugin:rollup@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.366] [error][status][plugin:remote_clusters@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.367] [error][status][plugin:cross_cluster_replication@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:37.368] [error][status][plugin:snapshot_restore@7.2.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:43.813] [warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection.

  log   [05:40:44.191] [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   [05:40:45.379] [error][status][plugin:reporting@7.2.1] Status changed from uninitialized to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:45.840] [error][status][plugin:security@7.2.1] Status changed from green to red - [data] Elasticsearch cluster did not respond with license information.

  log   [05:40:54.304] [warning][reporting] The Reporting plugin encountered issues launching Chromium in a self-test. You may have trouble generating reports: [[object Object]]

  log   [05:40:54.305] [warning][reporting] See Chromium's log output at "/soft/ElasticSearch/kibana-7.2.1-linux-x86_64/data/headless_shell-linux/chrome_debug.log"

  log   [05:40:54.318] [warning][reporting] Reporting plugin self-check failed. Please check the Kibana Reporting settings. Error: Could not close browser client handle!


查看完整描述

4 回答

已采纳
?
慕虎0359979

有解决掉吗,我也遇到这个问题了

查看完整回答
反对 回复 2019-08-22
?
吃屎崽

咋解决 我也没解决

查看完整回答
2 反对 回复 2019-09-26
?
慕粉3775789

我也没有解决

查看完整回答
1 反对 回复 2019-09-27
?
慕斯4328264

不要看kibana的日志,看es的日志,设置cluster和node名就可以了

查看完整回答
反对 回复 2019-09-30

添加回答

回复

举报

0/150
提交
取消
意见反馈 帮助中心 APP下载
官方微信