Bug 1057900

Summary: [abrt] snapper: exit(): snapperd killed by SIGABRT
Product: [Fedora] Fedora Reporter: Mathieu Chouquet-Stringer <mathieu-acct>
Component: snapperAssignee: Ondrej Kozina <okozina>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 20CC: agk, dconan12, lvm-team, mcsontos, msnitzer, okozina
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b7898546e6cf373fb3d6d3ba704be9ba49282f40
Whiteboard: abrt_hash:edfb8c77d2cd324aa751186a232295d5b367c36c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:45:43 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: core_backtrace
none
File: dso_list
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Mathieu Chouquet-Stringer 2014-01-25 21:37:11 UTC
Description of problem:
I have enabled snapperd as a yum plugin. Everytime there's an update, it's launched a go through the snapshost to compute differences (to allow you to rollback files and so on), that's when it crashes.

Version-Release number of selected component:
snapper-0.1.7-1.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        snapperd
crash_function: exit
executable:     /usr/sbin/snapperd
kernel:         3.13.0
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (2 frames)
 #19 exit at exit.c:104
 #21 _start

Comment 1 Mathieu Chouquet-Stringer 2014-01-25 21:37:16 UTC
Created attachment 855489 [details]
File: backtrace

Comment 2 Mathieu Chouquet-Stringer 2014-01-25 21:37:17 UTC
Created attachment 855490 [details]
File: cgroup

Comment 3 Mathieu Chouquet-Stringer 2014-01-25 21:37:19 UTC
Created attachment 855491 [details]
File: core_backtrace

Comment 4 Mathieu Chouquet-Stringer 2014-01-25 21:37:21 UTC
Created attachment 855492 [details]
File: dso_list

Comment 5 Mathieu Chouquet-Stringer 2014-01-25 21:37:23 UTC
Created attachment 855493 [details]
File: limits

Comment 6 Mathieu Chouquet-Stringer 2014-01-25 21:37:25 UTC
Created attachment 855494 [details]
File: maps

Comment 7 Mathieu Chouquet-Stringer 2014-01-25 21:37:27 UTC
Created attachment 855495 [details]
File: open_fds

Comment 8 Mathieu Chouquet-Stringer 2014-01-25 21:37:29 UTC
Created attachment 855496 [details]
File: proc_pid_status

Comment 9 dconan12 2014-07-02 00:59:41 UTC
Another user experienced a similar problem:

I did a 
root: snapper create --command "yum install epiphany" --description "epiphany"
to create a pre and post snapshot for running "yum install epiphany". 5 minutes after snapper crashed. However, I did a few snapper create --command "yum install softwarehere" --description "description here" and it did not crash after while. Do note however that the snapshots are working.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/sbin/snapperd
crash_function: exit
executable:     /usr/sbin/snapperd
kernel:         3.14.9-200.fc20.x86_64
package:        snapper-0.1.7-1.fc20
reason:         snapperd killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 10 Fedora End Of Life 2015-05-29 10:40:44 UTC
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.

Comment 11 Fedora End Of Life 2015-06-29 14:45:43 UTC
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.