ELK搭建过程中出现的问题与解决方法汇总
搭建过程中出现的问题
elasticsearch启动过程中报错【1】
ERROR: [1] bootstrap checks failed
[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured
[2019-06-03T07:05:44,761][INFO ][o.e.n.Node ] [hz] stopping ...
[2019-06-03T07:05:44,788][INFO ][o.e.n.Node ] [hz] stopped
[2019-06-03T07:05:44,788][INFO ][o.e.n.Node ] [hz] closing ...
[2019-06-03T07:05:44,801][INFO ][o.e.n.Node ] [hz] closed
[2019-06-03T07:05:44,804][INFO ][o.e.x.m.p.NativeController] [hz] Native controller process has stopped - no new native processes can be started
解决办法
#修改config/elasticsearch.yml下约第23行，放开node.name注释，可更改名称
node.name: node-1
elasticsearch启动过程中报错【2】
ERROR: [1] bootstrap checks failed
[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured
解决办法
#打开第68行注释，ip替换host1等，多节点请添加多个ip地址，单节点可写按默认来
#配置以下三者，最少其一
#[discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes]
cluster.initial_master_nodes: ["node-1"] #这里的node-1为node-name配置的值
无法通过外部ip访问elasticsearch
解决办法
#修改config/elasticsearch.yml下约第55行,修改为当前es地址或0.0.0.0
network.host: 0.0.0.0
Failed to clear cache for realms [[]]
暂无解决办法，官方github上已经有人提issue了
[status][plugin:spaces@7.1.1] Status changed from yellow to green - Ready
这个问题只会出现在单体ELK中，无需理会
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
解决办法：
临时解决办法：切换root用户执行如下命令
# sysctl -w vm.max_map_count=262144
永久解决办法：在 /etc/sysctl.conf文件最后添加一行
# echo "vm.max_map_count=262144" >> /etc/sysctl.conf
# sysctl -p #使修改立即生效
查看修改结果：
# sysctl -a|grep vm.max_map_count
显示：
vm.max_map_count = 262144
ERROR: bootstrap checks failed
memory locking requested for elasticsearch process but memory is not locked
这是因为设置了锁定内存参数bootstrap.memory_lock=true，这里给出本人之前的笔记链接https://www.cnblogs.com/hellxz/p/11009634.html
docker版本的数据目录与日志目录持载到本地无法启动，提示Permission Denied
解决办法：
添加容器环境变量TAKE_FILE_OWNERSHIP=true
未完待续
