Hi Devs,
After eventually getting ElasticSearch/Kibana working locally with Geonetwork 3.4.x, I’m trying to deploy to my production server. I’ve followed the exact same instructions for configuring as I did locally, these came from Jose (thanks Jose).
My current situation is that although ElasticSearch and Kibana seem to be working, judging from stdout, I can’t access the Kibana application. There are a couple of differences in the two setups. Firstly, running locally I was using all the default ports and running using maven. My production server is running tomcat, and is using port 80 for geonetwork rather than 8080.
My first question is hopefully a really easy one to answer! Does it matter particularly where the es folder is placed (eg https://github.com/geonetwork/core-geonetwork/tree/develop/es)? it doesn’t seem to be included in the war file that I built (using the es profile) so I’ve had to transfer it from my local build to the server, but I don’t know if it matters where I put it. I’ve placed it in /usr/share for now.
Secondly, like I said, I can’t access kibana at the default URL (I’m ssh tunnelling so it should be at localhost:5601/app/kibana, same as default). The page simply says “Kibana did not load properly. Check the server output for more information” but the server output shows no errors.
When I try to access the dashboard from within geonetwork, it also doesn’t work. nginx sits in front of geonetwork, and the log files tell me it’s trying to access http://127.0.0.1:8080/geonetwork/srv/api.site/index/es and http://127.0.0.1:8080/geonetwork/warninghealthcheck but it should not be trying to use port 8080- this is not set in the geonetwork settings though, and everything else in geonetwork works fine. I’m wondering if there’s a default URL hardcoded somewhere that I’ve missed.
Any help would be greatly appreciated!
Jo
···
Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009
Hi Francois,
Thanks for this, I find I can access kibana at [url]/geonetwork/dashboards/app/kibana which is slightly different to what it says in the documentation but it seems to be working.
However, when I view the admin console in geonetwork I still don’t see the dashboards. I see tabs for Status, WFS Indexing, Information and versioning but not content or search statistics. When I run the same geonetwork locally (eg using maven, but the same version the war file is deployed from) then everything works. So I’m wondering if the war file somehow hasn’t been built with the es profile? How would I test this?
So to be clear, I built the war file with:
mvn clean install -Penv-prod,es -DskipTests
Locally I run it using the following:
mvn jetty:run -Penv-prod,es
And this works, but the war file deployed in tomcat does not. Am I missing something?
Thanks again
Jo
···
On Thu, Apr 5, 2018 at 8:23 AM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:
Hi Jon
–
2018-04-04 17:37 GMT+02:00 Jo Cook <jocook@anonymised.com>:
Hi Devs,
After eventually getting ElasticSearch/Kibana working locally with Geonetwork 3.4.x, I’m trying to deploy to my production server. I’ve followed the exact same instructions for configuring as I did locally, these came from Jose (thanks Jose).
My current situation is that although ElasticSearch and Kibana seem to be working, judging from stdout, I can’t access the Kibana application. There are a couple of differences in the two setups. Firstly, running locally I was using all the default ports and running using maven. My production server is running tomcat, and is using port 80 for geonetwork rather than 8080.
My first question is hopefully a really easy one to answer! Does it matter particularly where the es folder is placed (eg https://github.com/geonetwork/core-geonetwork/tree/develop/es)? it doesn’t seem to be included in the war file that I built (using the es profile) so I’ve had to transfer it from my local build to the server, but I don’t know if it matters where I put it. I’ve placed it in /usr/share for now.
Secondly, like I said, I can’t access kibana at the default URL (I’m ssh tunnelling so it should be at localhost:5601/app/kibana, same as default). The page simply says “Kibana did not load properly. Check the server output for more information” but the server output shows no errors.
If you followed
https://github.com/geonetwork/core-geonetwork/tree/develop/es/es-dashboards#manual-installation
and define kibana server base path, then Kibana can only be accessed through the proxy
https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webResources/WEB-INF/web.xml#L422
So you can’t access Kibana using localhost:5601 but you have to use localhost:8080/geonetwork/dashboard which proxy to kibana which is configured with this base path.
When I try to access the dashboard from within geonetwork, it also doesn’t work. nginx sits in front of geonetwork, and the log files tell me it’s trying to access http://127.0.0.1:8080/geonetwork/srv/api.site/index/es and http://127.0.0.1:8080/geonetwork/warninghealthcheck but it should not be trying to use port 8080- this is not set in the geonetwork settings though, and everything else in geonetwork works fine. I’m wondering if there’s a default URL hardcoded somewhere that I’ve missed.
It should not. Sounds odd.
HTH
Francois
Any help would be greatly appreciated!
Jo
–
Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009
–
Astun Technology Ltd, The Coach House, 17 West Street, Epsom, Surrey, KT18 7RL, UK
t:+44 1372 744 009 w: astuntechnology.com twitter:@astuntech
iShare - enterprise geographic intelligence platform
GeoServer, PostGIS and QGIS training
Helpdesk and customer portal
Company registration no. 5410695. Registered in England and Wales. Registered office: 120 Manor Green Road, Epsom, Surrey, KT19 8LN VAT no. 864201149.
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
GeoNetwork-devel mailing list
GeoNetwork-devel@anonymised.comorge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009