elasticsearch Kibana和elasticsearch状态为活动状态，我可以通过浏览器访问elasticsearch，但Kibana给出了错误信息

我在google实例上安装了kibana和elasticsearch，elasticsearch运行良好。但当对kibana执行curl命令时，它会给出一条错误消息

    curl -X GET "10.128.0.26:9200/"
{
"name" : "node-1",
"cluster_name" : "ElasticsearchStaging",
"cluster_uuid" : "r-A1o-coQlWUWeoXIFa5gw",
"version" : {
"number" : "7.3.0",
"build_flavor" : "default",
"build_type" : "deb",
"build_hash" : "de777fa",
"build_date" : "2019-07-24T18:30:11.767338Z",
"build_snapshot" : false,
"lucene_version" : "8.1.0",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}

这是我给kibana的信息

curl -X GET "10.128.0.26:5601/"
Kibana server is not ready yet

kibana.log文件：

07T10:17:47Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:47Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:47Z","tags":["warning","task_manager"],"pid":6590,"message":"PollError No Living connections"}
07T10:17:48Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:48Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:50Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:50Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:50Z","tags":["warning","task_manager"],"pid":6590,"message":"PollError No Living connections"}
07T10:17:51Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:51Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:53Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:53Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:53Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:53Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:53Z","tags":["warning","task_manager"],"pid":6590,"message":"PollError No Living connections"}
07T10:17:56Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:56Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:56Z","tags":["warning","elasticsearch","data"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:56Z","tags":["warning","elasticsearch","data"],"pid":6590,"message":"No living connections"}
07T10:17:56Z","tags":["license","warning","xpack"],"pid":6590,"message":"License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluation from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. Error: No Living connections"}
07T10:17:56Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:56Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}
07T10:17:56Z","tags":["warning","task_manager"],"pid":6590,"message":"PollError No Living connections"}
07T10:17:58Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"Unable to revive connection: http://0.0.0.0:9200/"}
07T10:17:58Z","tags":["warning","elasticsearch","admin"],"pid":6590,"message":"No living connections"}

这是我的kibana.yml文件：

# Kibana is served by a back end server. This setting specifies the port to use.
server.port: 5601
# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: "10.128.0.26"
# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""
# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# This setting was effectively always `false` before Kibana 6.3 and will
# default to `true` starting in Kibana 7.0.
#server.rewriteBasePath: false
# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576
# The Kibana server's name.  This is used for display purposes.
server.name: "ironman"
# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["http://0.0.0.0:9200"]
# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
elasticsearch.preserveHost: true
# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.

kibana.index: ".kibana"

我还尝试了

/bin/kibana

这就是我得到的信息

Kibana should not be run as root. Use --allow-root to continue.

遵照指示

./bin/kibana --allow-root

我得到了这个信息：

 log   [09:53:13.146] [fatal][root] Error: Port 5601 is already in use. Another instance of Kibana may be running!
    at Root.shutdown (/usr/share/kibana/src/core/server/root/index.js:67:18)
    at Root.setup (/usr/share/kibana/src/core/server/root/index.js:46:18)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
 FATAL  Error: Port 5601 is already in use. Another instance of Kibana may be running!

尝试更改此选项：

elasticsearch.hosts: ["http://10.128.0.26:9200"]

尝试更改此选项：

elasticsearch.hosts: ["http://10.128.0.26:9200"]

---

是的，我试过了，但现在运行curl命令后，我什么也没有得到，另一件让我不安的事情是，如何在kibana

logging.dest:/var/log/kibana/kibana.log中生成日志文件在yml文件中设置完后，我的kibana停止工作了，但是你的Kibana现在可以工作了吗？先生，问题是如果我们暂时忘记日志，那么Kibana状态是活动的，当我运行
service Kibana status
时，它显示为活动运行，但在
curl
命令之后，它没有显示任何内容，甚至没有错误。然后我尝试查看日志文件，这就是我在yml文件中设置路径的原因，但现在kibana甚至不处于活动状态。
lsof-i:5601
命令PID用户FD类型设备大小/脱离节点名称节点2994 kibana 19u IPv4 28201 0t0 TCP弹性阶段vyakar.c.vyakar-staging.internal:5601（侦听）
我不确定您为什么要通过curl访问kibana。你能详细说明一下吗？是的，我试过了，但现在在运行curl命令后，我什么都没有得到，另一件让我不安的事情是，如何在kibana
logging.dest:/var/log/kibana/kibana.log
中生成日志文件在yml文件中设置好后，我的kibana就停止工作了，但是你的Kibana现在可以工作了吗？先生，问题是如果我们暂时忘记日志，那么Kibana状态是活动的，当我运行
service Kibana status
时，它显示为活动运行，但在
curl
命令之后，它没有显示任何内容，甚至没有错误。然后我尝试查看日志文件，这就是我在yml文件中设置路径的原因，但现在kibana甚至不处于活动状态。
lsof-i:5601
命令PID用户FD类型设备大小/脱离节点名称节点2994 kibana 19u IPv4 28201 0t0 TCP弹性阶段vyakar.c.vyakar-staging.internal:5601（侦听）
我不确定您为什么要通过curl访问kibana。你能详细说明一下吗？