Unknown setting 'jass_path' for kafka in kafka input

Elastic Stack Logstash
1

Hi,

I'm trying to configure logstash to connect to confluent cloud kafka using input configuration a jaas file

using docker compose with logstash image version 6.0.1 (also tried with v6.8)

my docker service looks like this

logstash:
image: docker.elastic.co/logstash/logstash:6.0.1
container_name: logstash--dev
volumes:
- ./logstash/config/logstash.yml:/usr/share/logstash/config/logstash.yml:ro
- ./logstash/config/confluent_jass.conf:/usr/share/logstash/config/confluent_jass.conf:ro
- ./logstash/config/pipelines.yml:/usr/share/logstash/config/pipelines.yml:ro
- ./logstash/pipeline:/usr/share/logstash/pipeline:ro

environment:
  LS_JAVA_OPTS: "-Xmx256m -Xms256m"
ports:
  - "5000:5000"
depends_on: 
  - elasticsearch
  - broker

my jaas files configuration looks like this:

KafkaClient {
org.apache.kafka.common.security.plain.PlainLoginModule required
serviceName="Logatsh"
username="some username"
password="some pass";
};

And My input configuration looks like this:

kafka {

	group_id => "my-lgstash-consumers"
	topics => ["topic1", "topic2"]
	bootstrap_servers => "myserverdomain:9092"
	security_protocol => "SASL_SSL"
	sasl_mechanism => "PLAIN"		
	jass_path => "/usr/share/logstash/config/confluent_jass.conf"
	 codec => json {
	 	charset => "UTF-8"
	 }
}

However when I run it I get an error log:

[ERROR][logstash.inputs.kafka ] Unknown setting 'jass_path' for kafka
[2019-06-10T08:43:07,788][ERROR][logstash.agent ] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:events-pipeline, :exception=>"LogStash::ConfigurationError", :message=>"Something is wrong with your configuration.", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/config/mixin.rb:86:in config_init'", "/usr/share/logstash/logstash-core/lib/logstash/inputs/base.rb:60:ininitialize'", "org/logstash/plugins/PluginFactoryExt.java:255:in plugin'", "org/logstash/plugins/PluginFactoryExt.java:184:inplugin'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:71:in plugin'", "(eval):24:ininitialize'", "org/jruby/RubyKernel.java:1061:in eval'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:49:ininitialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:90:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:43:inblock in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:96:in block in exclusive'", "org/jruby/ext/thread/Mutex.java:165:insynchronize'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:96:in exclusive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:39:inexecute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:334:in `block in converge_state'"]}

2

solved , it was a typo in the name

3

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