java.io.IOException

ZooKeeperServer not running 2014-10-27 23:06:36,845 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007] - Closed socket connection for client /141.105.120.150:47142 (no session established for client) ..... 2014-10-28 00:07:18,464 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868] - Client attempting to establish new session at /141.105.125.180:56530 2014-10-28 00:07:18,468 [myid:2] - INFO [CommitProcessor:2:ZooKeeperServer@617] - Established session 0x24954020e470268 with negotiated timeout 6000 for client /141.105.125.180:56530 2014-10-28 00:07:18,483 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007] - Closed socket connection for client /141.105.125.180:56530 which had sessionid 0x24954020e470268 2014-10-28 00:07:18,632 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /178.21.116.224:45958 2014-10-28 00:07:18,632 [myid:2] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822] - Connection request from old client /178.21.116.224:45958; will be dropped if server is in r-o mode 2014-10-28 00:07:18,632 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868] - Client attempting to establish new session at /178.21.116.224:45958 2014-10-28 00:07:18,636 [myid:2] - INFO [CommitProcessor:2:ZooKeeperServer@617] - Established session 0x24954020e470269 with negotiated timeout 6000 for client /178.21.116.224:45958 2014-10-28 00:07:18,650 [myid:2] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of stream exception EndOfStreamException: Unable to read additional data from client sessionid 0x24954020e470269, likely client has closed socket

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web11

  • via GitHub by nsphung
    ,
  • Stack trace

    • java.io.IOException: ZooKeeperServer not running 2014-10-27 23:06:36,845 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007] - Closed socket connection for client /141.105.120.150:47142 (no session established for client) ..... 2014-10-28 00:07:18,464 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868] - Client attempting to establish new session at /141.105.125.180:56530 2014-10-28 00:07:18,468 [myid:2] - INFO [CommitProcessor:2:ZooKeeperServer@617] - Established session 0x24954020e470268 with negotiated timeout 6000 for client /141.105.125.180:56530 2014-10-28 00:07:18,483 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007] - Closed socket connection for client /141.105.125.180:56530 which had sessionid 0x24954020e470268 2014-10-28 00:07:18,632 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /178.21.116.224:45958 2014-10-28 00:07:18,632 [myid:2] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822] - Connection request from old client /178.21.116.224:45958; will be dropped if server is in r-o mode 2014-10-28 00:07:18,632 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868] - Client attempting to establish new session at /178.21.116.224:45958 2014-10-28 00:07:18,636 [myid:2] - INFO [CommitProcessor:2:ZooKeeperServer@617] - Established session 0x24954020e470269 with negotiated timeout 6000 for client /178.21.116.224:45958 2014-10-28 00:07:18,650 [myid:2] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of stream exception EndOfStreamException: Unable to read additional data from client sessionid 0x24954020e470269, likely client has closed socket at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228) at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitor2 times, last one