Bug 1053292

Summary: [abrt] systemd: link_entry_into_array_plus_one(): systemd-journald killed by SIGBUS
Product: [Fedora] Fedora Reporter: Juan Orti <jorti>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dabbill, hopparz, johannbg, lnykryn, martin, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c295bfec4100aac81d8d1c59c0b774da616f657d
Whiteboard: abrt_hash:89185508ff95f8035adf28dbbf79317dcbc67f5c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-05 02:35:46 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 Juan Orti 2014-01-14 22:58:06 UTC 
Version-Release number of selected component:
systemd-208-9.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: link_entry_into_array_plus_one
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.12.6-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 link_entry_into_array_plus_one at ../src/journal/journal-file.c:1169
 #1 journal_file_link_entry_item at ../src/journal/journal-file.c:1188
 #2 journal_file_link_entry at ../src/journal/journal-file.c:1229
 #3 journal_file_append_entry_internal at ../src/journal/journal-file.c:1272
 #4 journal_file_append_entry at ../src/journal/journal-file.c:1354
 #5 write_to_journal at ../src/journal/journald-server.c:450
 #6 dispatch_message_real at ../src/journal/journald-server.c:776
 #7 server_dispatch_message at ../src/journal/journald-server.c:876
 #8 stdout_stream_log at ../src/journal/journald-stream.c:130
 #9 stdout_stream_line at ../src/journal/journald-stream.c:231
Comment 1 Juan Orti 2014-01-14 22:58:12 UTC 
Created attachment 850283 [details]
File: backtrace
Comment 2 Juan Orti 2014-01-14 22:58:14 UTC 
Created attachment 850284 [details]
File: cgroup
Comment 3 Juan Orti 2014-01-14 22:58:17 UTC 
Created attachment 850285 [details]
File: core_backtrace
Comment 4 Juan Orti 2014-01-14 22:58:19 UTC 
Created attachment 850286 [details]
File: dso_list
Comment 5 Juan Orti 2014-01-14 22:58:21 UTC 
Created attachment 850287 [details]
File: environ
Comment 6 Juan Orti 2014-01-14 22:58:23 UTC 
Created attachment 850288 [details]
File: exploitable
Comment 7 Juan Orti 2014-01-14 22:58:25 UTC 
Created attachment 850289 [details]
File: limits
Comment 8 Juan Orti 2014-01-14 22:58:28 UTC 
Created attachment 850290 [details]
File: maps
Comment 9 Juan Orti 2014-01-14 22:58:30 UTC 
Created attachment 850291 [details]
File: open_fds
Comment 10 Juan Orti 2014-01-14 22:58:32 UTC 
Created attachment 850292 [details]
File: proc_pid_status
Comment 11 Juan Orti 2014-01-14 22:58:34 UTC 
Created attachment 850293 [details]
File: var_log_messages
Comment 12 Zbigniew Jędrzejewski-Szmek 2014-06-18 17:38:55 UTC 
*** Bug 1093966 has been marked as a duplicate of this bug. ***
Comment 13 Zbigniew Jędrzejewski-Szmek 2014-06-18 17:39:14 UTC 
*** Bug 1075980 has been marked as a duplicate of this bug. ***
Comment 14 Martin Dengler 2014-08-24 23:01:08 UTC 
Another user experienced a similar problem:

Not sure if I was trying to restart systemd-journald or just using it.  I suspect the root cause was the btrfs device that the journal was on was full (btrfs root fs & /var device was full: "btrfs fi show" showed the devid's "used" amount the same as the "size" amount).

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: link_entry_into_array_plus_one
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.15.7-200.fc20.x86_64
package:        systemd-208-21.fc20
reason:         systemd-journald killed by SIGBUS
runlevel:       3 5
type:           CCpp
uid:            0
Comment 15 Martin Dengler 2014-08-24 23:12:48 UTC 
Another user experienced a similar problem:

Again, similar circumstances to #1053292 ( https://bugzilla.redhat.com/show_bug.cgi?id=1053292 ):  not sure if I was trying to restart systemd-journald or just using it.  I suspect the root cause was the btrfs device that the journal was on was full (btrfs root fs & /var device was full: "btrfs fi show" showed the devid's "used" amount the same as the "size" amount).

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: link_entry_into_array_plus_one
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.15.7-200.fc20.x86_64
package:        systemd-208-21.fc20
reason:         systemd-journald killed by SIGBUS
runlevel:       3 5
type:           CCpp
uid:            0
Comment 16 Lennart Poettering 2015-01-05 02:35:46 UTC 

*** This bug has been marked as a duplicate of bug 1045810 ***