尽管kibana.service正常启动,但Kibana停止工作,现在服务器未准备就绪 [英] Kibana stopped working and now server not getting ready although kibana.service starts up nicely
问题描述
没有对我的Ubuntu进行任何重大系统更新( 4.4.0-142-通用#168-Ubuntu SMP
),Kibana 7.2.0停止工作。我仍然可以使用 sudo systemctl start kibana.service
启动服务,并且相应的状态看起来很好。只有警告,没有错误,这似乎不是问题所在:
Without any major system update of my Ubuntu (4.4.0-142-generic #168-Ubuntu SMP
), Kibana 7.2.0 stopped working. I am still able to start the service with sudo systemctl start kibana.service
and the corresponding status looks fine. There is only a warning and no error, this does not seem to be the issue:
# 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分钟之后):
Nevertheless, when I visit http://srv003:5601/
on my client machine, I keep seeing only (even after waiting 20 minutes):
Kibana server is not ready yet
在服务器上 srv003
本身,我看到
On the server srv003
itself, I see
me@srv003:# curl -XGET http://localhost:5601/status -I
curl: (7) Failed to connect to localhost port 5601: Connection refused
这很奇怪,因为Kibana似乎真的在监听该端口,并且防火墙已禁用出于测试目的:
This is a strange since Kibana seems to be really listening at that port and the firewall is disabled for testing purposes:
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
的日志中也没有可疑的东西:
There is nothing suspicious in the log of kibana.service
either:
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的相应日志文件中没有什么有趣的东西:
My Elasticsearch is still up and running. There is nothing interesting in the corresponding log files about 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]
现在我的选项有点用尽了,我希望有人能给我另一个提示。
Now I am running a bit out of options, and I hope somebody can give me another hint.
编辑:我没有安装任何Kibana插件。
I do not have any Kibana plugins installed.
咨询来源:
- 如何修复 Kibana服务器为n还没准备好使用AKS时发生错误
- Kibana服务正在运行,但无法通过浏览器访问控制台
- 为什么Kibana节点服务器无法启动?
- https://discuss.elastic.co/t/failed -to-start-kibana-7-0-1 / 180259/3 -最有前途的线程,但没人回答
- https://discuss.elastic。 co / t / kibana服务器尚未升级到6-5-0 / 157021之后仍是问题
- https://discuss.elasti c.co/t/kibana-server-not-ready/162075
- 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 - most promising thread, but nobody ever answered
- 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进入描述的未定义状态,则需要简单地重新启动计算机。对于运行其他服务的(虚拟或物理)计算机,这当然是不可接受的。
It looks like if Kibana enters the described undefined state, a simple reboot of the computer is necessary. This is of course not acceptable for a (virtual or physical) machine where other services are running.
这篇关于尽管kibana.service正常启动,但Kibana停止工作,现在服务器未准备就绪的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!