Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    Stop all kafka and zookeper proccesses ("ps -aux | grep zoo" and "ps -aux | grep kafka" and kill all the proccess ids) then, run zookeper and then run kafka server.

Solutions on the web

via GitHub by drcrallen
, 1 year ago
Unable to connect to zookeeper server within timeout: 30000
via GitHub by gianm
, 1 year ago
Unable to connect to zookeeper server within timeout: 30000
via GitHub by drcrallen
, 1 year ago
Unable to connect to zookeeper server within timeout: 30000
via GitHub by binlijin
, 1 year ago
Unable to connect to zookeeper server within timeout: 6000
via GitHub by gianm
, 1 year ago
Unable to connect to zookeeper server within timeout: 6000
via GitHub by nishantmonu51
, 1 year ago
Unable to connect to zookeeper server within timeout: 6000
org.I0Itec.zkclient.exception.ZkTimeoutException: Unable to connect to zookeeper server within timeout: 30000	at org.I0Itec.zkclient.ZkClient.connect(ZkClient.java:1223)	at org.I0Itec.zkclient.ZkClient.(ZkClient.java:155)	at org.I0Itec.zkclient.ZkClient.(ZkClient.java:129)	at kafka.utils.ZkUtils$.createZkClientAndConnection(ZkUtils.scala:89)	at kafka.utils.ZkUtils$.apply(ZkUtils.scala:71)	at kafka.server.KafkaServer.initZk(KafkaServer.scala:278)	at kafka.server.KafkaServer.startup(KafkaServer.scala:168)	at io.druid.indexing.kafka.test.TestBroker.start(TestBroker.java:73)	at io.druid.indexing.kafka.KafkaIndexTaskTest.setUp(KafkaIndexTaskTest.java:248)