Bug 1060724

Summary: [abrt] rsyslog: journal_file_move_to_object(): rsyslogd killed by SIGBUS
Product: [Fedora] Fedora Reporter: Josh Cogliati <jrincayc>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: allinux4, a.nesvetov, etay.meiri, james, jlieskov, johannbg, lkundrak, lnykryn, mah.darade, martin, mikhail.v.gavrilov, msekleta, plautrba, samuelmarqueslima1, systemd-maint, theinric, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a5aa592c95390033e6bac2f9879fca97c228914d
Whiteboard: abrt_hash:430205999b83eb32c2d5eda10273b64b83caeb62
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-05 02:36:34 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 Josh Cogliati 2014-02-03 13:06:37 UTC 
Version-Release number of selected component:
rsyslog-7.4.2-2.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /sbin/rsyslogd -n
crash_function: journal_file_move_to_object
executable:     /usr/sbin/rsyslogd
kernel:         3.12.8-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 journal_file_move_to_object at ../src/journal/journal-file.c:439
 #1 generic_array_get at ../src/journal/journal-file.c:1454
 #2 journal_file_next_entry at ../src/journal/journal-file.c:1991
 #3 next_with_matches at ../src/journal/sd-journal.c:814
 #4 next_beyond_location at ../src/journal/sd-journal.c:836
 #5 real_journal_next at ../src/journal/sd-journal.c:895
 #6 sd_journal_next at ../src/journal/sd-journal.c:931
 #7 runInput at imjournal.c:533
 #8 thrdStarter at ../threads.c:212
Comment 1 Josh Cogliati 2014-02-03 13:06:48 UTC 
Created attachment 858554 [details]
File: backtrace
Comment 2 Josh Cogliati 2014-02-03 13:06:50 UTC 
Created attachment 858555 [details]
File: cgroup
Comment 3 Josh Cogliati 2014-02-03 13:06:52 UTC 
Created attachment 858556 [details]
File: core_backtrace
Comment 4 Josh Cogliati 2014-02-03 13:06:53 UTC 
Created attachment 858557 [details]
File: dso_list
Comment 5 Josh Cogliati 2014-02-03 13:06:55 UTC 
Created attachment 858558 [details]
File: environ
Comment 6 Josh Cogliati 2014-02-03 13:06:57 UTC 
Created attachment 858559 [details]
File: exploitable
Comment 7 Josh Cogliati 2014-02-03 13:06:59 UTC 
Created attachment 858560 [details]
File: limits
Comment 8 Josh Cogliati 2014-02-03 13:07:01 UTC 
Created attachment 858561 [details]
File: maps
Comment 9 Josh Cogliati 2014-02-03 13:07:07 UTC 
Created attachment 858562 [details]
File: open_fds
Comment 10 Josh Cogliati 2014-02-03 13:07:09 UTC 
Created attachment 858563 [details]
File: proc_pid_status
Comment 11 Josh Cogliati 2014-02-03 13:07:13 UTC 
Created attachment 858564 [details]
File: var_log_messages
Comment 12 Tomas Heinrich 2014-02-04 10:33:17 UTC 
Given that rsyslog calls a function that takes a single opaque argument [1], I'm inclined to think this is a bug in systemd.

[1] sd_journal_next(sd_journal* j);
Comment 13 Zbigniew Jędrzejewski-Szmek 2014-02-04 13:53:03 UTC 
This range seems to be mapped. Is is possible that the file (/var/log/journal/c83a8a098011452b87b04623eed08648/system~) has been modified at the same time by something else? Alternatively, was the system under memory pressure?
Comment 14 Josh Cogliati 2014-02-05 03:28:35 UTC 
I wasn't fiddling with files in var log (so it would have had to have been a different program if that is the case).  Also, the system has 4GB so it shouldn't have that much memory pressure.
Comment 15 Tomas Heinrich 2014-02-09 13:53:43 UTC 
*** Bug 1062892 has been marked as a duplicate of this bug. ***
Comment 16 Tomas Heinrich 2014-04-18 13:11:20 UTC 
*** Bug 1089103 has been marked as a duplicate of this bug. ***
Comment 17 Tomas Heinrich 2014-06-12 12:56:40 UTC 
*** Bug 1105881 has been marked as a duplicate of this bug. ***
Comment 18 Tomas Heinrich 2014-06-27 12:25:48 UTC 
*** Bug 974331 has been marked as a duplicate of this bug. ***
Comment 19 Lennart Poettering 2015-01-05 02:36:34 UTC 

*** This bug has been marked as a duplicate of bug 1047625 ***
Comment 20 Tomas Heinrich 2015-01-05 15:22:56 UTC 
*** Bug 1177933 has been marked as a duplicate of this bug. ***
Comment 21 Tomas Heinrich 2015-03-04 16:28:47 UTC 
*** Bug 1163636 has been marked as a duplicate of this bug. ***