Re: Can't produce message with SASL: timeout error

2017-02-16 Thread Stephane Maarek
It seems to be conflicting when I try running the commands on the same box as where Kafka is running. I think it was inheriting Kafka's principal somehow and not the kafkaclient principal. When moving to another box all seems to work ! An odd one I see if I can reproduce and open a JIRA On 17 Feb.

Re: Can't produce message with SASL: timeout error

2017-02-16 Thread Manikumar
Pl enable authorizer logs ( config/log4j.properties) and check if operations are getting denied. Also, enable producer debug logs (config/tools-log4j.properties) to check for any errors. On Fri, Feb 17, 2017 at 10:34 AM, Stephane Maarek < steph...@simplemachines.com.au> wrote: > Hi, > > I secure

Can't produce message with SASL: timeout error

2017-02-16 Thread Stephane Maarek
Hi, I secured my cluster and everything was working fine. Brokers are up and don’t complain, my topics are all synchronized. Here’s my config (excerpt): listeners= PLAINTEXT://0.0.0.0:9092,SSL://0.0.0.0:9093,SASL_PLAINTEXT://0.0.0.0:9094,SASL_SSL://0.0.0.0:9095 super.users=User:kafka;User:ANONYMO