Elasticsearch active failed


(yurizal) #1

Hello,
OS = centos7, install in vm
java version

openjdk version "1.8.0_102"
OpenJDK Runtime Environment (build 1.8.0_102-b14)
OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)

the first time when install elasticsearch is successful, and its status running (curl -X GET 'http://localhost:9200'). I follow the https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html (Installing from the RPM repository)

==============================================================================
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2017-09-11 18:02:52 EDT; 11min ago
Docs: http://www.elastic.co
Process: 1119 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 1130 (java)
CGroup: /system.slice/elasticsearch.service
└─1130 /bin/java -Xms2g -Xmx2g -XX:+UseConcMarkSweepGC -XX:CMSInit...

Sep 11 18:02:52 192.168.1.9 systemd[1]: Starting Elasticsearch...
Sep 11 18:02:52 192.168.1.9 systemd[1]: Started Elasticsearch.

[root@192 cenelk]# curl -X GET 'http://localhost:9200' {
"name" : "bCTNIfd",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "eeS1QsUmQC69-vMZ8ZFftQ",
"version" : {
"number" : "5.6.0",
"build_hash" : "781a835",
"build_date" : "2017-09-07T03:09:58.087Z",
"build_snapshot" : false,
"lucene_version" : "6.6.0"
},
"tagline" : "You Know, for Search"
}

keep install kibana also successful and status(elasticsearch & kibana) sill running, after install logstash and status running, but elasticsearch status failed, is there any problem. can u help me??

==================================================================================
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-09-11 19:16:20 EDT; 11min ago
Docs: http://www.elastic.co
Process: 6121 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG_DIR} -Edefault.path.data=${DATA_DIR} -Edefault.path.conf=${CONF_DIR} (code=exited, status=1/FAILURE)
Process: 6117 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 6121 (code=exited, status=1/FAILURE)

Sep 11 19:16:18 192.168.1.9 systemd[1]: Started Elasticsearch.
Sep 11 19:16:19 192.168.1.9 elasticsearch[6121]: OpenJDK 64-Bit Server VM warning: INFO: os::com...12)
Sep 11 19:16:19 192.168.1.9 elasticsearch[6121]: #
Sep 11 19:16:19 192.168.1.9 elasticsearch[6121]: # There is insufficient memory for the Java Run...ue.
Sep 11 19:16:19 192.168.1.9 elasticsearch[6121]: # Native memory allocation (mmap) failed to map...ry.
Sep 11 19:16:19 192.168.1.9 elasticsearch[6121]: # An error report file with more information is...as:
Sep 11 19:16:19 192.168.1.9 elasticsearch[6121]: # /tmp/hs_err_pid6121.log
Sep 11 19:16:20 192.168.1.9 systemd[1]: elasticsearch.service: main process exited, code=exited...LURE
Sep 11 19:16:20 192.168.1.9 systemd[1]: Unit elasticsearch.service entered failed state.
Sep 11 19:16:20 192.168.1.9 systemd[1]: elasticsearch.service failed.
Hint: Some lines were ellipsized, use -l to show in full.


(Mark Walkom) #2

It's better if you keep things to the one thread :slight_smile:


(Mark Walkom) #3