# Invalid Configuration class specified on Upgrade to 5.1.2

**URL:** <https://discuss.elastic.co/t/invalid-configuration-class-specified-on-upgrade-to-5-1-2/72623>\
**Category:** Elasticsearch\
**Created:** [January 24, 2017, 11:34am UTC](https://discuss.elastic.co/t/invalid-configuration-class-specified-on-upgrade-to-5-1-2/72623 "2017-01-24T11:34:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![CharliesL](https://avatars.discourse-cdn.com/v4/letter/c/a183cd/32.png) [@CharliesL](https://discuss.elastic.co/u/CharliesL)\
**Post date:** [January 24, 2017, 11:34am UTC](https://discuss.elastic.co/t/invalid-configuration-class-specified-on-upgrade-to-5-1-2/72623/1 "2017-01-24T11:34:21Z")

</div>

Hi,

I've just tried to upgrade from 5.0.1 to 5.1.2 using the rpm.

I did rpm -i --force elasticsearch-5.1.2.rpm  
(i hope that is correct)

But then when trying to start it up I get the following problem and cannot figure out why  
service elasticsearch status  
● elasticsearch.service - Elasticsearch  
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)  
Active: failed (Result: exit-code) since Tue 2017-01-24 11:28:32 GMT; 3s ago  
Docs: [http://www.elastic.co](http://www.elastic.co)  
Process: 14553 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: 14551 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)  
Main PID: 14553 (code=exited, status=1/FAILURE)

Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) elasticsearch[14553]: Exception in thread "main" java.lang.IllegalArgumentException: Invalid Configuration class specified  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) elasticsearch[14553]: at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(Default...ava:193)  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) elasticsearch[14553]: at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(Default...ava:157)  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) elasticsearch[14553]: at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(Default...java:54)  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) elasticsearch[14553]: at org.elasticsearch.common.logging.LogConfigurator.configureStatusLogger(LogConfigurator.java:125)  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) elasticsearch[14553]: at org.elasticsearch.common.logging.LogConfigurator.configureWithoutConfig(LogConfigurator.java:67)  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) elasticsearch[14553]: at org.elasticsearch.cli.Command.main(Command.java:85)  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) systemd[1]: Unit elasticsearch.service entered failed state.  
Jan 24 11:28:32 [es5-mv01.intranet.net](http://es5-mv01.intranet.net) systemd[1]: elasticsearch.service failed.  
Hint: Some lines were ellipsized, use -l to show in full.

---

<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:** [January 24, 2017, 12:09pm UTC](https://discuss.elastic.co/t/invalid-configuration-class-specified-on-upgrade-to-5-1-2/72623/2 "2017-01-24T12:09:56Z")

</div>

> [@CharliesL](#):
>
> I've just tried to upgrade from 5.0.1 to 5.1.2 using the rpm.
> 
> I did rpm -i --force elasticsearch-5.1.2.rpm(i hope that is correct)

No, it's not correct, and I suspect that's the source of your problem. To upgrade, you should do `rpm -U` or `rpm --upgrade`. I suspect that you have conflicting JARs lying around. I think at this point you want to uninstall and reinstall (perhaps even checking that `/usr/share/elasticsearch/lib` is completely empty between uninstalling and installing.

---

<div class="post-metadata">

**Author:** ![CharliesL](https://avatars.discourse-cdn.com/v4/letter/c/a183cd/32.png) [@CharliesL](https://discuss.elastic.co/u/CharliesL)\
**Post date:** [January 24, 2017, 12:10pm UTC](https://discuss.elastic.co/t/invalid-configuration-class-specified-on-upgrade-to-5-1-2/72623/3 "2017-01-24T12:10:52Z")

</div>

Yep I thought it was the cause. Have now rolled back and done the it with the upgrade command and it's working now.

Thanks!

---

<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:** [January 24, 2017, 12:29pm UTC](https://discuss.elastic.co/t/invalid-configuration-class-specified-on-upgrade-to-5-1-2/72623/4 "2017-01-24T12:29:17Z")

</div>

You're welcome.

---

<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:** [February 21, 2017, 12:29pm UTC](https://discuss.elastic.co/t/invalid-configuration-class-specified-on-upgrade-to-5-1-2/72623/5 "2017-02-21T12:29:51Z")

</div>

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