Rolling to 7.13

Elastic Stack Elasticsearch
1

Hola,

I am pretty new to ElasticSearch. I am trying to upgrade my node from 7.6 to 7.13. It happened that when I run my new node with 7.13, the console throws a mistake. I have searched without success on how to solve it. Can you guys orient me on what to do?

Screenshot 2021-06-16 at 18.13.33
Screenshot 2021-06-16 at 18.13.331767×553 359 KB

2

Welcome!

Please don't post images of text as they are hard to read, may not display correctly for everyone, and are not searchable.

Instead, paste the text and format it with </> icon or pairs of triple backticks (```), and check the preview window to make sure it's properly formatted before posting it. This makes it more likely that your question will receive a useful answer.

It would be great if you could update your post to solve this.

3

Hola David, thanks for your answer. I just updated the question accordingly.
Thanks for your help, in advance.

Exception in thread "main" org.elasticsearch.bootstrap.BootstrapException: java.nio.file.FileAlreadyExistsException: /home/hamlet/node2/elasticsearch-7.13.1/config/elasticsearch.keystore.tmp
Likely root cause: java.nio.file.FileAlreadyExistsException: /home/hamlet/node2/elasticsearch-7.13.1/config/elasticsearch.keystore.tmp
        at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:94)
        at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
        at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
        at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:219)
        at java.base/java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:478)
        at java.base/java.nio.file.Files.newOutputStream(Files.java:224)
        at org.apache.lucene.store.FSDirectory$FSIndexOutput.<init>(FSDirectory.java:410)
        at org.apache.lucene.store.FSDirectory$FSIndexOutput.<init>(FSDirectory.java:406)
        at org.apache.lucene.store.FSDirectory.createOutput(FSDirectory.java:254)
        at org.elasticsearch.common.settings.KeyStoreWrapper.save(KeyStoreWrapper.java:484)
        at org.elasticsearch.bootstrap.Bootstrap.loadSecureSettings(Bootstrap.java:253)
        at org.elasticsearch.bootstrap.Bootstrap.loadSecureSettings(Bootstrap.java:228)
        at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:343)
        at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159)
        at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150)
        at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:75)
        at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:116)
        at org.elasticsearch.cli.Command.main(Command.java:79)
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115)
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:81)`Preformatted text`
4

I don't know how you entered in that situation. May be you should remove manually the file /home/hamlet/node2/elasticsearch-7.13.1/config/elasticsearch.keystore.tmp? And then start Elasticsearch.

5

it is complaning about this file. what is this file? what is the permission of this dir?

6

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