FS#66726 - [elasticsearch] 7.7.0-1 JVM Options and Environment Issues
Attached to Project:
Community Packages
Opened by David Wheeler (dwheeler) - Wednesday, 20 May 2020, 15:20 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Saturday, 23 May 2020, 15:01 GMT
Opened by David Wheeler (dwheeler) - Wednesday, 20 May 2020, 15:20 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Saturday, 23 May 2020, 15:01 GMT
|
Details
Description:
Upstream changes are preventing elasticsearch from starting. 1: Changes to elasticsearch-env were made that need to be included in the arch package's version. See https://github.com/elastic/elasticsearch/blame/13f5631eec1175a533e8f68078d280b393afbfa5/distribution/src/bin/elasticsearch-env#L70-L77 2: The new JVM options directory needs to be readable by the elasticsearch group. Logs and a patch are attached. Additional info: * 7.7.0-1 Steps to reproduce: Install a new instance, or upgrade an existing one, and then start the service. |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Saturday, 23 May 2020, 15:01 GMT
Reason for closing: Fixed
Additional comments about closing: elasticsearch-7.7.0-2
Saturday, 23 May 2020, 15:01 GMT
Reason for closing: Fixed
Additional comments about closing: elasticsearch-7.7.0-2
I used to actually query the service from an application that I was developing but I don't use it anymore and this time I forgot even to start it. I let some time pass from building the package to publishing it and lost focus and this is the result, sorry about that!
I think it would be better if I stop maintaining the whole ELK stack altogether given that I don't really use them at all and you are already co-maintaining them anyway.
Thanks for the patch!
Thanks!