# Cant start ES after update from 5.6.2 to 6.0

**URL:** https://discuss.elastic.co/t/cant-start-es-after-update-from-5-6-2-to-6-0/108843
**Category:** Elasticsearch
**Created:** [November 23, 2017, 8:59am UTC](https://discuss.elastic.co/t/cant-start-es-after-update-from-5-6-2-to-6-0/108843 "2017-11-23T08:59:43Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)
#### Post date: [November 24, 2017, 2:43am UTC](https://discuss.elastic.co/t/cant-start-es-after-update-from-5-6-2-to-6-0/108843/4 "2017-11-24T02:43:33Z")

</div>

> [@tatdat](#):
>
> elasticsearch-systemd-pre-exec could not be executed

This is the key log line. We do not have an `ExecStartPre` entry in 6.0.0 yet clearly your unit file still refers to one after the upgrade. This means you still have an old 5.x unit file and the upgrade did not replace the unit file with the 6.0.0 unit file. Maybe you edited the unit file (don’t do that!) and when you upgraded the package installer gave you a .rpmnew. You need to use the 6.0.0 unit file.

> [@tatdat](#):
>
> I have 5 node in production, all is down ...

Try to test changes to your production system in a staging environment first.

---

_[View the full topic](https://discuss.elastic.co/t/cant-start-es-after-update-from-5-6-2-to-6-0/108843)._