Hey all, I’m currently running Elasticsearch 5.5.0 in a container (official Elastic image) with the associated ROR plugin bundled in and installed. When I try starting the container it halts when checking the SSL keystore (I think?); the logs show:
Caused by: java.util.NoSuchElementException: No value present
at java.util.Optional.get(Optional.java:135) ~[?:1.8.0_131]
at org.elasticsearch.plugin.readonlyrest.settings.RorSettings.<init>(RorSettings.java:98) ~[?:?]
at org.elasticsearch.plugin.readonlyrest.es.SSLTransportNetty4.<init>(SSLTransportNetty4.java:55) ~[?:?]
at org.elasticsearch.plugin.readonlyrest.es.ReadonlyRestPlugin.lambda$getHttpTransports$0(ReadonlyRestPlugin.java:86) ~[?:?]
at org.elasticsearch.node.Node.<init>(Node.java:436) ~[elasticsearch-5.5.0.jar:5.5.0]
at org.elasticsearch.node.Node.<init>(Node.java:244) ~[elasticsearch-5.5.0.jar:5.5.0]
at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:232) ~[elasticsearch-5.5.0.jar:5.5.0]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:232) ~[elasticsearch-5.5.0.jar:5.5.0]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:351) ~[elasticsearch-5.5.0.jar:5.5.0]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) ~[elasticsearch-5.5.0.jar:5.5.0]
... 6 more
The keystore appears valid, and the pass I’m using in the config is correct. If I comment out the ‘http.type’ directive, ES throws a ton of errors which I assume is normal in this case. I honestly don’t know where the issue is here; any advice would be massively appreciated.