Troubleshooting monitoring issues
The following table contains the issues you might face while monitoring your Apache Kafka environment and the resolutions.
Issue | Resolution |
|---|---|
Connection failed for - <Kafka-host/service-name>:9092, Error - Failed to create new KafkaAdminClient | Check whether the <host/service-name> is pingable. In case of container, provide the service name from the pod namespace. |
TimeoutException - Connection failed for - < Kafka-host/service-name >:9092, Kafka environment connection timeout. | Check whether the <host/service-name> is pingable and Kafka servers are responding in a timely manner. |
Connection failed for - <host/service-name>:9092, Error - org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: listNodes | Check whether the <host/service-name> is pingable and Kafka servers are responding in a timely manner. |
Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: <host/service-name>; nested exception is: java.net.SocketException: No buffer space available (maximum connections reached?): connect] java.lang.SecurityException: Authentication failed! Credentials required | Check whether JMX authentication is provided in Kafka monitoring policy and is correct. |
SSL error - org.apache.kafka.common.errors.InvalidConfigurationException: SSL key store is specified, but key store password is not specified org.apache.kafka.common.KafkaException: Failed to load SSL keystore as of type JKS org.apache.kafka.common.errors.InvalidConfigurationException: SSL key store is not specified, but key store password is specified | Check whether SSL authentication is provided in Kafka monitoring policy and all the required fields are correct. |