Pinpoint: zookeeper Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect

Created on 27 Jul 2018  Â·  9Comments  Â·  Source: pinpoint-apm/pinpoint

2018-07-27 17:19:31 WARN Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2018-07-27 17:19:31 WARN handleUpdate failed. caused:Instance must be connected., jobSize:1
com.navercorp.pinpoint.collector.cluster.zookeeper.exception.ConnectionException: Instance must be connected.
at com.navercorp.pinpoint.collector.cluster.zookeeper.DefaultZookeeperClient.checkState(DefaultZookeeperClient.java:273)
at com.navercorp.pinpoint.collector.cluster.zookeeper.DefaultZookeeperClient.exists(DefaultZookeeperClient.java:255)
at com.navercorp.pinpoint.collector.cluster.zookeeper.ZookeeperJobWorker.handleUpdate(ZookeeperJobWorker.java:341)
at com.navercorp.pinpoint.collector.cluster.zookeeper.ZookeeperJobWorker.handle(ZookeeperJobWorker.java:323)
at com.navercorp.pinpoint.collector.cluster.zookeeper.ZookeeperJobWorker.run(ZookeeperJobWorker.java:228)
at java.lang.Thread.run(Thread.java:745)
2018-07-27 17:19:32 WARN handleUpdate failed. caused:Instance must be connected., jobSize:1
com.navercorp.pinpoint.collector.cluster.zookeeper.exception.ConnectionException: Instance must be connected.
at com.navercorp.pinpoint.collector.cluster.zookeeper.DefaultZookeeperClient.checkState(DefaultZookeeperClient.java:273)
at com.navercorp.pinpoint.collector.cluster.zookeeper.DefaultZookeeperClient.exists(DefaultZookeeperClient.java:255)
at com.navercorp.pinpoint.collector.cluster.zookeeper.ZookeeperJobWorker.handleUpdate(ZookeeperJobWorker.java:341)
at com.navercorp.pinpoint.collector.cluster.zookeeper.ZookeeperJobWorker.handle(ZookeeperJobWorker.java:323)
at com.navercorp.pinpoint.collector.cluster.zookeeper.ZookeeperJobWorker.run(ZookeeperJobWorker.java:228)
at java.lang.Thread.run(Thread.java:745)
2018-07-27 17:19:32 WARN Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect

pinpoint version:1.7.3
zookeeper version: 3.4.6

stale

All 9 comments

Hello, @god8816
Do check your configuration on your zookeeper cluster's address

Hello,@RoySRose
my zookeeper single node , not cluster's。

@god8816
I hope you write a little more detailed explanation.
If disconnected from the zookeeper server, this is a normal log.

Therefore, it is impossible to judge whether there is a problem.

Please explain in detail what kind of operation after connection brokened.
It is even better if you give them a situation that can be reproduced.

@koo-taejin zookeeper
[admin@vm-xaj-vmc-pinpoint-collector-d01 classes]$ telnet zookeeper-test.idc.yst.com.cn 2181
Trying 10.213.2.141...
Connected to zookeeper-test.idc.yst.com.cn.
Escape character is '^]'
it can connected from the zookeeper server

@koo-taejin why pinpoint can not Connected zookeeper?

@god8816

Please check your zookeepr related settings.
If there are no problems with the settings.
It is recommended to test the connection using the Zookeeper library.

same problem here.

But my pinpoint was working before today. Now It's broken, I check the log. It's the same issue. connects ZK refused.

This issue/proposal has been automatically marked as stale because it hasn't had any recent activity. It will automatically be closed if no further activity occurs for 20days. If you think this should still be open, or the problem still persists, just pop a reply in the comments and one of the maintainers will (try!) to follow up. Thank you for your interest and contribution to the Pinpoint Community.

zookeeper Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
_"server null"_ indicates that you have forgotten to pass the server parameters while running your zookeeper CLI.
Your command should be like this:
./zkCli.sh -server
If you don't specify port it will take the default 2181.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

geniuszhe picture geniuszhe  Â·  3Comments

yanpeng-ali picture yanpeng-ali  Â·  3Comments

08s011003 picture 08s011003  Â·  3Comments

ing-arriola picture ing-arriola  Â·  3Comments

Allive1 picture Allive1  Â·  5Comments