Setting "xpack.security.enabled" hasn't been registered

Hi, I installed x-pack on elasticsearch, logstash and kibana set the appropriate settings kibana and elasticsearch are working just fine but i get the following error in logstash.

An unexpected error occurred! {:error=>#<ArgumentError: Setting "xpack.security.enabled" hasn't been registered>, :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/settings.rb:32:inget_setting'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:65:in set_value'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:84:inblock in merge'", "org/jruby/RubyHash.java:1343:in each'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:84:inmerge'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:133:in validate_all'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:280:inexecute'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:in run'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:232:inrun'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/clamp-0.6.5/lib/clamp/command.rb:132:in run'", "/usr/share/logstash/lib/bootstrap/environment.rb:71:in'"]}`

logstash.yml
xpack.management.enabled: true
xpack.management.elasticsearch.username: ""
xpack.monitoring.enabled: true
xpack.security.enabled: false

cheers!
rob

Hi Rob,

See this issue; https://github.com/elastic/logstash/issues/8493

It's not expanding here like I thought public github issues usually do, so I'll elaborate on what's in that issue;

In Elastic and Kibana, when x-pack is installed but the security is disabled, you have the following setting in config file:

xpack.security.enabled: false
But in logstash, this setting does not exist.
Instead, you have to provide and empty login and an empty password :

xpack.monitoring.elasticsearch.url: http://localhost:9201
xpack.monitoring.elasticsearch.username: 
xpack.monitoring.elasticsearch.password:

Regards,
Lee

1 Like

@LeeDr that fixed it thanks !

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