Elastic update from 5.6.10 to 6.2.3 failed

Graylog Central (peer support)
1

Hi, in our Test Graylog Enviroment we updatet Graylog from 2.4.6 to 2.5.2. Then we would update Elastic from 5.6.1 to 6.2.3.
After the update Elastic did not start and we got following error:

[2019-04-17T16:35:08,051][ERROR][o.e.b.Bootstrap ] Exception
java.lang.IllegalArgumentException: unknown setting [path.conf] please check that any required plugins are installed, or check the breaking c
hanges documentation for removed settings
at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:346) ~[elasticsearch-6.2.3.jar:6.2.3
]
We only stop the Elastic Service and install the new Version with rpm. Our elasticsearch.yml was not changed after the update.

path:
conf: /etc/elasticsearch
data: /data1/elasticsearch
logs: /var/log/elasticsearch

Any Idea?

2

Hello MaBe,

probably you will find in /etc/graylog/ and /etc/elasticsearch/ new config files with the suffic .rpmnew, for example /etc/elasticsearch/jvm.options.rpmnew.
Make a diff to the existing config file to find out about new config settings, or changes to be made.
Example:
diff jvm.options jvm.options.rpmnew

After this try to start again. But it makes sense to have a backup of the existing config files!

Regards,

Dietmar

3

We only stop the Elastic Service and install the new Version with rpm. Our elasticsearch.yml was not changed after the update.

That is a mistake - you should have read the upgrade notes of Elasticsearch …

4

It shows the error… I suggest read the error message again.
Maybe the parameters in the config file changed.
Check the .rpmsave file.
And as @jan said, RTFM.

5

We have also recognized that. Trial and error was not a good idea. Presumably we have to reinstall Elasticserach?

6

. Presumably we have to reinstall Elasticserach?

just read the error, read the upgrade guide and correct the configuration.

7

We had now our Elasticsearch on Version 6.7.1. It was the settings in the /etc/elasticsearch/elasticsearch.yml with the Paths.
So, next Problem. Then we update Graylog to 3.0.1. The server started, but the we got in the server.log the following error:
2019-04-23T14:18:57.850+02:00 ERROR [SerializedLogEventCodec] Couldn’t deserialize log event
java.lang.IllegalArgumentException: readObject requires a FilteredObjectInputStream or an ObjectInputStream that accepts an ObjectInputFilter
at org.apache.logging.log4j.util.SortedArrayStringMap.readObject(SortedArrayStringMap.java:596) ~[graylog.jar:?]
at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]

8

what java Version did you have installed on this server?

9

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