Arch Linux User Repository

That's a strange one.

I just git cloned this to /tmp, built and installed it cleanly . Ran elasticsearch-keystore create and started the service all without experiencing the lines you're talking about anywhere in the list.

Is it possible you're experiencing something unique to your own filesystem?

Could you please fix this issue?

Detected unsafe path transition /etc/elasticsearch (owned by elasticsearch) → /etc/elasticsearch/jvm.options (owned by root) during canonicalization of etc/elasticsearch/jvm.options.
Detected unsafe path transition /etc/elasticsearch (owned by elasticsearch) → /etc/elasticsearch/elasticsearch.yml (owned by root) during canonicalization of etc/elasticsearch/elasticsearch.yml.
Detected unsafe path transition /etc/elasticsearch (owned by elasticsearch) → /etc/elasticsearch/log4j2.properties (owned by root) during canonicalization of etc/elasticsearch/log4j2.properties.
Detected unsafe path transition /etc/elasticsearch (owned by elasticsearch) → /etc/elasticsearch/role_mapping.yml (owned by root) during canonicalization of etc/elasticsearch/role_mapping.yml.
Detected unsafe path transition /etc/elasticsearch (owned by elasticsearch) → /etc/elasticsearch/roles.yml (owned by root) during canonicalization of etc/elasticsearch/roles.yml.
Detected unsafe path transition /etc/elasticsearch (owned by elasticsearch) → /etc/elasticsearch/users (owned by root) during canonicalization of etc/elasticsearch/users.
Detected unsafe path transition /etc/elasticsearch (owned by elasticsearch) → /etc/elasticsearch/users_roles (owned by root) during canonicalization of etc/elasticsearch/users_roles.
error: command failed to execute correctly

Thank you for the lightning-fast fix!

Yeah its been bugging me on every machine this week. Will change it here too.

Hi, there was a change in java packages: jdk-openjdk includes now the jre packages and conflict from now on with jre-openjdk... packages. Elasticsearch shoud have "java-runtime" as dependency not jre-openjdk... Otherwise it blocks installing jdk-openjdk from now on - see here also: https://archlinux.org/news/incoming-changes-in-jdk-jre-21-packages-may-require-manual-intervention/

The team have fixed building with JDK21 upstream however advised the JDK21 toolchain provides nothing special. Building with JDK17 is fine.

Thanks ❤️ but it feels like a cop out falling all the way back to JDK17 due to the warning in JDK21.

If you grant me access to elasticsearch-bin I can try to save it.

Migrated back to elasticsearch as elasticsearch-bin is failing.

Sounds like we have a great maintainer out there! Long live ipaqmaster!

Updated the package to include java-17-openjdk as a make dependency and to build Elasticsearch with it for now.

Resulting package still set to run using the latest which is currently java-21-openjdk.

Opened upstream issue in case the warnings experienced on java-21-openjdk are a problem: https://github.com/elastic/elasticsearch/issues/100173

Sorry I didn't see these earlier. I'll try to correct this.

It seems jre-openjdk-headless has started shipping java-21-openjdk which experiences warnings as errors during the build.

My machine has its archlinux-java set to java-17-openjdk (default) but a brand new docker container which only has jre-openjdk-headless (java-21-openjdk) can't build it due to the warning errors.

I was able to build it with java-20-openjdk in the container after downgrading to these three together: jdk-openjdk-20.0.2.u9-3 jre-openjdk-20.0.2.u9-3 jre-openjdk-headless-20.0.2.u9-3

Because Java 8,11,17 and 21 are the currently supported versions on Archlinux perhaps this AUR package could be changed to build using 17 until 21 doesn't error on warn?