Elasticsearch error

[Brian E Davis]

Since upgrading to Ubuntu 18.04.1 LTS, I’m seeing elasticsearch errors during the last part of the ingest (Index AIP). I’m getting the ‘Failed to establish a new connection: [Errno 111] Connection refused’. I’m running version 1.8.1 and 0.13.0 of the storage service. The Storage Service seems to be working fine, as does all the microprocesses until Index AIP. I've gone through all the usual elasticsearch checks and it seems to be running, but just not connecting.

I should mention that the Backlog and Archival Storage tabs of the dashboard throw an elasticsearch error as well (<class 'elasticsearch.exceptions.ConnectionError’>).

Could it be the url/host? I have a feeling that there might be a simple solution staring me in the face and I'm just not seeing it yet. 😳

Brian

[rspe...@artefactual.com]

Hi Brian,

Did you manage to resolve this or do you still need a hand to look at it on the forum? 

Let us know!

Cheers,

Ross

[Brian E Davis]

Hey Ross,

I haven't resolved it yet. This install of Archivematica is just for testing purposes, so it's not mission critical for me. However, I would love to figure this out.

Brian

[rspe...@artefactual.com]

We'll see what we can do! 

I guess first, back to the beginning, what's the Elasticsearch service status? sudo service elasticsearch status

Let me know, and then i follow up with folks here and see if anyone has diagnosed something like this before.

Ross

[Brian E Davis]

Ross,

I ran what you suggested and it said that elasticsearch was "inactive (dead)". So rather than running Restart, I decided to run Start. Then I ran what you suggested a 2nd time and got the following:

I'm not sure at this point if it's something to do with Java 10 and if I should install Java 8.

Brian

[rspe...@artefactual.com]

Thanks Brian. That helps a lot. 

Chatting internally, my colleague Radda reckons your diagnosis is spot-on - it's an old version of Elasticsearch, 1.x. And we can see similar problems for folk out there in the wild: https://stackoverflow.com/search?q=unrecognized+vm+option+%27useparnewgc%27 

He sent me this too, and it shows a Java compatibility matrix for 5.x and 6.x: https://www.elastic.co/support/matrix#matrix_jvm

If you're okay to downgrade Java and give that a go, you should be back up on your feet. Please let us know how it goes. 

And I will clarify what we need to update here so that folks don't run into the same problems in future. 

[Brian E Davis]

After rolling back to Java 8, it's working now. 

Thank you, Ross! (and Radda)

Brian

[BrzI Channel]

Had the same issue with Java 1.8.0_191.

Startign ElasticSearch manually created no errors...