FS#50049 - [elasticsearch] elasticsearch 2.3.4-1 'start-limit-hit' or no pid file?
Attached to Project:
Community Packages
Opened by Antoni Kaniowski (amk) - Friday, 15 July 2016, 08:07 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Tuesday, 31 January 2017, 09:19 GMT
Opened by Antoni Kaniowski (amk) - Friday, 15 July 2016, 08:07 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Tuesday, 31 January 2017, 09:19 GMT
|
Details
Elasticsearch fails to start on 4.6.3-1-ARCH, systemctl
status reports:
● elasticsearch.service - Elasticsearch Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit-hit) since Fri 2016-07-15 09:58:24 CEST; 3min 16s ago Docs: http://www.elastic.co Process: 4201 ExecStart=/usr/bin/elasticsearch -d -p /run/elasticsearch/elasticsearch.pid -Des.default.path.home=${ES_HOME} -Des.default.path.logs=${LOG_DIR} -Des.defau Main PID: 4219 (code=exited, status=1/FAILURE) Jul 15 09:58:23 m700 systemd[1]: elasticsearch.service: Unit entered failed state. Jul 15 09:58:23 m700 systemd[1]: elasticsearch.service: Failed with result 'exit-code'. Jul 15 09:58:24 m700 systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart. Jul 15 09:58:24 m700 systemd[1]: Stopped Elasticsearch. Jul 15 09:58:24 m700 systemd[1]: elasticsearch.service: Start request repeated too quickly. Jul 15 09:58:24 m700 systemd[1]: Failed to start Elasticsearch. Jul 15 09:58:24 m700 systemd[1]: elasticsearch.service: Unit entered failed state. Jul 15 09:58:24 m700 systemd[1]: elasticsearch.service: Failed with result 'start-limit-hit'. lines 1-15/15 (END) Steps taken before: pacman -S elasticsearch systemctl enable elasticsearch systemctl start elasticsearch Attached are the results of "journalctl -au elasticsearch", contents of "/etc/systemd/system/multi-user.target.wants/elasticsearch.service" and "/usr/lib/tmpfiles.d/elasticsearch.conf" Upon starting the service, there appears to be no file or folder called "elasticsearch" in "/var/run" |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Tuesday, 31 January 2017, 09:19 GMT
Reason for closing: Not a bug
Tuesday, 31 January 2017, 09:19 GMT
Reason for closing: Not a bug
The directory is created at startup and cleaned up at stop by systemd so it's normal that you don't see when the service is not running.
Also the message "PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory" is misleading and simply means that elasticsearch hasn't yet created the PID file (but will do it in time) and it is not the cause for the service failure.
You should look at logs in /var/log/elasticsearch.
[1] https://www.freedesktop.org/software/systemd/man/systemd.exec.html
I'm work around with ln -s /etc/elasticsearch /usr/share/elasticsearch/config
I've waited enough for more feedback and I'm now closing this as elasticsearch works fine for me on a clean installation.
/etc/elasticsearch has wrong permissions?
Did you get an error during installation?
Are you asking if the permissions are wrong or did you check?
Can you share the output of `ls -ld /etc/elasticsearch`.
What about the log files in /var/log/elasticsearch? Any relevant error?
After 'systemctl start elasticsearch' I got this:
Jan 27 00:41:11 linux systemd[1]: Starting Elasticsearch...
Jan 27 00:41:11 linux systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory
Jan 27 00:41:13 linux systemd[1]: elasticsearch.service: Daemon never wrote its PID file. Failing.
Jan 27 00:41:13 linux systemd[1]: Failed to start Elasticsearch.
Jan 27 00:41:13 linux systemd[1]: elasticsearch.service: Unit entered failed state.
Jan 27 00:41:13 linux systemd[1]: elasticsearch.service: Failed with result 'resources'.
Jan 27 00:41:13 linux systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.
Jan 27 00:41:13 linux systemd[1]: Stopped Elasticsearch.
Jan 27 00:41:13 linux systemd[1]: Starting Elasticsearch...
Jan 27 00:41:13 linux systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory
Mem load increments about 1.5Gib, page file to 100%.
I am not sure if it is due to the lack of resources or the faulty creation of the PID file.
You have to look at the logs in /var/log/elasticsearch for more details.