Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45806 - [elasticsearch] Unable to start service

Attached to Project: Community Packages
Opened by Rowan Lewis (meow) - Tuesday, 28 July 2015, 09:53 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Tuesday, 28 July 2015, 16:19 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Massimiliano Torromeo (mtorromeo)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Systemd complains that the pid file is not readable yet and then the service exits.

Tested with version 1.6.0 and 1.7.0, here is an excerpt from the journal:

Jul 28 11:26:06 boris.local systemd[1]: Starting ElasticSearch...
Jul 28 11:26:06 boris.local systemd[1]: elasticsearch.service: PID file /run/elasticsearch/elasticsearch.pid not readable (yet?) after start: No such file or directory
Jul 28 11:26:06 boris.local systemd[1]: Started ElasticSearch.
Jul 28 11:26:09 boris.local systemd[1]: elasticsearch.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Jul 28 11:26:09 boris.local systemd[1]: elasticsearch.service: Unit entered failed state.
Jul 28 11:26:09 boris.local systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Jul 28 11:26:10 boris.local systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.

Steps to reproduce:
1) Install the elasticsearch package
2) Start the service
This task depends upon

Closed by  Massimiliano Torromeo (mtorromeo)
Tuesday, 28 July 2015, 16:19 GMT
Reason for closing:  Not a bug
Comment by Rowan Lewis (meow) - Tuesday, 28 July 2015, 10:12 GMT
After removing /var/lib/elasticsearch I was able to start the daemon again, I'm not sure what the problem actually was but have attached the output from the command line just in case this is not something I've fucked up.
   manual.log (12.9 KiB)
Comment by Massimiliano Torromeo (mtorromeo) - Tuesday, 28 July 2015, 13:02 GMT
I think you could have tried to delete just the state file based on similar upstream reports [1]
This does not seem like a packaging issue.

[1] https://github.com/elastic/elasticsearch/search?utf8=%E2%9C%93&q=%22Could+not+find+a+state+file+to+recover+from%22&type=Issues
Comment by Rowan Lewis (meow) - Tuesday, 28 July 2015, 15:31 GMT
Yes, you're right, I just opened it as a packaging issue because my initial impression of what was happening was wrong and I thought it may have to do with the packaged service files.

Loading...