oller: failed to fetch stats, err=zookeeper: dial failed,

[amithrh]

Hi all ,

I am getting this error , please help

oller: failed to fetch stats, err=zookeeper: dial failed, err=&net.OpError{Op:"dial", Net:"tcp", Source:net.Addr(nil), Addr:net.Addr(nil), Err:(*net.DNSError)(0xc42009060

[lucianjon]

Hi, that generally indicates that it can't talk to zookeeper. What kind of setup are you running?

[amithrh]

I am running one zookeeper container along with zookeepeer exporter. Can you please let me know which config files you are referring to .

[regardfs]

same mistake

[lucianjon]

If you're running it inside docker it sounds like a docker networking issue. If you're running locally you should work with the command line flag -servers localhost:2181

[ankitraijr]

Hi, I am getting the same error and I am not running zookeeper in a docker container although I am running zookeeper in a cluster of 3 nodes and I am using only one node's url for zookeeper-exporter. Does this make any difference? Please help..

[altinukshini]

I have a similar issue. I'm using a 3 node zk setup with -servers A:2181,B:2181,C:2181. Everything works fine and I can see zk_ok return 1 for each instance A,B,C. However, if I kill one of the instances, let's say A, I keep seeing zk_ok return 1 for instance A, but the instance is down.... Logs show the following error: poller: failed to fetch stats, err=zookeeper: dial failed, err=&net.OpError{Op:"dial", Net:"tcp", Source:net.Addr(nil), Addr:(*net.TCPAddr)(0xc420156b70), Err:(*os.SyscallError)(0xc420243860)} Maybe there should be a case that handles the failed connection, and marks the instance as down instead of just waiting for a imok?