Bug 905302

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: 项纪汉 <xiangjihan>
Component: zeromqAssignee: Thomas Spura <tomspur>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: andrewniemants, bkabrda, dmalcolm, ivazqueznet, jonathansteffan, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:5ed24cc7e7889fde3f57708de970af29e4d8ba45
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 18:38:42 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: backtrace
none
File: cgroup
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description 项纪汉 2013-01-29 05:56:35 UTC 
Version-Release number of selected component:
python-2.7.3-13.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/fedmsg-notify-daemon
core_backtrace: 
crash_function: zmq::zmq_abort
executable:     /usr/bin/python2.7
kernel:         3.7.2-204.fc18.i686.PAE
remote_result:  NOTFOUND
uid:            1000
var_log_messages: Jan 25 23:20:33 localhost abrt[7687]: Saved core dump of pid 1751 (/usr/bin/python2.7) to /var/spool/abrt/ccpp-2013-01-25-23:20:29-1751 (107003904 bytes)

Truncated backtrace:
Thread no. 1 (7 frames)
 #3 zmq::zmq_abort at err.cpp:76
 #4 zmq::tcp_connecter_t::connect at tcp_connecter.cpp:285
 #5 zmq::tcp_connecter_t::out_event at tcp_connecter.cpp:115
 #6 zmq::tcp_connecter_t::in_event at tcp_connecter.cpp:110
 #7 zmq::epoll_t::loop at epoll.cpp:154
 #8 thread_routine at thread.cpp:83
 #9 ??
Comment 1 项纪汉 2013-01-29 05:56:41 UTC 
Created attachment 689575 [details]
File: backtrace
Comment 2 项纪汉 2013-01-29 05:56:43 UTC 
Created attachment 689576 [details]
File: cgroup
Comment 3 项纪汉 2013-01-29 05:56:48 UTC 
Created attachment 689577 [details]
File: dso_list
Comment 4 项纪汉 2013-01-29 05:56:50 UTC 
Created attachment 689578 [details]
File: environ
Comment 5 项纪汉 2013-01-29 05:56:53 UTC 
Created attachment 689579 [details]
File: limits
Comment 6 项纪汉 2013-01-29 05:57:02 UTC 
Created attachment 689580 [details]
File: maps
Comment 7 项纪汉 2013-01-29 05:57:04 UTC 
Created attachment 689581 [details]
File: open_fds
Comment 8 项纪汉 2013-01-29 05:57:07 UTC 
Created attachment 689582 [details]
File: proc_pid_status
Comment 9 Thomas Spura 2013-01-29 12:36:07 UTC 
Thanks for the bug report.

Unfortunately, I don't know how to properly run into this bug.
How is this reproducible?
Comment 10 Fedora End Of Life 2013-12-21 10:57:14 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.
Comment 11 Fedora End Of Life 2014-02-05 18:38:42 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.