Description of problem: it crashed when I was using zookeeper > cli_mt 127.0.0.1:12181 > ls / time = 0 msec /: rc = 0 zookeeper time = 0 msec > quit Quitting... 段错误(吐核) Version-Release number of selected component: zookeeper-3.4.5-12.fc20 Additional info: reporter: libreport-2.1.12 .gdb_history: backtrace_rating: 4 cmdline: cli_mt 127.0.0.1:12181 crash_function: free_completions executable: /usr/bin/cli_mt kernel: 3.12.10-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 free_completions at src/zookeeper.c:1153 #1 zookeeper_close at src/zookeeper.c:2490 #2 api_epilog at src/zookeeper.c:1779 #3 zookeeper_close at src/zookeeper.c:2496 #4 api_epilog at src/zookeeper.c:1779 #5 zookeeper_close at src/zookeeper.c:2496 #6 api_epilog at src/zookeeper.c:1779 #7 zookeeper_close at src/zookeeper.c:2496 #8 api_epilog at src/zookeeper.c:1779 #9 zookeeper_close at src/zookeeper.c:2496
Created attachment 863160 [details] File: backtrace
Created attachment 863161 [details] File: cgroup
Created attachment 863162 [details] File: core_backtrace
Created attachment 863163 [details] File: dso_list
Created attachment 863164 [details] File: environ
Created attachment 863165 [details] File: limits
Created attachment 863166 [details] File: maps
Created attachment 863167 [details] File: open_fds
Created attachment 863168 [details] File: proc_pid_status
Created attachment 863169 [details] File: var_log_messages
Created attachment 863170 [details] File: exploitable
and server log : [myid:0] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:12181:NIOServerCnxn@349] - caught end of stream exception EndOfStreamException: Unable to read additional data from client sessionid 0x442f72a4f90002, likely client has closed socket at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:220) at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208) at java.lang.Thread.run(Thread.java:744) [myid:0] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:12181:NIOServerCnxn@1001] - Closed socket connection for client /127.0.0.1:40483 which had sessionid 0x442f72a4f90002 [myid:0] - WARN [RecvWorker:2:QuorumCnxManager$RecvWorker@762] - Connection broken for id 2, my id = 0, error = java.io.EOFException
zookeeper-3.4.6-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/zookeeper-3.4.6-1.fc21
Package zookeeper-3.4.6-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing zookeeper-3.4.6-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13460/zookeeper-3.4.6-1.fc21 then log in and leave karma (feedback).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.