ELK problems arising in the course of building and Solutions Summary

Build problems arising in the course

elasticsearch error to start the process [1]

ERROR: [1] bootstrap checks failed
[1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, d                                                                                                                           iscovery.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 ne                                                                                                                           w native processes can be started

Solution

#修改config/elasticsearch.yml下约第23行，放开node.name注释，可更改名称
node.name: node-1

elasticsearch startup error [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

Solution

#打开第68行注释，ip替换host1等，多节点请添加多个ip地址，单节点可写按默认来
#配置以下三者，最少其一
#[discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes]
cluster.initial_master_nodes: ["node-1"] #这里的node-1为node-name配置的值

###### ###### ###### ###### ###### ###### ###### ######

Elasticsearch inaccessible by external ip

Solution

#修改config/elasticsearch.yml下约第55行,修改为当前es地址或0.0.0.0
network.host: 0.0.0.0

###### ###### ###### ###### ###### ###### ###### ######

Failed to clear cache for realms [[]]

No solution has already been put on the official github issue of

###### ###### ###### ###### ###### ###### ###### ######

[status][plugin:[email protected]] Status changed from yellow to green - Ready

This problem only occurs in the monomer ELK, please disregard

###### ###### ###### ###### ###### ###### ###### ######

max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Solution:

Temporary solution: switch the root user execute the following command

# sysctl -w vm.max_map_count=262144

Permanent Solution: In the /etc/sysctl.conf file add the line

# echo "vm.max_map_count=262144" > /etc/sysctl.conf
# sysctl -p  #使修改立即生效

View modify the results:

# sysctl -a|grep vm.max_map_count

display:

vm.max_map_count = 262144

###### ###### ###### ###### ###### ###### ###### ######

ERROR: bootstrap checks failed
memory locking requested for elasticsearch process but memory is not locked

This is because the lock has been set memory parameters bootstrap.memory_lock = true, notes the link given here before I https://www.cnblogs.com/hellxz/p/11009634.html

To be continued