Elasticsearch fails to start, no logs, (code=exited, status=1/FAILURE)

Elastic Stack Elasticsearch
1

systemctl status elasticsearch

● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-07-14 12:06:05 +03; 4min 42s ago
Docs: http://www.elastic.co
Process: 3258 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 3258 (code=exited, status=1/FAILURE)

Jul 14 12:05:57 systemd[1]: Started Elasticsearch.
Jul 14 12:06:05 systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Jul 14 12:06:05 systemd[1]: Unit elasticsearch.service entered failed state.
Jul 14 12:06:05 systemd[1]: elasticsearch.service failed.

1 Like
2

Welcome.

Please share elasticsearch logs and format them according to the rules of this forum. Thanks.

3

We need a FAQ if its the problem with systemd vs. /var/run now being a tmpfs (ram disk) so dir /var/run/elasticsearch/ disappears at reboot.

4

Is it related? Sorry. I'm not following.

5

Because this message may mean that ${PID_DIR} isn't writable by elasticsearch, as in doesn't exist. If you don't get elasticsearch logs, look at /var/log/messages.

1 Like
6

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