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
Created attachment 914501 [details] File: backtrace
Created attachment 914502 [details] File: cgroup
Created attachment 914503 [details] File: core_backtrace
Created attachment 914504 [details] File: dso_list
Created attachment 914505 [details] File: environ
Created attachment 914506 [details] File: exploitable
Created attachment 914507 [details] File: limits
Created attachment 914508 [details] File: maps
Created attachment 914509 [details] File: open_fds
Created attachment 914510 [details] File: proc_pid_status
Created attachment 914511 [details] File: var_log_messages
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.
Thank you, closing. Please re-open if this problem occurs again.