ElasticSearch StartUp Error, After updating from v 2.4.3 to v 2.4.4

After a update from 2.4.3 to 2.4.4 elasticsearch, getting exception while starting
Machine: CentOs 7

systemctl start elasticsearch
systemctl status elasticsearch

elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-02-14 09:33:33 EST; 11min ago
Docs: http://www.elastic.co
Process: 1051 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -Des.pidfile=${PID_DIR}/elasticsearch.pid -Des.default.path.home=${ES_HOME} -Des.default.path.logs=${LOG_DIR} -Des.default.path.data=${DATA_DIR} -Des.default.path.conf=${CONF_DIR} (code=exited, status=1/FAILURE)
Process: 1042 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 1051 (code=exited, status=1/FAILURE)

Feb 14 09:33:33 AELK-N03 elasticsearch[1051]: at org.elasticsearch.node.Node.(Node.java:158)
Feb 14 09:33:33 AELK-N03 elasticsearch[1051]: at org.elasticsearch.node.Node.(Node.java:140)
Feb 14 09:33:33 AELK-N03 elasticsearch[1051]: at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:143)
Feb 14 09:33:33 AELK-N03 elasticsearch[1051]: at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:194)
Feb 14 09:33:33 AELK-N03 elasticsearch[1051]: at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:286)
Feb 14 09:33:33 AELK-N03 elasticsearch[1051]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:45)
Feb 14 09:33:33 AELK-N03 elasticsearch[1051]: Refer to the log for complete error details.
Feb 14 09:33:33 AELK-N03 systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Feb 14 09:33:33 AELK-N03 systemd[1]: Unit elasticsearch.service entered failed state.
Feb 14 09:33:33 AELK-N03 systemd[1]: elasticsearch.service failed.

Check your actual ES logs, there should be something there.

Thanks already checked and it worked :slight_smile:

What worked?

ES logs, and fixed the issue. It was es plugins compatibility issue.

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