I have a problem with loading openssl, does not make a difference if statically or dynamically linked, I always get the following error message when starting up
[2019-04-13T21:40:36,563][INFO ][c.f.s.s.DefaultSearchGuardKeyStore] [HMTWkAe] OpenSSL not available (this is not an error, we simply fallback to built-in JDK SSL) because of java.lang.IllegalArgumentException: Failed to load any of the given libraries: [netty_tcnative_linux_x86_64, netty_tcnative_linux_x86_64_fedora, netty_tcnative_x86_64, netty_tcnative]
There are no other DEBUG or INFO messages regarding this issue before or after.
I use the netty files
Elasticsearch is 6.7.1.
If no netty file at all is present I get (correctly)
[2019-04-13T21:17:58,427][INFO ][c.f.s.s.DefaultSearchGuardKeyStore] [HMTWkAe] OpenSSL not available (this is not an error, we simply fallback to built-in JDK SSL) because of java.lang.Cl assNotFoundException: io.netty.internal.tcnative.SSL
Running on CentOS latest, of course when trying the dynamically linked version apr is installed. But from what I can see for dynamically linked you would expect that the OpenSSL version on the system is updated to the latest version manually which is an absolute no-go on RHEL systems in production as a lot of packages expect the version which is provided by RHEL/CentOS and side effects can occur, this is official statement from RedHat. But it makes no difference, the error is always the same. In generel the static linked version would be preferred.
Don’t know what I can do about it.
Can you help pease?