Hi @abhijithshivaswamy, can you share your elasticsearch.yml, whether you're using the RPM installation or Docker install, and the timing of the error message?

If I fire up a fresh cluster using Docker, that line seems essential, but if you've already removed the plugin or the cluster is already running, I can imagine an error being thrown. Thanks!

from for-elasticsearch-docs.

I Apologise for late reply.
I installed it using RPM, added the opendistro_security.disabled in elasticsearch.yml, and moved the plugins/security out of the installation folder of opendistro.

Then restarted opendistro, and above mentioned exception was being thrown in log file.

Here's the elasticsearch.yml (i have not changed any settings related to elasticsearch, only opendistro settings)

######## Start OpenDistro for Elasticsearch Security Demo Configuration ########

WARNING: revise all the lines below before you go into production

opendistro_security.disabled: true
cluster.routing.allocation.disk.threshold_enabled: false
discovery.zen.minimum_master_nodes: 1
node.max_local_storage_nodes: 3
######## End OpenDistro for Elasticsearch Security Demo Configuration ########

from for-elasticsearch-docs.

Hi @abhijithshivaswamy, gotcha, that's what I suspected. I'll see if I can separate the two operations a bit in the documentation. Basically:

1. If you want to temporarily disable the plugin, but reenable it at a later time, you just add the opendistro_security.disabled line.
2. If you want to completely remove it, you remove the folder.

So it's one or the other. Doing both isn't necessary.

from for-elasticsearch-docs.

oh, i'm sorry then, i read it as both steps are required to disable security.

Thanks for clarifying @aetter 👍

from for-elasticsearch-docs.

Hi @abhijithshivaswamy, no worries at all. If you read it that way, others will, too. I'll separate it with headers or something. Thanks a bunch for reporting!

from for-elasticsearch-docs.