Continuing the discussion from Elasticsearch Service won't start after full cluster upgrade from 5.4 to 6.0:
I'm mid upgrade from 5.6.6. to 6.2.4 and haivng an issue getting elastic to start, if I look in /usr/lib/systemd/system/elasticsearch.service
I also see the line with -Edefault.path.conf=${CONF_DIR}
I have added path.config
and path.log
to the elasticsearch.yml file
opened /etc/sysconfig/elasticsearch and added ES_PATH_CONF=/etc/elasticsearch
but when I try to start it I'm getting
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2018-04-19 16:48:16 BST; 5min ago
Docs: http://www.elastic.co
Process: 40345 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=203/EXEC)
Main PID: 21347 (code=exited, status=143)
Apr 19 16:48:16 opselastic1 systemd[1]: Starting Elasticsearch...
Apr 19 16:48:16 opselastic1 systemd[1]: elasticsearch.service: control process exited, code=exited status=203
Apr 19 16:48:16 opselastic1 systemd[1]: Failed to start Elasticsearch.
Apr 19 16:48:16 opselastic1 systemd[1]: Unit elasticsearch.service entered failed state.
Apr 19 16:48:16 opselastic1 systemd[1]: elasticsearch.service failed.
I'm guessing there is something I've missed but as elastic is putting nothing to the logs I'm not sure what it may be. out of desperation I tried the suggestions to change /usr/lib/systemd/system/elasticsearch.service
but it made no difference.