Elasticsearch 5.0.0 installation Common errors or problems __CENTOS6

Elasticsearch 5.0.0 installation Common errors or problems

Question one:
[2016-11-06t16:27:21,712] [WARN] [O.e.b.jnanatives] Unable to install Syscall filter:
Java.lang.UnsupportedOperationException:seccomp unavailable:requires kernel 3.5+ with Config_seccompandconfig_ SECCOMP_FILTERcompiledinatorg.elasticsearch.bootstrap.Seccomp.linuxImpl (seccomp.java:349) ~[ elasticsearch-5.0.0.jar:5.0.0]
At Org.elasticsearch.bootstrap.Seccomp.init (seccomp.java:630) ~[elasticsearch-5.0.0.jar:5.0.0]
Reason: A lot of mistakes, we do not need to panic, in fact, is only a warning, mainly because of your Linux version is too low caused.
Solution: 1, reinstall the new version of Linux System 2, warning does not affect the use, you can ignore
Question two: Error:bootstrap checks failed
Max file descriptors [4096] for elasticsearch process likely too low, increase to at least [65536]
Reason: Unable to create a local file problem, the maximum number of files that the user can create is too small
Solution: Switch to root, edit the limits.conf configuration file, and add something similar to the following:
Vi/etc/security/limits.conf
Add the following: * Soft nofile 65536
* Hard Nofile 131072
* Soft Nproc 2048
* Hard Nproc 4096 Note: * represents Linux all user names (such as Hadoop)
Save, exit, log back in to take effect
Question three: max number of threads [1024] for user [es] likely too down, increase to at least [2048] Reason: Unable to create the local thread problem, the user can create the maximum number of threads too small solution Case: Switch to root, enter LIMITS.D directory, modify 90-nproc.conf configuration file.
Vi/etc/security/limits.d/90-nproc.conf
Find the following:
* Soft Nproc 1024
#修改为
* Soft Nproc 2048
Question four: max virtual memory Areas Vm.max_map_count [65530] likely too low, increase to at least [262144] reason: Max dummy memory too small solution: Switch to R Under Oot users, modify the configuration file sysctl.conf
Vi/etc/sysctl.conf
Add the following configuration:
vm.max_map_count=655360
and execute the command:
Sysctl-p
Then restart the Elasticsearch to start the success.
Issue five: Elasticsearch boot could not find host or routing reason: Elasticsearch unicast configuration problem Solution: Check the configuration files in Elasticsearch VI config/elasticsearch.yml find the following configuration:
discovery.zen.ping.unicast.hosts:["192.168.**.**:9300", "192.168.**.**:9300"] in general, there is a problem with the configuration here, note the writing format
Question six: org.elasticsearch.transport.RemoteTransportException:Failed to deserialize exception response from stream
Reason: JDK version inconsistency between elasticsearch nodes
Solution: Elasticsearch Cluster Unified JDK Environment
Question seven: unsupported Major.minor version 52.0
Cause: JDK version problem is too low solution: Replace JDK version, ElasticSearch5.0.0 support jdk1.8.0
Question eight: bin/elasticsearch-plugin install license Error:unknown plugin license
Reason: ElasticSearch5.0.0 The plugin command has changed after the solution: Install all plugins with the latest command

Bin/elasticsearch-plugin Install X-pack

This article from: http://www.dajiangtai.com/community/18136.do?origin=csdn-geek&dt=1214, only for their own use to facilitate the search

Complement: Startup exception: Error:bootstrap checks failed
System call filters failed to install; Check the logs and fix your configuration or disable system call filters at your own

Problem reason: Because CENTOS6 does not support Seccomp, and ES5.2.1 default bootstrap.system_call_filter is true for detection, it causes detection to fail, which directly causes ES to fail to start. See: https://github.com/elastic/elasticsearch/issues/22899

Workaround: Configure Bootstrap.system_call_filter to False in elasticsearch.yml, and note that under memory:
Bootstrap.memory_lock:false
Bootstrap.system_call_filter:false