# Service start fail after Upgrade 5.6.12 to latest

**URL:** <https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968>\
**Category:** Elasticsearch\
**Created:** [February 4, 2019, 1:56pm UTC](https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968 "2019-02-04T13:56:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ronny\_Preiss](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@Ronny\_Preiss](https://discuss.elastic.co/u/Ronny_Preiss)\
**Post date:** [February 4, 2019, 1:56pm UTC](https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968/1 "2019-02-04T13:56:02Z")

</div>

Hi @ all, 🙂

I've updated ES from 5.6.12 to the latest version and can't start the service anymore.

I've done this with the following steps:

```
wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add -
echo "deb https://artifacts.elastic.co/packages/6.x/apt stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-6.x.list
apt update &amp;&amp; apt install elasticsearch

```

After This I Have to set _ES\_PATH\_CONF=/etc/elasticsearch_ in _/etc/default/elasticsearch_ then dpkg finished successfully.

Now when I try to start the service with _systemctl start elasticsearch_ I got the following error:  
[https://pastebin.com/q1Tzu5H6](https://pastebin.com/q1Tzu5H6)

When I try to start ES manually as elasticsearch user with _sudo -i -u elasticsearch /usr/share/elasticsearch/bin/elasticsearch_ I get the following error:  
[https://pastebin.com/CawfYLWG](https://pastebin.com/CawfYLWG)

I use ES with Graylog.

Here all Files:  
/etc/default/elasticsearch  
[https://pastebin.com/zZ9tfGX3](https://pastebin.com/zZ9tfGX3)

/usr/lib/systemd/system/elasticsearch.service  
[https://pastebin.com/4Qft9d8Y](https://pastebin.com/4Qft9d8Y)

/etc/elasticsearch/elasticsearch.yml  
[https://pastebin.com/dhYtWXZJ](https://pastebin.com/dhYtWXZJ)

Now I'm stuck and need some help 🙂

Greetings

Ronny

---

<div class="post-metadata">

**Author:** ![Ronny\_Preiss](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@Ronny\_Preiss](https://discuss.elastic.co/u/Ronny_Preiss)\
**Post date:** [February 4, 2019, 2:58pm UTC](https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968/2 "2019-02-04T14:58:14Z")

</div>

Hi,

I think I have solved my initial issue with setting `path.data:` and `path.logs:` to `/var/lib/elasticsearch`. There is the old Elasticsearch 5.6.12 data stored. I've found the path it with `echo $ES_HOME`.

Now i get another error that i cant solve anymore.  
[https://pastebin.com/u03aNFUC](https://pastebin.com/u03aNFUC)

There is an error but but i cant find a solution for this.

```
Caused by: java.security.AccessControlException: access denied ("java.io.FilePermission" "/etc/graylog/server/ssl/cacerts.jks" "read")

```

But I don't know how to solve it.

I tried the following without success

- `chmod 777`
- `chown root:root`
- `chown elasticsearch:elasticsearch`

Greetings 😕

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 4, 2019, 4:25pm UTC](https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968/3 "2019-02-04T16:25:49Z")

</div>

For security reasons, Elasticsearch will only read config files from within its config directory. Is `/etc/graylog/server/ssl/` a subdirectory of the Elasticsearch config directory?

---

<div class="post-metadata">

**Author:** ![Ronny\_Preiss](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@Ronny\_Preiss](https://discuss.elastic.co/u/Ronny_Preiss)\
**Post date:** [February 5, 2019, 6:12am UTC](https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968/4 "2019-02-05T06:12:19Z")

</div>

Hi,

thanks for reply. 🙂

`/etc/graylog/server/ssl/` is the graylog ssl directory.

The Elasticsearch config is `ES_PATH_CONF=/etc/elasticsearch`

Befor I upgraded Elasticsearch from 5.6.12 to 6.6 this config works without any problems.

How could i solve this?

---

<div class="post-metadata">

**Author:** ![Ronny\_Preiss](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@Ronny\_Preiss](https://discuss.elastic.co/u/Ronny_Preiss)\
**Post date:** [February 5, 2019, 7:43am UTC](https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968/5 "2019-02-05T07:43:08Z")

</div>

Just a workaround but it help for the moment.

I just removed`-Djavax.net.ssl.trustStore=/etc/graylog/server/ssl/cacerts.jks` in `/etc/defaults/elasticsearch`

Now Elsticsearch starts normaly.

---

<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:** [March 5, 2019, 7:43am UTC](https://discuss.elastic.co/t/service-start-fail-after-upgrade-5-6-12-to-latest/166968/6 "2019-03-05T07:43:11Z")

</div>

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