# I broke ES while upgrading from 2.3 to 5.6 :(

**URL:** https://discuss.elastic.co/t/i-broke-es-while-upgrading-from-2-3-to-5-6/192544
**Category:** Elasticsearch
**Created:** [July 27, 2019, 11:31pm UTC](https://discuss.elastic.co/t/i-broke-es-while-upgrading-from-2-3-to-5-6/192544 "2019-07-27T23:31:54Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![tryptych](https://avatars.discourse-cdn.com/v4/letter/t/6bbea6/32.png) [@tryptych](https://discuss.elastic.co/u/tryptych)
#### Post date: [July 27, 2019, 11:31pm UTC](https://discuss.elastic.co/t/i-broke-es-while-upgrading-from-2-3-to-5-6/192544/1 "2019-07-27T23:31:54Z")

</div>

I'm on CentOS7, using Elastic Search for Graylog. I'm a rookie, learning as I go. I upgraded ES from 2.3 to 5.6 using yum. When I start ES now it fails and doesn't give me any useful feedback.

> [root@locker2 ~]# systemctl status elasticsearch  
> ● elasticsearch.service - Elasticsearch  
> Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)  
> Active: failed (Result: exit-code) since Sat 2019-07-27 19:22:44 EDT; 5min ago  
> Docs: [http://www.elastic.co](http://www.elastic.co)  
> Process: 1902 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: 1898 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)  
> Main PID: 1902 (code=exited, status=1/FAILURE)
> 
> Jul 27 19:22:38 locker2 systemd[1]: Starting Elasticsearch...  
> Jul 27 19:22:38 locker2 systemd[1]: Started Elasticsearch.  
> Jul 27 19:22:44 locker2 systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE  
> Jul 27 19:22:44 locker2 systemd[1]: Unit elasticsearch.service entered failed state.  
> Jul 27 19:22:44 locker2 systemd[1]: elasticsearch.service failed.

**How can I troubleshoot this? How do I get ES to produce some useful logs? Where are they located? Is there a debug mode?**

Thanks in advance

---

<div class="post-metadata">

### Author: ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [August 2, 2019, 12:05pm UTC](https://discuss.elastic.co/t/i-broke-es-while-upgrading-from-2-3-to-5-6/192544/2 "2019-08-02T12:05:51Z")

</div>

Hi,

please see our [documentation when installing Elasticsearch from the rpm package](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/rpm.html). Among other things you'll find the [directory layout](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/rpm.html#rpm-layout) documented there which says that the default path for the log files is in `/var/log/elasticsearch`.

Daniel

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 30, 2019, 12:05pm UTC](https://discuss.elastic.co/t/i-broke-es-while-upgrading-from-2-3-to-5-6/192544/3 "2019-08-30T12:05:51Z")

</div>

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