Bug 865040

Summary: [abrt] python-2.7.3-13.fc18: zmq::zmq_abort: Process /usr/bin/python2.7 was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Elad Alfassa <elad>
Component: zeromqAssignee: Thomas Spura <tomspur>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bkabrda, dmalcolm, ivazqueznet, jonathansteffan, lmacken, rbean, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:54b717f6bef5bf57028f290dd9b82794545e3b88
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-20 21:27:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: xsession_errors
none
File: maps
none
File: dso_list
none
File: build_ids
none
File: open_fds
none
File: proc_pid_status none

Description Elad Alfassa 2012-10-10 17:00:12 UTC 
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:
python-2.7.3-13.fc18

Additional info:
libreport version: 2.0.15
abrt_version:   2.0.14
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/fedmsg-notify-daemon
crash_function: zmq::zmq_abort
kernel:         3.6.0-3.fc18.x86_64

truncated backtrace:
: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
Comment 1 Elad Alfassa 2012-10-10 17:00:23 UTC 
Created attachment 625020 [details]
File: core_backtrace
Comment 2 Elad Alfassa 2012-10-10 17:01:07 UTC 
Created attachment 625021 [details]
File: environ
Comment 3 Elad Alfassa 2012-10-10 17:01:17 UTC 
Created attachment 625022 [details]
File: backtrace
Comment 4 Elad Alfassa 2012-10-10 17:01:25 UTC 
Created attachment 625023 [details]
File: limits
Comment 5 Elad Alfassa 2012-10-10 17:01:42 UTC 
Created attachment 625024 [details]
File: cgroup
Comment 6 Elad Alfassa 2012-10-10 17:01:50 UTC 
Created attachment 625025 [details]
File: xsession_errors
Comment 7 Elad Alfassa 2012-10-10 17:02:01 UTC 
Created attachment 625027 [details]
File: maps
Comment 8 Elad Alfassa 2012-10-10 17:02:09 UTC 
Created attachment 625029 [details]
File: dso_list
Comment 9 Elad Alfassa 2012-10-10 17:02:16 UTC 
Created attachment 625032 [details]
File: build_ids
Comment 10 Elad Alfassa 2012-10-10 17:02:23 UTC 
Created attachment 625034 [details]
File: open_fds
Comment 11 Elad Alfassa 2012-10-10 17:02:27 UTC 
Created attachment 625037 [details]
File: proc_pid_status
Comment 12 Thomas Spura 2012-10-10 17:20:28 UTC 
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)
Comment 13 Ralph Bean 2013-02-20 17:45:31 UTC 
Any updates on this?  Can it be closed?
Comment 14 Thomas Spura 2013-02-20 21:27:34 UTC 
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...