# ElasticSearch StartUp Error, After updating from v 2.4.3 to v 2.4.4
**URL:** https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057
**Category:** Elasticsearch
**Created:** [February 14, 2017, 2:47pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057 "2017-02-14T14:47:26Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@umir1](https://discuss.elastic.co/u/umir1)
#### Post date: [February 14, 2017, 2:47pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057/1 "2017-02-14T14:47:27Z")
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](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.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 15, 2017, 9:25pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057/2 "2017-02-15T21:25:45Z")
Check your actual ES logs, there should be something there.
---
### Author:  [@umir1](https://discuss.elastic.co/u/umir1)
#### Post date: [February 21, 2017, 12:26pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057/3 "2017-02-21T12:26:27Z")
Thanks already checked and it worked 🙂
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 21, 2017, 8:49pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057/4 "2017-02-21T20:49:46Z")
What worked?
---
### Author:  [@umir1](https://discuss.elastic.co/u/umir1)
#### Post date: [February 22, 2017, 12:09pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057/5 "2017-02-22T12:09:05Z")
ES logs, and fixed the issue. It was es plugins compatibility issue.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 22, 2017, 12:09pm UTC](https://discuss.elastic.co/t/elasticsearch-startup-error-after-updating-from-v-2-4-3-to-v-2-4-4/75057/6 "2017-03-22T12:09:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.