Startup failed of ElasticSearch 6.8.15 on Ubuntu 20.04 with JDK 11

[mmenozzi]

Here the syslog:

Apr  9 12:53:24 store-live systemd[1]: Started Elasticsearch.
Apr  9 12:53:24 store-live elasticsearch[56767]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Apr  9 12:53:24 store-live elasticsearch[56767]: [0.000s][error][logging] Error opening log file 'logs/gc.log': No such file or directory
Apr  9 12:53:24 store-live elasticsearch[56767]: [0.000s][error][logging] Initialization of output 'file=logs/gc.log' using options 'filecount=32,filesize=64m' failed.
Apr  9 12:53:24 store-live elasticsearch[56767]: Invalid -Xlog option '-Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m', see error log for details.
Apr  9 12:53:24 store-live elasticsearch[56767]: Error: Could not create the Java Virtual Machine.
Apr  9 12:53:24 store-live elasticsearch[56767]: Error: A fatal exception has occurred. Program will exit.
Apr  9 12:53:24 store-live systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Apr  9 12:53:24 store-live systemd[1]: elasticsearch.service: Failed with result 'exit-code'.

I think it's because you replace the entire jvm.options file and it's broken for this versions matrix.

I think we have to do the same you said in this comment but even for ES 6.

[mmenozzi]

I think we have to do the same you said in this comment but even for ES 6.

No, I was wrong. This is not possible with ES6, as stated here.

Anyway ES6 on Ubuntu 20.04 and JDK 11 fails. We should use a different strategy to configure the jvm.options on ES6. Maybe a lineinfile.

What do you think @geerlingguy?

[stale]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[stale]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.