Invalid Configuration class specified on Upgrade to 5.1.2

Elastic Stack Elasticsearch
1

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
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 elasticsearch[14553]: Exception in thread "main" java.lang.IllegalArgumentException: Invalid Configuration class specified
Jan 24 11:28:32 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 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 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 elasticsearch[14553]: at org.elasticsearch.common.logging.LogConfigurator.configureStatusLogger(LogConfigurator.java:125)
Jan 24 11:28:32 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 elasticsearch[14553]: at org.elasticsearch.cli.Command.main(Command.java:85)
Jan 24 11:28:32 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 systemd[1]: Unit elasticsearch.service entered failed state.
Jan 24 11:28:32 es5-mv01.intranet.net systemd[1]: elasticsearch.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

2

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.

3

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!

4

You're welcome.

5

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