-
Notifications
You must be signed in to change notification settings - Fork 9k
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.
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
[bitnami/kafka] Unexpected Kafka request of type METADATA during SASL handshake. #25129
Comments
Hi,
|
You need to upgrade helm repo to the latest version. Both my two servers and my home computer can reproduce the above problem. You can use the command: helm repo update, or delete bitnami (helm repo remove bitnami) and add it through the command: helm repo add bitnami https://charts.bitnami.com/bitnami Then try again, because the new version has mandatory Sasl security verification, it cannot be started without setting it. Can you give me the allowed clusters using the help command? Instead of running directly through kubectl, version 3.7.0 is required |
There is indeed this issue, and I have also noticed it |
Hi,
And I not getting the |
You need to wait for more than 10 minutes before it will appear. It won't appear when it's just started |
I waited 40 minutes and no errors appeared:
|
We also have the similar setup with 3 brokers. [2024-05-09 10:27:14,590] INFO [SocketServer listenerType=BROKER, nodeId=2] Failed authentication with /xx.x.x.xxx (channelId=xx.x.x.xx:9094-xx.x.x.xxx:59288-261) (Unexpected Kafka request of type METADATA during SASL handshake.) (org.apache.kafka.common.network.Selector) |
Yes, I have raised this issue for a long time, but no one has dealt with it. If security is a concern, configurable parameters should be provided. However, this project has not been maintained, and upgrading the Helm repository version rashly will bring huge losses. The key issue has been raised for a long time but has not been resolved. My program is no longer able to link to my Kafka, but fortunately it is only in my testing environment, otherwise it will cause huge losses |
Many people have mentioned this serious bug in the comments section now. Please help to handle it, as it has caused us some friction losses |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
I need to reproduce the issue in order to identify the cause and look for a fix. Which kubernetes cluster are you using ? |
Hi @rafariossaa , please find details from our end. We have installed kafka on AWS EKS with version 28.0.3, image tag 3.7.0-debian-12-r3, enabled SASL_PLAINTEXT authentication and accessing kafka brokers from outside cluster using clusterIP and ingress nginx service. Error: [2024-05-16 07:30:01,490] INFO [SocketServer listenerType=BROKER, nodeId=1] Failed authentication with /x.x.3.92 (channelId=x.x.3.100:9095-x.x.3.92:50650-88) (Unexpected Kafka request of type METADATA during SASL handshake.) (org.apache.kafka.common.network.Selector) authentication failed with ingress-nginx-controller pod(x.x.3.92) with the broker x.x.3.100:9095. Even though error is appearing in the log we are able to send and consume messages form kafka brokers. Let me know if we have missed any configuration. |
kafkaVersion=3.7.0 image tag bitnami/kafka:3.7.0-debian-12-r6 |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/kafka 3.7.0
What architecture are you using?
amd64
What steps will reproduce the bug?
helm repo update
4.View Running Containers
5.Viewing container logs, this process takes a few minutes to reproduce after the Kafka container is started. I will ignore any extra logs because there are too many of them
Are you using any custom parameters or values?
What is the expected behavior?
1.I hope that the K8S console logs will no longer report errors, and I can create, modify queues, and send messages through the account link I specified, Kafka
2.The startup log of the container keeps reporting errors, and the program cannot connect to Kafka. This problem has been bothering me for a long time, and I have been unable to solve it since upgrading BitNami. I hope the official can provide the correct execution command so that I can minimize the entire 3-node cluster to run
What do you see instead?
The startup log of the container keeps reporting errors, and the program cannot connect to Kafka. This problem has been bothering me for a long time, and I have been unable to solve it since upgrading BitNami. I hope the official can provide the correct execution command so that I can minimize the entire 3-node cluster to run
Additional information
The startup log of the container keeps reporting errors, and the program cannot connect to Kafka. This problem has been bothering me for a long time, and I have been unable to solve it since upgrading BitNami. I hope the official can provide the correct execution command so that I can minimize the entire 3-node cluster to run
The text was updated successfully, but these errors were encountered: