Elasticsearch 5 common errors or problems with installing a deployment __elasticsearch

Question 1:

Uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException:java.lang.RuntimeException: Can not run Elasticsearch as root

Problem reason: Cannot start with root user
Solution: Switch to another user

Question 2:

Unable to install Syscall Filter:java.lang.UnsupportedOperationException:seccomp unavailable:requires kernel with Config_seccomp and Config_seccomp_filter compiled in Org.elasticsearch.bootstrap.SystemCallFilter.linuxImpl (Sy STEMCALLFILTER.JAVA:350) ~[elasticsearch-5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.SystemCallFilter.init (Sy stemcallfilter.java:638) ~[elasticsearch-5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.JNANatives.tryInstallSys Temcallfilter (jnanatives.java:215) [elasticsearch-5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.Natives.tryInst Allsystemcallfilter (natives.java:99) [elasticsearch-5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.Bootstrap.ini Tializenatives (bootstrap.java:111) [elasticsearch-5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.Bootstrap.setup (bootstrap.java:204) [elasticsearch-5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.Bootstrap.init (bootstrap.java:360) [elasticsearch- 5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.Elasticsearch.init (elasticsearch.java:123) [elasticsearch-5.4.0.jar:5.4.0]
        At Org.elasticsearch.bootstrap.Elasticsearch.execute (elasticsearch.java:114) [elasticsearch-5.4.0.jar:5.4.0] At Org.elasticsearch.cli.EnvironmentAwareCommand.execute (environmentawarecommand.java:67) [ ELASTICSEARCH-5.4.0.JAR:5.4.0] at org.elasticsearch.cli.Command.mainWithoutErrorHandling (command.java:122) [Elast
        ICSEARCH-5.4.0.JAR:5.4.0] at Org.elasticsearch.cli.Command.main (command.java:88) [elasticsearch-5.4.0.jar:5.4.0]  At Org.elasticsearch.bootstrap.Elasticsearch.main (elasticsearch.java:91) [elasticsearch-5.4.0.jar:5.4.0] at Org.elasticsearch.bootstrap.Elasticsearch.main (elasticsearch.java:84) [elasticsearch-5.4.0.jar:5.4.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 the Linux system
2, warning does not affect the use, you can ignore

Question 3:

Error:bootstrap checks failed
memory locking requested for Elasticsearch process but memory are not locked

Reason: Lock memory failed

Solution:
Switch to root, edit the limits.conf configuration file, and add something similar to the following:
sudo vim/etc/security/limits.conf

Add the following:
* Soft Memlock Unlimited
* Hard Memlock Unlimited
Note: * On behalf of all Linux user names

Save, exit, log back in to take effect
Temporary cancellation restrictions
Ulimit-l Unlimited

Question 4:

Error:bootstrap checks failed
max file descriptors [4096] for Elasticsearch process was 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 limits.conf configuration file, add something similar to the following:
sudo vim/etc/security/limits.conf

Add the following:
* Soft Nofile 65536
* Hard Nofile 131072
Note: * On behalf of all Linux user names

Save, exit, log back in to take effect

Question 5:

Max number of threads [1024] for user [es] are too low, increase to at least [2048]
Reason: Unable to create a local thread problem, the maximum number of threads that the user can create is too small
Solution: Switch to root, enter LIMITS.D directory, modify 90-nproc.conf configuration file.

sudo vim/etc/security/limits.d/90-nproc.conf

Find the following:
* Soft Nproc 1024

Amended to
* Soft Nproc 2048

Question 6:

Max virtual Memory Areas Vm.max_map_count [65530] is too low, increase to at least [262144]
Reason: Max virtual memory is too small
Solution: Switch to root, modify configuration file sysctl.conf

sudo vim/etc/sysctl.conf

Add the following configuration:
vm.max_map_count=655360

and execute the command:
Sysctl-p

Question 7:

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

Seccomp is a simple sandboxing mechanism supported by the Linux kernel (since the 2.6.23 version). It enables a process to enter a "safe" mode of operation in which processes can invoke only 4 system calls (the system calls), read (), write (), exit () and Sigreturn (), or the process is terminated.

The ES5.2 version of the default Bootstrap.system_call_filter to True for detection, so that the detection failed, after the failure of the direct cause ES can not start.
See: https://github.com/elastic/elasticsearch/issues/22899
System Call Filter Settingedit
Elasticsearch has attempted to install a system call filter since version 2.1.0. These are are enabled by default and could to be disabled via Bootstrap.seccomp. The naming of this setting is poor since seccomp are specific to Linux but Elasticsearch attempts to install a system call Filter on various operating systems. Starting in Elasticsearch 5.2.0, this setting has been to renamed. The previous setting is still support but'll be removed in Elasticsearch.

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

Question 8:

Elasticsearch boot could not find host or route
Reason: There is a problem with the Elasticsearch unicast configuration
Solution:
Check for configuration files in Elasticsearch
Vim Config/elasticsearch.yml
Locate 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 9:

Org.elasticsearch.transport.RemoteTransportException:Failed to deserialize exception response from stream
Reason: JDK version inconsistency between elasticsearch nodes
Solution: Elasticsearch Cluster unified JDK Environment LS

Question 10:

Unsupported Major.minor version 52.0
Reason: JDK version problem is too low
Solution: Replace JDK version, ElasticSearch5.0.0 support jdk1.8.0

Question 11:

Bin/elasticsearch-plugin Install license
Error:unknown Plugin License

Reason: ElasticSearch5.0.0 after plugin command has changed
Solution: Install all plugins with the latest command
Bin/elasticsearch-plugin Install X-pack