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 ...
随机推荐
- 【GIT-精讲】从零玩转Git/GitHub/GitLab
关于版本控制 一.什么是版本控制 版本控制(Version Control Systems)版本控制(Revision control)是一种软件工程技巧 在开发的过程中,确保由不同人所编辑的同一档案 ...
- linux下开启防火墙,允许通过的端口
1.查看防火墙状态 systemctl status firewalld 2.如果不是显示active状态,需要打开防火墙 systemctl start firewalld 3.# 查看所有已开放的 ...
- [LeetCode]287. 寻找重复数(二分)
题目 给定一个包含 n + 1 个整数的数组 nums,其数字都在 1 到 n 之间(包括 1 和 n),可知至少存在一个重复的整数.假设只有一个重复的整数,找出这个重复的数. 示例 1: 输入: [ ...
- 没使用Spring Cloud的版本管理导致Eureka服务无法注册到Eureka服务注册中心
创建了一个Eureka Server的服务注册集群(两个Eureka服务),都能相互注册,写了一个Eureka客户端服务无法注册到服务发现注册中心 注册中心1: 注册中心2: 服务正常: pom依赖文 ...
- 【好消息】博客迁移到github,求关注,求star,求支持
博客迁移到github 地址:https://github.com/dirkhe1051931999/hjBlog
- apisix网关-构建docker镜像构建及插件化开发
高能劝退:lua开发,适合小白看!!! 前段时间有个项目,用的java程序做网关,压测tps只有1k多点,惨不忍睹. 后来公司有个大佬改用apisix做网关,tps飙升到1w多. 于是对神奇的apis ...
- springcloud一些博文记录
自己搭建完整demo后看的一个系列博文https://my.oschina.net/u/3375733/following 现在看着这个系列的后期文章估计出差前不会看了 一个博主的系列的git地址和博 ...
- hystrix(2) metrics
上一节讲到了hystrix提供的五个功能,这一节我们首先来讲hystrix中提供实时执行metrics信息的实现.为什么先讲metrics,因为很多功能都是基于metrics的数据来实现的,它是很多功 ...
- idea模拟前端向后台请求数据输出响应结果
tools-httpClient-Test restful web service 通过上述步骤之后出现如下图 1 表示通过哪种方式请求:2 请求数据的地址头部:3 请求数据的除了头部之后的地址:4, ...
- 一篇文章搞定 Nginx 反向代理与负载均衡
代理 要想弄明白反向代理,首先要知道啥是正向代理,要搞懂正向代理只需要知道啥是代理即可.代理其实就是一个中介,在不同事物或同一事物内部起到居间联系作用的环节.比如买票黄牛,房屋中介等等. 在互联网中代 ...