Community Packages

Please read this before reporting a bug:

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!

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
Task Type Bug Report
Category Packages
Status Closed
Assigned To Massimiliano Torromeo (mtorromeo)
Levente Polyak (anthraxx)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


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
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
Comment by Levente Polyak (anthraxx) - Wednesday, 20 May 2020, 15:49 GMT
@mtorromeo: don't you test new (in the context of ELK major) release trees locally?
Comment by Massimiliano Torromeo (mtorromeo) - Wednesday, 20 May 2020, 16:03 GMT
What I usually do is install the package and just start the service.

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.
Comment by Levente Polyak (anthraxx) - Wednesday, 20 May 2020, 16:05 GMT
No problem, happens. I'm a fan of co-maintaining so if you feel uncomfortable testing major releases I'm more than happy if you just help co-maintaining regular point releases :)
Comment by Massimiliano Torromeo (mtorromeo) - Wednesday, 20 May 2020, 16:08 GMT
Sure, no problem. I'll just switch to the co-pilot seat then :)
Comment by Massimiliano Torromeo (mtorromeo) - Thursday, 21 May 2020, 16:56 GMT
Should be fixed in elasticsearch-7.7.0-2

Thanks for the patch!
Comment by Lucas Gomes (heregoesnoth) - Thursday, 21 May 2020, 23:51 GMT
Same problem here after upgrade.
Comment by Massimiliano Torromeo (mtorromeo) - Friday, 22 May 2020, 19:30 GMT
@heregoesnoth: are you sure it's the same problem? Can you share come logs? What version of the JVM are you using?
Comment by Lucas Gomes (heregoesnoth) - Saturday, 23 May 2020, 14:30 GMT
@mtorromeo yes, but its working now with the new update. Don't worry.

Comment by Massimiliano Torromeo (mtorromeo) - Saturday, 23 May 2020, 15:01 GMT
Ok, thought you meant that elasticsearch-7.7.0-2 was not working for you.