We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have upgraded AKS from 1.23.8 to 1.24.10 post which we are facing the issues with the exporter and getting the below error:
Failed to read response while authenticating with SASL to broker. read: connection reset by peer
[sarama] 2023/06/05 16:38:55 Error while closing connection to broker dedicated.servicebus.windows.net:9093: tls: failed to send closeNotify alert (but connection was closed anyway): write tcp 10...69:56974->.50..80:9093: write: broken pipe [sarama] 2023/06/05 16:38:55 client/metadata got error from broker -1 while fetching metadata: read tcp 10...69:56974->.50..80:9093: read: connection reset by peer [sarama] 2023/06/05 16:38:55 client/metadata no available broker to send metadata request to [sarama] 2023/06/05 16:38:55 client/brokers resurrecting 1 dead seed brokers [sarama] 2023/06/05 16:38:55 client/metadata retrying after 250ms... (1 attempts remaining) [sarama] 2023/06/05 16:38:55 client/metadata fetching metadata for all topics from broker dedicated.servicebus.windows.net:9093 [sarama] 2023/06/05 16:38:56 Successful SASL handshake. Available mechanisms: [PLAIN OAUTHBEARER] [sarama] 2023/06/05 16:38:57 Failed to read response while authenticating with SASL to broker dedicated.servicebus.windows.net:9093: read tcp 10...69:56984->.50..80:9093: read: connection reset by peer
We are using 1.3.0 version of the kafka exporter.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We have upgraded AKS from 1.23.8 to 1.24.10 post which we are facing the issues with the exporter and getting the below error:
Failed to read response while authenticating with SASL to broker. read: connection reset by peer
[sarama] 2023/06/05 16:38:55 Error while closing connection to broker dedicated.servicebus.windows.net:9093: tls: failed to send closeNotify alert (but connection was closed anyway): write tcp 10...69:56974->.50..80:9093: write: broken pipe
[sarama] 2023/06/05 16:38:55 client/metadata got error from broker -1 while fetching metadata: read tcp 10...69:56974->.50..80:9093: read: connection reset by peer
[sarama] 2023/06/05 16:38:55 client/metadata no available broker to send metadata request to
[sarama] 2023/06/05 16:38:55 client/brokers resurrecting 1 dead seed brokers
[sarama] 2023/06/05 16:38:55 client/metadata retrying after 250ms... (1 attempts remaining)
[sarama] 2023/06/05 16:38:55 client/metadata fetching metadata for all topics from broker dedicated.servicebus.windows.net:9093
[sarama] 2023/06/05 16:38:56 Successful SASL handshake. Available mechanisms: [PLAIN OAUTHBEARER]
[sarama] 2023/06/05 16:38:57 Failed to read response while authenticating with SASL to broker dedicated.servicebus.windows.net:9093: read tcp 10...69:56984->.50..80:9093: read: connection reset by peer
We are using 1.3.0 version of the kafka exporter.
The text was updated successfully, but these errors were encountered: