kinaba 安装踩坑: FATAL Error: [elasticsearch.url]: definition for this key is missing 转
操作系统:Linux
kibana 版本: 7.4.0
1. 在/etc/yum.repos.d/ 下新建 kibana.repo 配置 yum 源地址 内容如下:

[root@localhost yum.repos.d]# cat kibana.repo
[kibana-7.x]
name=Kibana repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md

2. 安装 kibana
sudo yum install kibana
3. 安装完成之后,kibana 的相关目录如下所示:

4. 修改配置文件 ,主要是添加 elasticsearch 的信息:
server.port: 5601
server.host: "127.0.0.1"
server.name: "tanklog"
elasticsearch.url: "http://127.0.0.1:9200"
5. 启动 kibana (由于 root 用户不能直接启动 kibana,可以新建一个用户专门用来管理 kibana,或者在启动命令后追加 --allow-root)
/usr/share/kibana/bin/kibana --allow-root
6. 然后会报错如下:
FATAL Error: [elasticsearch.url]: definition for this key is missing
7. 经过一波操作之后,发现需要将 url 换成 hosts,配置文件需要设置为如下所示:
需要用: elasticsearch.hosts, 而不是: elasticsearch.url
server.port: 5601
server.host: "127.0.0.1"
server.name: tanklog
elasticsearch.hosts: ["http://localhost:9200/"]
# elasticsearch.url: "http://localhost:9200"
8. kibana 本身没问题,启动成功时会出现如下日志:

[root@localhost kibana]# /usr/share/kibana/bin/kibana --allow-root
log [08:41:50.254] [info][plugins-system] Setting up [4] plugins: [security,translations,inspector,data]
log [08:41:50.263] [info][plugins][security] Setting up plugin
log [08:41:50.266] [warning][config][plugins][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml
log [08:41:50.266] [warning][config][plugins][security] Session cookies will be transmitted over insecure connections. This is not recommended.
log [08:41:50.325] [info][plugins][translations] Setting up plugin
log [08:41:50.326] [info][data][plugins] Setting up plugin
log [08:41:50.328] [info][plugins-system] Starting [3] plugins: [security,translations,data]
log [08:42:15.769] [warning][plugin] Skipping non-plugin directory at /usr/share/kibana/src/legacy/core_plugins/metric_vis
log [08:42:15.832] [warning][plugin] Skipping non-plugin directory at /usr/share/kibana/src/legacy/core_plugins/table_vis
log [08:42:15.833] [warning][plugin] Skipping non-plugin directory at /usr/share/kibana/src/legacy/core_plugins/tagcloud
log [08:42:15.910] [warning][plugin] Skipping non-plugin directory at /usr/share/kibana/src/legacy/core_plugins/vega
log [08:42:17.487] [info][status][plugin:kibana@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.494] [info][status][plugin:elasticsearch@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.496] [info][status][plugin:xpack_main@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.508] [info][status][plugin:telemetry@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.511] [info][status][plugin:graph@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.525] [info][status][plugin:monitoring@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.529] [info][status][plugin:spaces@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.563] [info][status][plugin:security@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.565] [info][status][plugin:searchprofiler@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.568] [info][status][plugin:ml@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.635] [info][status][plugin:tilemap@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.638] [info][status][plugin:watcher@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.654] [info][status][plugin:grokdebugger@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.660] [info][status][plugin:dashboard_mode@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.662] [info][status][plugin:logstash@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.670] [info][status][plugin:beats_management@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.689] [info][status][plugin:apm_oss@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.727] [info][status][plugin:apm@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.729] [info][status][plugin:code@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.731] [info][status][plugin:data@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.733] [info][status][plugin:visualizations@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.740] [info][status][plugin:interpreter@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.742] [info][status][plugin:tile_map@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.746] [info][status][plugin:task_manager@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.751] [info][status][plugin:maps@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.770] [info][status][plugin:canvas@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.776] [info][status][plugin:license_management@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.779] [info][status][plugin:cloud@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:17.781] [info][status][plugin:index_management@7.4.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [08:42:17.799] [info][status][plugin:console@7.4.0] Status changed from uninitialized to green - Ready

9. 由于我的 elasticsearch 版本是7.3.2, 与 kibana 版本不一致,所以启动过程中出现了 error, 需要升级 elasticsearch 版本为 7.4.0

g [08:42:18.088] [info][status][plugin:table_vis@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:18.090] [info][status][plugin:tagcloud@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:18.092] [info][status][plugin:vega@7.4.0] Status changed from uninitialized to green - Ready
log [08:42:18.096] [warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection.
log [08:42:19.041] [error][status][plugin:xpack_main@7.4.0] Status changed from yellow to red - This version of Kibana requires Elasticsearch v7.4.0 on all nodes. I found the following incompatible nodes in your cluster: v7.3.2 @ 192.168.1.27:9200 (192.168.1.27)
log [08:42:19.042] [error][status][plugin:graph@7.4.0] Status changed from yellow to red - This version of Kibana requires Elasticsearch v7.4.0 on all nodes. I found the following incompatible nodes in your cluster: v7.3.2 @ 192.168.1.27:9200 (192.168.1.27)

升级 elasticsearch 版本
sudo yum -y install elasticsearch-oss
10. 启动 kibana,查看日志信息,发现有很多 warn
[warning][config][plugins][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml
根据 warn 提示,在 kibana.yml 里面添加缺失的属性内容
xpack.reporting.encryptionKey: "a_random_string"
xpack.security.encryptionKey: "something_at_least_32_characters"
启动 kibana,且将启动日志收集到指定文件
/usr/share/kibana/bin/kibana --allow-root > /var/lib/kibana/kibana.log &
访问
原文 https://www.cnblogs.com/miaoying/p/11639437.html
kinaba 安装踩坑: FATAL Error: [elasticsearch.url]: definition for this key is missing 转的更多相关文章
- kinaba 安装踩坑: FATAL Error: [elasticsearch.url]: definition for this key is missing
操作系统:Linux kibana 版本: 7.4.0 1. 在/etc/yum.repos.d/ 下新建 kibana.repo 配置 yum 源地址 内容如下: [root@localhost ...
- Android Studio安装踩坑
title: Android Studio安装踩坑 date: 2018-09-07 19:31:32 updated: tags: [Android,Android Studio,坑] descri ...
- Nextcloud fpm 版在 Dokcer 下安装踩坑
安装 首先到 https://registry.hub.docker.com/_/nextcloud 获取 Nextcloud 的示例 docker-compose version: '2' volu ...
- Symfony没有安装依赖_PHP Fatal error: require(): Failed opening required
$ php bin/console server:run PHP Warning: require(D:\home\workspace\pd\app/../vendor/autoload.php): ...
- VNPY - windows 安装踩坑记录
twisted requires PyHamcrest>=, which is not ins grin requires argparse>=1.1, which is not inst ...
- python2用pip进行安装时报错Fatal error in launcher: Unable to create process using '"'
win7下python3和python2共存环境 用pip安装一个包执行pip2 install xxx的时候报错Fatal error in launcher: Unable to create p ...
- ubuntu 16.04 + eigen3 安装(解决 fatal error: Eigen/Core: No such file or directory)
1.安装 sudo apt-get install libeigen3-dev 2. 解决 fatal error: Eigen/Core: No such file or directory 当调用 ...
- deepin 安装scrapy安装出错:fatal error: Python.h 的解决办法
环境deepin Linux 15.7 Python3.6.5 今天重新装了deepin系统,需要重新安装scrapy,直接pip了一下,没成. 报错:fatal error: Python.h: 没 ...
- 全文搜索引擎 Elasticsearch 安装踩坑记录
一.安装 Elastic 需要 Java 8 环境.如果你的机器还没安装 Java 安装完 Java,就可以跟着官方文档安装 Elastic.直接下载压缩包比较简单. $ wget https://a ...
随机推荐
- numpy函数笔记(持续更新)
numpy函数笔记 np.isin用法 np.isin(a,b) 用于判定a中的元素在b中是否出现过,如果出现过返回True,否则返回False,最终结果为一个形状和a一模一样的数组.(注意:这里的a ...
- range如何倒序
for j in range(3,-2,-1): 表示对3进行每次加-1的操作,直到-2,但不包括-2 print(j) 打印出3 2 1 0 -1都换行展示的
- [GXYCTF2019]Ping Ping Ping wp
根据题目考虑是命令注入方面, 打开网页,使用?ip=127.0.0.1;ls查询存在文件 后尝试使用?ip=127.0.01;cat flag.php打开flag.php无果 尝试打开index.ph ...
- iOS面试关于http知识点basic-01-http
URL URL 的全称是 Uniform Resource Locator(统一资源定位符) 通过 1 个 URL,能找到互联网上唯一的 1 个资源 URL就是资源的地址.位置,互联网上的每个资源都有 ...
- 面试官问:Mybatis中的TypeHandler你用过吗?
持续原创输出,点击上方蓝字关注我吧 目录 前言 环境配置 什么是TypeHandler? 如何自定义? 如何将其添加到Mybatis中? XML文件中如何指定TypeHandler? 源码中如何执行T ...
- Lucene索引库维护、搜索、中文分词器
删除索引(文档) 需求 某些图书不再出版销售了,我们需要从索引库中移除该图书. 1 @Test 2 public void deleteIndex() throws Exception { 3 // ...
- Depthwise Separable Convolution(深度可分离卷积)的实现方式
按照普通卷积-深度卷积-深度可分离卷积的思路总结. depthwise_conv2d来源于深度可分离卷积,如下论文: Xception: Deep Learning with Depthwise Se ...
- SON Web Tokens 工具类 [ JwtUtil ]
pom.xml <dependency> <groupId>io.jsonwebtoken</groupId> <artifactId>jjwt< ...
- 时间轮算法在Netty和Kafka中的应用,为什么不用Timer、延时线程池?
大家好,我是yes. 最近看 Kafka 看到了时间轮算法,记得以前看 Netty 也看到过这玩意,没太过关注.今天就来看看时间轮到底是什么东西. 为什么要用时间轮算法来实现延迟操作? 延时操作 Ja ...
- spring aop 源码分析(二) 代理方法的执行过程分析
在上一篇aop源码分析时,我们已经分析了一个bean被代理的详细过程,参考:https://www.cnblogs.com/yangxiaohui227/p/13266014.html 本次主要是分析 ...