# 6.2.1 to 6.4 upgrade results in X-pack 'NoSuchFileException' issue

**URL:** <https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935>\
**Category:** Elasticsearch\
**Created:** [August 24, 2018, 2:59pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935 "2018-08-24T14:59:49Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![stevedearl](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@stevedearl](https://discuss.elastic.co/u/stevedearl)\
**Post date:** [August 24, 2018, 2:59pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/1 "2018-08-24T14:59:49Z")

</div>

Hi All,

I tried running an offline RPM upgrade of the new Elasticsearch 6.4 on top of my existing 6.2.1 environment. The original environment has X-pack installed on it, configured to provide just a basic licence (so no Watcher, Machine learning etc.).

Unfortunately, after the upgrade when I try to restart Elasticsearch I see this error:

> [2018-08-24T14:41:28,557][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [OVF\_SharedServices\_ElasticNode\_gbdocldibgdap02] uncaught exception in thread [main]  
> org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Could not load plugin descriptor for plugin directory [x-pack]  
> at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:140) ~[elasticsearch-6.4.0.jar:6.4.0]

with, a few lines further down:

> Caused by: java.nio.file.NoSuchFileException: /usr/share/elasticsearch/plugins/x-pack/plugin-descriptor.properties  
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) ~[?:?]

I also see a similar error when trying to list the plugins:

> [root@gbdocldibgdap02 bin]# ./elasticsearch-plugin list  
> x-pack  
> Exception in thread "main" java.nio.file.NoSuchFileException: /usr/share/elasticsearch/plugins/x-pack/plugin-descriptor.properties

I know that from 6.3 onwards ELK came with more x-pack goodness included, so there was no additional install anymore. Does this mean I should have removed the x-pack plugin from my 6.2.1 environment before doing the RPM upgrade?

All help appreciated!

Regards,  
Steve

---

<div class="post-metadata">

**Author:** ![funtimes](https://avatars.discourse-cdn.com/v4/letter/f/f08c70/32.png) [@funtimes](https://discuss.elastic.co/u/funtimes)\
**Post date:** [August 25, 2018, 5:40pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/2 "2018-08-25T17:40:06Z")

</div>

I'm having the exact same issue, would love to hear from anybody who has found a fix for this problem.

---

<div class="post-metadata">

**Author:** ![funtimes](https://avatars.discourse-cdn.com/v4/letter/f/f08c70/32.png) [@funtimes](https://discuss.elastic.co/u/funtimes)\
**Post date:** [August 25, 2018, 6:52pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/3 "2018-08-25T18:52:09Z")

</div>

So I figured out a way to get elasticsearch up and running again after this issue.

Inside of the directory:

> /usr/share/elasticsearch/plugins

backup/remove all plugins including x-pack

After all plugins are removed, reinstall the latest versions of your plugins in my case it was only two

> bin/elasticsearch-plugin install ingest-geoip  
> bin/elasticsearch-plugin install ingest-user-agent  
> systemctl restart elasticsearch.service

And now my system is back to normal

---

<div class="post-metadata">

**Author:** ![stevedearl](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@stevedearl](https://discuss.elastic.co/u/stevedearl)\
**Post date:** [August 25, 2018, 7:05pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/4 "2018-08-25T19:05:55Z")

</div>

Hi Funtimes,

Thanks for the information. I'll be trying this when i get back into the office!

Cheers,

Steve

![](https://us1.discourse-cdn.com/elastic/original/3X/4/5/45e09ece765657a92cb26fd1d4a3a227eb567ea3.png "funtimes")  
[funtimes](https://discuss.elastic.co/u/funtimes)

August 25  
So I figured out a way to get elasticsearch up and running again after this issue.

Inside of the directory:

> /usr/share/elasticsearch/plugins

backup/remove all plugins including x-pack

After all plugins are removed, reinstall the latest versions of your plugins in my case it was only two

> bin/elasticsearch-plugin install ingest-geoip
> 
> bin/elasticsearch-plugin install ingest-user-agent
> 
> systemctl restart elasticsearch.service

And now my system is back to normal

---

<div class="post-metadata">

**Author:** ![it-chief](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/it-chief/32/29360_2.png) [@it-chief](https://discuss.elastic.co/u/it-chief)\
**Post date:** [September 18, 2018, 1:52pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/5 "2018-09-18T13:52:27Z")

</div>

Thanks. Worked like a charm for me.

---

<div class="post-metadata">

**Author:** ![funtimes](https://avatars.discourse-cdn.com/v4/letter/f/f08c70/32.png) [@funtimes](https://discuss.elastic.co/u/funtimes)\
**Post date:** [September 18, 2018, 2:27pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/6 "2018-09-18T14:27:06Z")

</div>

Glad it worked!

---

<div class="post-metadata">

**Author:** ![run4fun3](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@run4fun3](https://discuss.elastic.co/u/run4fun3)\
**Post date:** [October 1, 2018, 8:26pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/7 "2018-10-01T20:26:00Z")

</div>

THANK YOU!!! work for me too. I guess with the new way x-pack is installed by default it messed everything up. I could not get ES to start until I found this thread.

---

<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:** [October 29, 2018, 8:26pm UTC](https://discuss.elastic.co/t/6-2-1-to-6-4-upgrade-results-in-x-pack-nosuchfileexception-issue/145935/8 "2018-10-29T20:26:01Z")

</div>

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