Elastic search Service is getting stopped automatically


(Nitin Chavan) #1

The service is getting stopped automatically as soon as I start it. The elastic search version we are using is 6.3.2. Below is the error I am getting
elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-12-28 20:32:24 EST; 242ms ago
Docs: http://www.elastic.co
Process: 13427 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 13427 (code=exited, status=1/FAILURE)

Dec 28 20:32:04 servername systemd[1]: Started Elasticsearch.
Dec 28 20:32:0 servername systemd[1]: Starting Elasticsearch...
Dec 28 20:32:24 servername systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Dec 28 20:32:24 servername systemd[1]: Unit elasticsearch.service entered failed state.
Dec 28 20:32:24 servername systemd[1]: elasticsearch.service failed.


If we go to log section : tail -f /var/log/elasticsearch/elasticsearch.log, this is what I see
at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:66) ~[elasticsearch-6.3.2.jar:6.3.2]
at org.elasticsearch.node.Node.start(Node.java:652) ~[elasticsearch-6.3.2.jar:6.3.2]
at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:265) ~[elasticsearch-6.3.2.jar:6.3.2]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:335) ~[elasticsearch-6.3.2.jar:6.3.2]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-6.3.2.jar:6.3.2]
... 6 more
[2018-12-28T20:32:24,467][INFO ][o.e.n.Node ] [ipW1Qpr] stopping ...
[2018-12-28T20:32:24,473][INFO ][o.e.n.Node ] [ipW1Qpr] stopped
[2018-12-28T20:32:24,473][INFO ][o.e.n.Node ] [ipW1Qpr] closing ...
[2018-12-28T20:32:24,494][INFO ][o.e.n.Node ] [ipW1Qpr] closed


this is how my file look like

======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

https://www.elastic.co/guide/en/elasticsearch/reference/index.html

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

#cluster.name: my-application

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

#node.name: node-1

Add custom attributes to the node:

#node.attr.rack: r1

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

path.data: /var/lib/elasticsearch

Path to log files:

path.logs: /var/log/elasticsearch

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

Set the bind address to a specific IP (IPv4 or IPv6):

#network.host: 192.168.0.1
network.host: "http://servername.amer.abc.com"

Set a custom port for HTTP:

http.port: 9200

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when new node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

#discovery.zen.ping.unicast.hosts: ["host1", "host2"]

Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):

#discovery.zen.minimum_master_nodes:

For more information, consult the zen discovery module documentation.

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

#gateway.recover_after_nodes: 3

For more information, consult the gateway module documentation.

---------------------------------- Various -----------------------------------

Require explicit names when deleting indices:

#action.destructive_requires_name: true


(David Pilato) #2

Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.

Or use markdown style like:

```
CODE
```

This is the icon to use if you are not using markdown format:

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
Please update your post.

The log is not complete but sounds like it's related to bootstrap checks.

Please read https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html


(system) closed #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.