Closed jpcarey closed 1 year ago
Pinging @elastic/es-core-infra
Just to make sure I properly understand: Did you leave out bin/elasticsearch-keystore add-file xpack.watcher.encryption_key <filepath>/system_key
on purpose or is the exception thrown the bug you reported, when you did not call this?
@spinscale intentionally skipped adding the system_key to the keystore. I would expect an error that it wasn’t properly configured, rather than a NPE. On Tue, May 8, 2018 at 2:28 AM Alexander Reelsen notifications@github.com wrote:
Just to make sure I properly understand: Did you leave out bin/elasticsearch-keystore add-file xpack.watcher.encryption_key
/system_key on purpose or is the exception thrown the bug you reported, when you did not call this? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/elastic/elasticsearch/issues/30441#issuecomment-387325860, or mute the thread https://github.com/notifications/unsubscribe-auth/AE4aBpR9NdFI-l3KhIklqdCvIaptZqXsks5twVc4gaJpZM4T1tAZ .
Just had this same error.. After adding the system key in the elasticsearch keystore the issue was solved.
@willemdh how did you add the key ? When I tried it, the key and encryption were not taken into account unless I don't restart the node. However, on restarting the nodes, I still get the same NPE stack since the key is lost, i.e. it's not persistent.
Copied the system key from another node and imported it
Elasticsearch version: 6.2.4
Plugins installed: x-pack
Description of the problem including expected versus actual behavior: org.elasticsearch.bootstrap.StartupException NPE when configuring to use system_key.
Steps to reproduce:
$ echo -e "xpack.watcher.encrypt_sensitive_data: true\n$(cat config/elasticsearch.yml)" > config/elasticsearch.yml
$ bin/elasticsearch
Provide logs: