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
Created attachment 850283 [details] File: backtrace
Created attachment 850284 [details] File: cgroup
Created attachment 850285 [details] File: core_backtrace
Created attachment 850286 [details] File: dso_list
Created attachment 850287 [details] File: environ
Created attachment 850288 [details] File: exploitable
Created attachment 850289 [details] File: limits
Created attachment 850290 [details] File: maps
Created attachment 850291 [details] File: open_fds
Created attachment 850292 [details] File: proc_pid_status
Created attachment 850293 [details] File: var_log_messages
*** Bug 1093966 has been marked as a duplicate of this bug. ***
*** Bug 1075980 has been marked as a duplicate of this bug. ***
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
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
*** This bug has been marked as a duplicate of bug 1045810 ***