Kibana 停止工作,现在服务器没有准备好,尽管 kibana.service 启动良好
Kibana stopped working and now server not getting ready although kibana.service starts up nicely
我的 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 插件。
参考资料:
- 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 进入描述的未定义状态,则需要简单地重新启动计算机。对于其他服务 运行.
的(虚拟或物理)机器来说,这当然是不可接受的
我的 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 插件。
参考资料:
- 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 进入描述的未定义状态,则需要简单地重新启动计算机。对于其他服务 运行.
的(虚拟或物理)机器来说,这当然是不可接受的