Red Hat Bugzilla – Bug 865040
[abrt] python-2.7.3-13.fc18: zmq::zmq_abort: Process /usr/bin/python2.7 was killed by signal 6 (SIGABRT)
Last modified: 2013-02-20 16:27:34 EST
Description of problem:
Not sure, was running fedmsg-notify, there was a slight network problem, and then abrt notified me about a crash
Version-Release number of selected component:
libreport version: 2.0.15
cmdline: /usr/bin/python /usr/bin/fedmsg-notify-daemon
:Thread no. 1 (7 frames)
: #2 zmq::zmq_abort at err.cpp:76
: #3 zmq::zmq_connecter_t::zmq_connecter_t at zmq_connecter.cpp:48
: #4 zmq::connect_session_t::start_connecting at connect_session.cpp:59
: #5 zmq::session_t::detach at session.cpp:283
: #6 zmq::zmq_engine_t::error at zmq_engine.cpp:217
: #7 zmq::epoll_t::loop at epoll.cpp:161
: #8 thread_routine at thread.cpp:75
Created attachment 625020 [details]
Created attachment 625021 [details]
Created attachment 625022 [details]
Created attachment 625023 [details]
Created attachment 625024 [details]
Created attachment 625025 [details]
Created attachment 625027 [details]
Created attachment 625029 [details]
Created attachment 625032 [details]
Created attachment 625034 [details]
Created attachment 625037 [details]
Thanks for the bug report.
I'd ignore this backtrace for now, as we know about some problems with the version 2 of zeromq, but we hope to have it sorted out today with upgrading to the version 3 of it.
(But there is currently a pending review request about it in bug #864937)
Any updates on this? Can it be closed?
As python-zmq now uses zeromq3, this bug shouldn't be able to be reproduced anymore.
If there is another way to reproduce this directly with the C library this can be reopened again.
Closing as deferred until then...