gpt4 book ai didi

elasticsearch - 尽管kibana.service正常启动,但Kibana停止工作,现在服务器未准备就绪

转载 作者:行者123 更新时间:2023-12-02 23:51:59 42 4
gpt4 key购买 nike

没有对我的Ubuntu(4.4.0-142-generic #168-Ubuntu SMP)进行任何重大系统更新,Kibana 7.2.0停止工作。我仍然可以使用sudo systemctl start kibana.service启动该服务,并且相应的状态看起来很好。只有警告,没有错误,这似乎不是问题所在:

# sudo systemctl status kibana.service 
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-07-10 09:43:49 CEST; 22min ago
Main PID: 14856 (node)
Tasks: 21
Memory: 583.2M
CPU: 1min 30.067s
CGroup: /system.slice/kibana.service
└─14856 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-size=65536 /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml

Jul 10 09:56:36 srv003 kibana[14856]: {"type":"log","@timestamp":"2019-07-10T07:56:36Z","tags":["warning","task_manager"],"pid":14856,"message":"The task maps_telemetry \"Maps-maps_telemetry\" is not cancellable."}

但是,当我在客户端计算机上访问 http://srv003:5601/时,我仍然只能看到(即使在等待20分钟之后):
Kibana server is not ready yet

在服务器 srv003本身上,我看到了
me@srv003:# curl -XGET http://localhost:5601/status -I
curl: (7) Failed to connect to localhost port 5601: Connection refused

这很奇怪,因为Kibana似乎真的在该端口上监听,并且防火墙出于测试目的而被禁用:
root@srv003# sudo lsof -nP -i | grep 5601
node 14856 kibana 18u IPv4 115911041 0t0 TCP 10.0.0.72:5601 (LISTEN)
root@srv003# sudo ufw status verbose
Status: inactive
kibana.service的日志中也没有可疑的东西:
root@srv003:/var/log# journalctl -u kibana.service | grep -A 99 "Jul 10 10:09:14"
Jul 10 10:09:14 srv003 systemd[1]: Started Kibana.
Jul 10 10:09:38 srv003 kibana[14856]: {"type":"log","@timestamp":"2019-07-10T08:09:38Z","tags":["warning","task_manager"],"pid":14856,"message":"The task maps_telemetry \"Maps-maps_telemetry\" is not cancellable."}

我的Elasticsearch仍在运行。在有关Kibana的相应日志文件中没有有趣的事情:
root@srv003:/var/log# cat elasticsearch/elasticsearch.log  |grep kibana
[2019-07-10T09:46:25,158][INFO ][o.e.c.m.MetaDataIndexTemplateService] [srv003] adding template [.kibana_task_manager] for index patterns [.kibana_task_manager]
[2019-07-10T09:47:32,955][INFO ][o.e.c.m.MetaDataCreateIndexService] [srv003] [.monitoring-kibana-7-2019.07.10] creating index, cause [auto(bulk api)], templates [.monitoring-kibana], shards [1]/[0], mappings [_doc]

现在我的选项已经用光了,希望有人能给我另一个提示。

编辑:我没有安装任何Kibana插件。

咨询来源:
  • How to fix "Kibana server is not ready yet" error when using AKS
  • Kibana service is running but can not access via browser to console
  • Why won't Kibana Node server start up?
  • https://discuss.elastic.co/t/failed-to-start-kibana-7-0-1/180259/3-最有前途的线程,但没人回答
  • https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-issue-after-upgrade-to-6-5-0/157021
  • https://discuss.elastic.co/t/kibana-server-not-ready/162075
  • 最佳答案

    如果Kibana进入描述的未定义状态,则需要简单地重新启动计算机。对于运行其他服务的(虚拟或物理)机器,这当然是 Not Acceptable 。

    关于elasticsearch - 尽管kibana.service正常启动,但Kibana停止工作,现在服务器未准备就绪,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/56966684/

    42 4 0
    Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
    广告合作:1813099741@qq.com 6ren.com