Arch Linux

Description:

I just updated my elasticsearch package to 5.4.0-1, and it seems it keeps restarting in a loop.


Sample logs:
mai 06 17:21:03 Aurora systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory
mai 06 17:21:08 Aurora systemd[1]: Started Elasticsearch.
mai 06 17:21:17 Aurora systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
mai 06 17:21:17 Aurora systemd[1]: elasticsearch.service: Unit entered failed state.
mai 06 17:21:17 Aurora systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
mai 06 17:21:17 Aurora systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.
mai 06 17:21:17 Aurora systemd[1]: Stopped Elasticsearch.
mai 06 17:21:17 Aurora systemd[1]: Starting Elasticsearch...
mai 06 17:21:18 Aurora systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory
mai 06 17:21:22 Aurora systemd[1]: Started Elasticsearch.
mai 06 17:21:33 Aurora systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
mai 06 17:21:33 Aurora systemd[1]: elasticsearch.service: Unit entered failed state.
mai 06 17:21:33 Aurora systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
mai 06 17:21:33 Aurora systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.
mai 06 17:21:33 Aurora systemd[1]: Stopped Elasticsearch.
mai 06 17:21:33 Aurora systemd[1]: Starting Elasticsearch...
mai 06 17:21:34 Aurora systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory
mai 06 17:21:38 Aurora systemd[1]: Started Elasticsearch.
mai 06 17:21:48 Aurora systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
mai 06 17:21:48 Aurora systemd[1]: elasticsearch.service: Unit entered failed state.
mai 06 17:21:48 Aurora systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
mai 06 17:21:48 Aurora systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.
mai 06 17:21:48 Aurora systemd[1]: Stopped Elasticsearch.
mai 06 17:21:48 Aurora systemd[1]: Starting Elasticsearch...
mai 06 17:21:49 Aurora systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory
mai 06 17:21:53 Aurora systemd[1]: Started Elasticsearch.
mai 06 17:22:03 Aurora systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
mai 06 17:22:03 Aurora systemd[1]: elasticsearch.service: Unit entered failed state.
mai 06 17:22:03 Aurora systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
mai 06 17:22:04 Aurora systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.
mai 06 17:22:04 Aurora systemd[1]: Stopped Elasticsearch.
mai 06 17:22:04 Aurora systemd[1]: Starting Elasticsearch...
mai 06 17:22:04 Aurora systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory


Looking at the logs starting it manually, it seems the problem lies in [default.path.home]:

[2017-05-06T17:44:31,985][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [Aurora] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [default.path.home] did you mean any of [default.path.conf, default.path.logs]?
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:127) ~[elasticsearch-5.4.0.jar:5.4.0]


It's explained there: https://www.elastic.co/guide/en/elasticsearch/reference/5.4/breaking-changes-5.4.html