Issue with installation of Elastic search

[abhishek_Shetty]

Hi Team,

We are in the middle of installing Elastic search and kibana for installing RPA Orchestrator but after installing elastic search I am seeing that service is getting stopped.

Please find below details and help me in fixing the issue asap.

[shettya@scdl-sduipa-001 ~] sudo systemctl status elasticsearch.service ● elasticsearch.service - Elasticsearch Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2019-05-16 00:23:24 PDT; 1h 41min ago Docs: http://www.elastic.co Process: 9421 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p {PID_DIR}/elasticsearch.pid --quiet (code=exited, status=78)
Main PID: 9421 (code=exited, status=78)

May 16 00:23:15 scdl-sduipa-001 systemd[1]: Started Elasticsearch.
May 16 00:23:15 scdl-sduipa-001 elasticsearch[9421]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
May 16 00:23:24 scdl-sduipa-001 systemd[1]: elasticsearch.service: main process exited, code=exited, status=78/n/a
May 16 00:23:24 scdl-sduipa-001 systemd[1]: Unit elasticsearch.service entered failed state.
May 16 00:23:24 scdl-sduipa-001 systemd[1]: elasticsearch.service failed.

Error logs:

root@scdl-sduipa-001:/var/log/elasticsearch# tail -f elasticsearch.log
[2019-05-16T00:23:23,810][INFO ][o.e.t.TransportService ] [scdl-sduipa-001] pu blish_address {10.103.118.153:9300}, bound_addresses {10.103.118.153:9300}
[2019-05-16T00:23:23,817][INFO ][o.e.b.BootstrapChecks ] [scdl-sduipa-001] bo und or publishing to a non-loopback address, enforcing bootstrap checks
[2019-05-16T00:23:23,838][ERROR][o.e.b.Bootstrap ] [scdl-sduipa-001] no de validation exception
[2] bootstrap checks failed
[1]: system call filters failed to install; check the logs and fix your configur ation or disable system call filters at your own risk
[2]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_n odes] must be configured
[2019-05-16T00:23:23,848][INFO ][o.e.n.Node ] [scdl-sduipa-001] st opping ...
[2019-05-16T00:23:23,872][INFO ][o.e.n.Node ] [scdl-sduipa-001] st opped
[2019-05-16T00:23:23,873][INFO ][o.e.n.Node ] [scdl-sduipa-001] cl osing ...
[2019-05-16T00:23:23,883][INFO ][o.e.n.Node ] [scdl-sduipa-001] cl

Java version installed is 1.8.0_212
We are using red hat 7.6 OS

[luiz.santos]

Hi @abhishek_Shetty,

In order to ensure that some important settings receive the attention that they deserve, Elasticsearch has bootstrap checks upon startup. If Elasticsearch is in production mode, any bootstrap checks that fail will cause Elasticsearch to refuse to start. We consider an Elasticsearch node to be in production mode if it can join a cluster via non-loopback addresses.

According to your logs there are two bootstrap checks failing and preventing Elasticsearch to start:

[1]: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk
[2]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_n odes] must be configured

For [1], you can read the System call filter check docs and for [2], you can check Discovery configuration check docs.

I hope this helps you move forward.