Bug 1312995

Summary: [abrt] dnf: __env_size_insert(): python3.4 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Craig Robson <craig>
Component: libdbAssignee: Matej Mužila <mmuzila>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: craig, hhorak, jorton, jplesnik, jsilhan, jstanek, jsynacek, jzeleny, mdomonko, mluscon, novyjindrich, packaging-team-maint, paul, pknirsch, pnemade, ppisar, psabata, steve, vmukhame
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dd43eeccb990dc1e7fd3ecfd94e37a9c8028e5ae
Whiteboard: abrt_hash:b49be0496ed108eea8bb70c9f5ac4cb7f989ab98;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 19:07:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: _var_log_dnf.log
File: backtrace
File: cgroup
File: core_backtrace
File: dso_list
File: environ
File: exploitable
File: limits
File: maps
File: mountinfo
File: namespaces
File: open_fds
File: proc_pid_status none

Description Craig Robson 2016-02-29 17:16:34 UTC
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/python3 /bin/dnf upgrade
crash_function: __env_size_insert
dnf-makecache.log: Error was encountered while opening journal files: No data available
executable:     /usr/bin/python3.4
global_pid:     13765
kernel:         4.3.5-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __env_size_insert at ../../src/env/env_alloc.c:599
 #1 __memp_mf_discard at ../../src/mp/mp_fopen.c:1137
 #2 __memp_fclose at ../../src/mp/mp_fopen.c:1034
 #3 __db_refresh at ../../src/db/db.c:1028
 #4 __db_close at ../../src/db/db.c:747
 #5 __db_close_pp at ../../src/db/db_iface.c:261
 #6 db3_dbiClose at backend/db3.c:735
 #7 dbiForeach at rpmdb.c:441
 #8 rpmdbClose at rpmdb.c:468
 #9 rpmtsCloseDB at rpmts.c:78

Comment 1 Craig Robson 2016-02-29 17:16:39 UTC
Created attachment 1131645 [details]
File: _var_log_dnf.log

Comment 2 Craig Robson 2016-02-29 17:16:40 UTC
Created attachment 1131646 [details]
File: backtrace

Comment 3 Craig Robson 2016-02-29 17:16:41 UTC
Created attachment 1131647 [details]
File: cgroup

Comment 4 Craig Robson 2016-02-29 17:16:42 UTC
Created attachment 1131648 [details]
File: core_backtrace

Comment 5 Craig Robson 2016-02-29 17:16:43 UTC
Created attachment 1131649 [details]
File: dso_list

Comment 6 Craig Robson 2016-02-29 17:16:43 UTC
Created attachment 1131650 [details]
File: environ

Comment 7 Craig Robson 2016-02-29 17:16:44 UTC
Created attachment 1131651 [details]
File: exploitable

Comment 8 Craig Robson 2016-02-29 17:16:45 UTC
Created attachment 1131652 [details]
File: limits

Comment 9 Craig Robson 2016-02-29 17:16:46 UTC
Created attachment 1131653 [details]
File: maps

Comment 10 Craig Robson 2016-02-29 17:16:46 UTC
Created attachment 1131654 [details]
File: mountinfo

Comment 11 Craig Robson 2016-02-29 17:16:47 UTC
Created attachment 1131655 [details]
File: namespaces

Comment 12 Craig Robson 2016-02-29 17:16:48 UTC
Created attachment 1131656 [details]
File: open_fds

Comment 13 Craig Robson 2016-02-29 17:16:49 UTC
Created attachment 1131657 [details]
File: proc_pid_status

Comment 14 Michal Domonkos 2016-03-07 14:04:48 UTC
Hi Craig,

Can you still reproduce this issue, or was it just a random crash that never happened again?

Thank you

Comment 15 Craig Robson 2016-03-07 17:23:07 UTC
I think this only happened once.

Comment 16 Michal Domonkos 2016-03-09 14:48:29 UTC
We don't know the exact reason for this crash but it happens in the berkleydb so moving it over.

Comment 17 Petr Pisar 2016-03-09 15:55:42 UTC
In BerkleyDB, not in the Perl binding. Moving there.

Comment 18 Fedora End Of Life 2016-11-24 15:50:49 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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.

Comment 19 Fedora End Of Life 2016-12-20 19:07:55 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

Thank you for reporting this bug and we are sorry it could not be fixed.