-
-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elasticsearch not connecting to geonetwork. Some kind of security problem #7741
Comments
Elasticsearch 8 support is planned for next 4.4.3 release. See #7599 |
Thanks for the heads up, I was looking at https://docs.geonetwork-opensource.org/latest/install-guide/installing-index/ for 4.4.2 where it says and the instructions for installation start... I figured tested mean that it works.... |
the pom.xml in core-geonetwork repo also has <es.version>8.11.3</es.version> |
OK, got something working, here's the workflow: checkout 4.2.x core-geonetwork branch update ES_JAVA_HOME to point to the one in core-geonetwork\es\elasticsearch-7.17.15\jdk Set up Kibana login...
then run this to create keystore
Side track: try
try downloading https://github.com/geonetwork/core-geonetwork/archive/refs/tags/4.4.2.zip so... try checkout core-geonetwork/main |
solved for now, close |
Describe the bug
Build geonetwork from source. (separate issue... have to manually copy https://mvnrepository.com/artifact/org.geotools.jdbc/gt-jdbc-postgis)» 30.0 and
[https://mvnrepository.com/artifact/org.geotools/gt-gml-geometry-streaming) » 30.0 into my maven .m2 because maven couldn't access 0some kind of certificate problem.) Anyway got 4.4.3 snapshot build from a local fork for core-geonetwork sync'd with main.
Have installed and gotten Elastic Search 8.11.3 working with Kibana 8.11.3. had to generate and copy xpack.encryptedSavedObjects.encryptionKey, xpack.reporting.encryptionKey, and xpack.security.encryptionKey into kibana.yml, and set xpack.security.enabled: true and xpack.security.enrollment.enabled: true in ElasticSearch.yml. That seemed to get kibana workign with Elastic.
Copy geonetwork.war from target dir in core-geonetwork to tomcat9.0.85 webApps folder. In Chrome clear browsing history. start tomcat, after awhile its running. Stop tomcat, put in the elastic search user and password, change protocol to https (tried http first, didn't work).
in Geonetowrk, when I search or got to 'search page' get message "Query returned an error. Check the console for details."
run admin/status in geonetwork, says 'remote index OK'; 'Records in index/db = 6/23' That's odd, Kibana only see 6 records.
in the tomcat console I do see this
and in the elastic console this:
[2024-02-11T13:20:03,562][WARN ][o.e.h.n.Netty4HttpServerTransport] [EMERALD] http client did not trust this server's certificate, closing connection Netty4HttpChannel{localAddress=/[0:0:0:0:0:0:0:1]:9200, remoteAddress=/[0:0:0:0:0:0:0:1]:61335}
To Reproduce
Steps to reproduce the behavior:
What am I missing?
The text was updated successfully, but these errors were encountered: