Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SASL/SCRAM timeouts with 5 sec. Add -m flag to documentation / readme. #317

Closed
AkselAllas opened this issue Apr 22, 2021 · 2 comments
Closed

SASL/SCRAM timeouts with 5 sec. Add -m flag to documentation / readme. #317

AkselAllas opened this issue Apr 22, 2021 · 2 comments

Comments

@AkselAllas
Copy link

AkselAllas commented Apr 22, 2021 •
edited
Loading

I'm using -X security.protocol=SASL_SSL -X sasl.mechanism=SCRAM-SHA-512

To fix my use case I needed to add -m 10. This could be documented better. I read it from a commit message.
Is this normal, that SASL SCRAM takes longer?

For querying metadata, I get the correct response, but I also get this error concatenated at the end:

%3|1619095255.799|FAIL|rdkafka#producer-1| [thrd:sasl_ssl://b-3.msk-2-7-0-aws.kafkaDNSaddress.]: sasl_ssl://b-3.msk-2-7-0-aws.kafkaDNSaddress/3: SASL authentication error: SaslAuthenticateRequest failed: Local: Broker handle destroyed (after 0ms in state DOWN)

I'm using AWS MSK default configs.

Is this error normal?
@AkselAllas
Copy link
Author

I think the error is fine, since I listed all 3 brokers instead of one.

@edenhill
Copy link
Owner

Will improve error message.

edenhill added a commit that referenced this issue May 11, 2021
@edenhill
Fancy up metadata error message (#317)
8916a09
ns-mkusper pushed a commit to ns-mkusper/kcat that referenced this issue Sep 25, 2023
@edenhill @mkusper-rigetti
Fancy up metadata error message (edenhill#317)
2f5fdaf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edenhill @AkselAllas