Elasticsearch 6.* still not running on rhel7.5


(Adrian) #1

Blocked by another huddle....I installed elastic search as adviced here:

but it sends this error when i try checking if it runs
curl: (7) Failed connect to localhost:9200; Connection refused

i checked if the service was runnning and i found out that it wasn't so i started it then it sent me this response

    ● elasticsearch.service - Elasticsearch
       Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
       Active: active (running) since Wed 2018-09-19 07:21:43 UTC; 32s ago
         Docs: http://www.elastic.co
     Main PID: 5798 (java)
       CGroup: /system.slice/elasticsearch.service
               └─5798 /bin/java -Xms512m -Xmx512m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headl...

    Sep 19 07:21:43 ip-172-31-7-139.us-east-2.compute.internal systemd[1]: Started Elasticsearch.
    Sep 19 07:21:43 ip-172-31-7-139.us-east-2.compute.internal systemd[1]: Starting Elasticsearch...

but on trying to test the elastic search node it still sent me this error
curl: (7) Failed connect to localhost:9200; Connection refused
and on checking the status of the service, this is what it said

● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Wed 2018-09-19 07:23:52 UTC; 9s ago
     Docs: http://www.elastic.co
  Process: 5798 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=killed, signal=KILL)
 Main PID: 5798 (code=killed, signal=KILL)

Sep 19 07:21:43 ip-172-31-7-139.us-east-2.compute.internal systemd[1]: Started Elasticsearch.
Sep 19 07:21:43 ip-172-31-7-139.us-east-2.compute.internal systemd[1]: Starting Elasticsearch...
Sep 19 07:23:52 ip-172-31-7-139.us-east-2.compute.internal systemd[1]: elasticsearch.service: main process exited, code=killed, status=9/KILL
Sep 19 07:23:52 ip-172-31-7-139.us-east-2.compute.internal systemd[1]: Unit elasticsearch.service entered failed state.
Sep 19 07:23:52 ip-172-31-7-139.us-east-2.compute.internal systemd[1]: elasticsearch.service failed.

Please help


(Christian Dahlqvist) #2

What is in the the Elasticsearch logs?


(Adrian) #3

I checked /var/log/elasticsearch but there are no logs


(Adrian) #4

this is the only file that is there: gc.log.0.current


(Christian Dahlqvist) #5

How much RAM do you have on the host? Do you have anything else running on it?


(Adrian) #6

I have 1Gb RAM and 10Gb Volume. I have the LAMP stack running of it too.

I reduced the heap size to 512Mbs though!:man_shrugging:


(Christian Dahlqvist) #7

Elasticsearch also requires off-heap storage, so you may need to reduce it even more. I am however not sure what the minimum heap size is to get it to work. How much free RAM do you have when the LAMP stack is running?


(Adrian) #8

552Mbs free and 533Mbs available


(Christian Dahlqvist) #9

That is unlikely to be enough due to the off-heap storage, so you will either need to reduce heap further (not sure how useful a node with that little heap will be), add RAM or install Elasticsearch on a separate host.


(Adrian) #10

Will weigh my options. Thanks Christian.


(Adrian) #11

Reduced my heap size to 256Mbs. It works now.


(system) #12

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.