Problems upgrading

[shokcwave]

Hi i have tried to update our version of LME to v0.2 i have run the sudo ./deploy.sh uninstall command as mentioned in upgrading.md and them attempted to run the install script from the new location. everything seemd to be running ok until it gets to
'Waiting for elasticsearch to be ready'
and it just sits there forever or at least 24 hours in my case, is there a way i can see if elasticsearch is started?
many thanks

[duncan-ncc]

Hi @shokcwave

'Waiting for elasticsearch to be ready' - This is when the script waits for the elasticsearch servers rest API to return that the elasticsearch server is up and ready and available to receive logs. This check uses the curl command to connect to the server on port 9200 locally with the temporary username and password of elastic:temp.

This stage can often take ~30 minute whilst elasticsearch starts up depending on RAM/CPU and disk throughput.

You can manually check this using the following command
curl --cacert /opt/lme/Chapter\ 3\ Files/certs/root-ca.crt --user elastic:temp https://127.0.0.1:9200

You can check the elasticsearch docker logs with the following command
docker service -f logs lme_elasticsearch

[shokcwave]

I have just run the first command and it returned
curl: (60) SSL certificate problem: unable to get local issuer certificate

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it.

[duncan-ncc]

Did you run this command on the LME box? The --cacert points curl to the root CA so that command should work.
Can you provide the elasticsearch docker logs?

[shokcwave]

Yes I ran this command on the LME server, please find attached the logs

logs.txt

[duncan-ncc]

Hi @shokcwave
It looks like your instance of elasticsearch is only assigned 1GB of Ram so will not be able to boot.
Please check your docker-compose-stack-live.yml and change this to something more suitable (Over 8GB)
There is a chance that this has been caused by a regex bug that was reported and fixed in commit ab20084

Thanks,
Duncan

[shokcwave]

Hi @duncan-ncc sorry for the delay in replying i have been having a play around with this and managed to get it working, when i checked the docker-compose-stack-live.yml it already had 17G assigned so i renamed the file and reran the install script again, i eventually got it installed and working again.

However my next issue is i cant import the dashboards mentioned in chapter4, it appears to have updated the version of Kibana i had, i think it used to be 6.5.1 but now it is 7.4.0. (i didnt knowingly do this if i did it :) )

The error i receive when i try to import is 'The file could not be processed' please see attached picture

[shokcwave]

Just an update it appears to be the dashboard v0.2.0 that i am having problems with 0.1.2 imports fine

[duncan-ncc]

Hi @shokcwave,
The version 0.2.0 we had uploaded was designed for Kibana API import rather than via the GUI, We have just updated the file in chapter 4 files which should import via the Kibana GUI now.

[shokcwave]

I have just tried to import the new file you mentioned and i am still getting the same error message when importing it via the gui in Kibana

[duncan-ncc]

Apologies, The files were the wrong way round, it works for me in development, Let me know if this doesn't resolve your issue.

[shokcwave]

I have just tried again but this time i receive a slightly different error 'Saved objects file is invalid and cannot be imported'