ES 8.0 RPM Install - cannot be located launching scripts/binaries from the bin directory - RHEL 8

I am deploying a new ES cluster running 8.0 using RHEL 8.5. Fairly vanilla deployment and Elasticsearch is running on the first node with auto-security used, no JVM installed (using built-in). SELINUX is permissive.

Elastic is launching using systemd and I am able to query the cluster information:

  "name" : "",
  "cluster_name" : "nkl-prd-es-clr-01",
  "cluster_uuid" : "zpb0mWSGSVSVvByeZ-fl4w",
  "version" : {
    "number" : "8.0.0",
    "build_flavor" : "default",
    "build_type" : "rpm",
    "build_hash" : "1b6a7ece17463df5ff54a3e1302d825889aa1161",
    "build_date" : "2022-02-03T16:47:57.507843096Z",
    "build_snapshot" : false,
    "lucene_version" : "9.0.0",
    "minimum_wire_compatibility_version" : "7.17.0",
    "minimum_index_compatibility_version" : "7.0.0"
  "tagline" : "You Know, for Search"

When I attempt to run any of the scripts in the bin folder to generate tokens for adding the additional nodes I receive the following:

[template@es-mstr-01 ~]$ cd /usr/share/elasticsearch/bin
[template@es-mstr-01 bin]$ sudo ./elasticsearch-create-enrollment-token -s node
/usr/share/elasticsearch/jdk/bin/java: error while loading shared libraries: cannot open shared object file: No such file or directory
[template@es-mstr-01 bin]$ ./elasticsearch-create-enrollment-token -s node
./elasticsearch-env: line 83: /usr/share/elasticsearch/jdk/bin/java: Operation not permitted

Additionally, the following output can be seen when attempting to locate

[template@es-mstr-01 bin]$ locate
[template@es-mstr-01 bin]$ sudo ldd /usr/share/elasticsearch/jdk/bin/java (0x00007ffeb3bf4000) => /lib64/ (0x00007f1f7e6bf000) => /usr/share/elasticsearch/jdk/bin/../lib/ (0x00007f1f7e4ae000) => /lib64/ (0x00007f1f7e28e000) => /lib64/ (0x00007f1f7e08a000) => /lib64/ (0x00007f1f7dcc5000)
	/lib64/ (0x00007f1f7ead9000)
[template@es-mstr-01 bin]$

Any ideas would be greatly appreciated. I have also attempted to add the path using ldconfig but this made no difference.


can you open an issue in Issues · elastic/elasticsearch · GitHub - that looks like a bug to me.



GitHub - Issue



This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.