>
在CentOS 7.8.2003版本上新安装了elasticsearch和kibanaLinux
kibana服务显示kibana服务器尚未就绪
curl http://localhost:5601
Kibana server is not ready yet
curl http://127.0.0.1:9200
{
"name" : "elkserver1",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "_na_",
"version" : {
"number" : "7.9.2",
"build_flavor" : "default",
"build_type" : "rpm",
"build_hash" : "d34da0ea4a966c4e49417f2da2f244e3e97b4e6e",
"build_date" : "2020-09-23T00:45:33.626720Z",
"build_snapshot" : false,
"lucene_version" : "8.6.2",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
/usr/share/kibana/bin/kibana --version
7.9.2
systemctl status kibana
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; disabled; vendor preset: disabled)
Active: active (running) since Sat 2020-09-26 12:46:17 EDT; 9s ago
Main PID: 22390 (node)
CGroup: /system.slice/kibana.service
└─22390 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli
Sep 26 12:46:17 elkserver1 systemd[1]: Started Kibana.
Sep 26 12:46:23 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:23Z","tags":["warning","plugins-discovery"],"pid":22390,"message":"Expect plugin \"id\" in camelCase, but found: beats_management"}
Sep 26 12:46:23 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:23Z","tags":["warning","plugins-discovery"],"pid":22390,"message":"Expect plugin \"id\" in camelCase, but found: triggers_actions_ui"}
cat /etc/elasticsearch/elasticsearch.yml | grep 'network.host\|http.port'
network.host: localhost
http.port: 9200
cat /etc/kibana/kibana.yml | grep 'elasticsearch.hosts'
elasticsearch.hosts: ["http://localhost:9200"]
journalctl --follow --unit kibana
-- Logs begin at Sat 2020-09-26 08:45:46 EDT. --
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["warning","plugins","encryptedSavedObjects","config"],"pid":22390,"message":"Generating a random key for xpack.encryptedSavedObjects.encryptionKey. To be able to decrypt encrypted saved objects attributes after restart, please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml"}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["warning","plugins","ingestManager"],"pid":22390,"message":"Fleet APIs are disabled due to the Encrypted Saved Objects plugin using an ephemeral encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml."}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["warning","plugins","actions","actions"],"pid":22390,"message":"APIs are disabled due to the Encrypted Saved Objects plugin using an ephemeral encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml."}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["warning","plugins","alerts","plugins","alerting"],"pid":22390,"message":"APIs are disabled due to the Encrypted Saved Objects plugin using an ephemeral encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml."}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["info","plugins","monitoring","monitoring"],"pid":22390,"message":"config sourced from: production cluster"}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["warning","plugins","monitoring","monitoring"],"pid":22390,"message":"X-Pack Monitoring Cluster Alerts will not be available: X-Pack plugin is not installed on the Elasticsearch cluster."}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["info","savedobjects-service"],"pid":22390,"message":"Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved objects migrations..."}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["info","savedobjects-service"],"pid":22390,"message":"Starting saved objects migrations"}
Sep 26 12:46:35 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:46:35Z","tags":["warning","plugins","reporting","config"],"pid":22390,"message":"Chromium sandbox provides an additional layer of protection, but is not supported for Linux Centos 7.8.2003 OS. Automatically setting 'xpack.reporting.capture.browser.chromium.disableSandbox: true'."}
Sep 26 12:47:05 elkserver1 kibana[22390]: {"type":"log","@timestamp":"2020-09-26T16:47:05Z","tags":["warning","savedobjects-service"],"pid":22390,"message":"Unable to connect to Elasticsearch. Error: Request Timeout after 30000ms"}
@罗汉。谢谢你的指点。终于发现了问题。
curl http://127.0.0.1:9200
{
"name" : "elkserver1",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "_na_", >>> Cluster_uuid
"version" : {
"number" : "7.9.2",
"build_flavor" : "default",
"build_type" : "rpm",
"build_hash" : "d34da0ea4a966c4e49417f2da2f244e3e97b4e6e",
"build_date" : "2020-09-23T00:45:33.626720Z",
"build_snapshot" : false,
"lucene_version" : "8.6.2",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
[2020-09-28T13:29:56,862][WARN ][o.e.c.c.ClusterFormationFailureHelper] [elkserver1] master not discovered or elected yet, an election requires a node with id [8G5Afwq7Qkqs7vUjSGTAfg], have discovered [{elkserver1}{VKd5Aef5SzyKLDfWFCzEqQ}{IgEkTEsURfih_IKP299QWw}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=8201424896, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}] which is not a quorum; discovery will continue using [127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, 127.0.0.1:9305, [::1]:9301, [::1]:9302, [::1]:9303, [::1]:9304, [::1]:9305] from hosts providers and [{elkserver1}{VKd5Aef5SzyKLDfWFCzEqQ}{IgEkTEsURfih_IKP299QWw}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=8201424896, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}] from last-known cluster state; node term 1, last-accepted version 36 in term 1
我的elasticsearch服务器运行时有索引,比如说服务器XX。XXX。XXX。XXX:9200。 我在服务器ES集群XX中有索引。XXX。XXX。XXX:9200,我正试图在本地主机5601(Kibana)中为其创建仪表盘 在我的kibana.yml我有这样的配置: 在弹性搜索中。yml我有这个配置: 但我在运行kibana时遇到了这个错误。yml: 连接ECONNREFUSED超文本传输协
问题内容: 我在跟踪为什么无法连接到特定主机时遇到问题。 通过curl或浏览器,以下命令可以正常工作: 但是,如果我使用请求: 我得到: 在网络上,我仅看到客户端问好,服务器立即断开连接,因此似乎没有任何ssl或密码不兼容。(我希望这些都是SSL层错误)在这种情况下还有什么其他问题? 我在python 3.6.1上,请求2.14.2(带有安全性额外功能)。 问题答案: 该服务器以多种方式损坏。 一
问题内容: 我已经在RHEL7上安装了ES 7.5和Kibana 7.5,但是在启动Kibana并检查UI后,我看到了错误,“ Kibana服务器尚未准备好。” 检查Kibana日志,我发现它没有正确连接到ES。任何帮助表示赞赏! 这是 journalctl –unit kibana 的输出: Elasticsearch.yml Kibana.yml 另外,当我运行 ss -tunlp | gre
我已经在RHEL7上安装了ES 7.5和Kibana 7.5,但是在启动Kibana并检查UI之后,我看到了错误,“Kibana服务器还没有准备好。” 检查Kibana日志,我看到它没有正确连接到ES。感谢任何帮助! 以下是journalctl的输出——单位kibana: 弹性搜索。yml 基巴纳。yml 此外,当我在Kibana启动期间运行ss-tunlp|grep 5601时,我看到Kiban
我在SpringBoot 2.0中使用标准的HikariCP实现。1份申请书。但是过了一会儿,我一遍又一遍地犯同样的错误 HikariPool-1-连接不可用,请求在30000ms后超时 我首先检查了代码,如果有任何未关闭的连接或丢失的事务注释,但我没有找到任何东西。我也试图增加游泳池,减少我application.yml的时间,但这似乎没有任何效果。 奇怪的是,HikariCP似乎只创建了4个池
尝试使用Docker容器将Kibana连接到ES时出错: kibana-product-624|{"type":"log","@time戳":"2018-05-25T14:56:36Z","tags":["警告","elasticsearch","admin"],"pid": 1,"消息":"无法恢复连接:超文本传输协议://elasticsearch: 9200/"}kibana-product