Bug 1116046

Summary: [abrt] munin: do_clean_named_objs(): perl killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Lacrocivious Acrophosist <altbinspam>
Component: muninAssignee: d. johnson <drjohnson1>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: drjohnson1, ingvar, jvanek
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5a2dc2823a2ffbc8f3b6ad2504e52c6c3119f215
Whiteboard: abrt_hash:f5ac71bc57c410db96041267fb7b1dbf57072204
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-04 02:53:50 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: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Lacrocivious Acrophosist 2014-07-03 14:49:21 UTC 
Version-Release number of selected component:
munin-2.0.19-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/perl /usr/share/munin/munin-update
crash_function: do_clean_named_objs
executable:     /usr/bin/perl
kernel:         3.13.7-200.fc20.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            991

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 do_clean_named_objs at sv.c:510
 #1 S_visit at sv.c:422
 #2 Perl_sv_clean_objs at sv.c:581
 #3 perl_destruct at perl.c:766
Comment 1 Lacrocivious Acrophosist 2014-07-03 14:49:25 UTC 
Created attachment 914501 [details]
File: backtrace
Comment 2 Lacrocivious Acrophosist 2014-07-03 14:49:27 UTC 
Created attachment 914502 [details]
File: cgroup
Comment 3 Lacrocivious Acrophosist 2014-07-03 14:49:29 UTC 
Created attachment 914503 [details]
File: core_backtrace
Comment 4 Lacrocivious Acrophosist 2014-07-03 14:49:31 UTC 
Created attachment 914504 [details]
File: dso_list
Comment 5 Lacrocivious Acrophosist 2014-07-03 14:49:32 UTC 
Created attachment 914505 [details]
File: environ
Comment 6 Lacrocivious Acrophosist 2014-07-03 14:49:34 UTC 
Created attachment 914506 [details]
File: exploitable
Comment 7 Lacrocivious Acrophosist 2014-07-03 14:49:36 UTC 
Created attachment 914507 [details]
File: limits
Comment 8 Lacrocivious Acrophosist 2014-07-03 14:49:38 UTC 
Created attachment 914508 [details]
File: maps
Comment 9 Lacrocivious Acrophosist 2014-07-03 14:49:40 UTC 
Created attachment 914509 [details]
File: open_fds
Comment 10 Lacrocivious Acrophosist 2014-07-03 14:49:41 UTC 
Created attachment 914510 [details]
File: proc_pid_status
Comment 11 Lacrocivious Acrophosist 2014-07-03 14:49:42 UTC 
Created attachment 914511 [details]
File: var_log_messages
Comment 12 Lacrocivious Acrophosist 2014-07-03 19:07:58 UTC 
Immediately after filing this bug, abrt alerted me to another one ( bug 1116045 ), and as soon as I reported that one, another popped up for packagekit. At that point I realized the operating instance was borked and did a hardware power cycle on the system.

The system is older hardware, and pukes forth abrt alerts way too often. See comments in bug 1116045.

Therefore I recommend that this ticket be deleted, as it comes from an abrt alert running on a known flaky system, and the abrts may be artifacts of aging hardware beginning to die by degrees.

If this happens again -- on other running systems -- I will report it again. For now, I suggest not wasting anyone's time on this one.

Thank you.
Comment 13 d. johnson 2014-07-04 02:53:50 UTC 
Thank you, closing.  Please re-open if this problem occurs again.