Bug 1199442

Summary: [abrt] systemd: journal_file_link_data(): systemd-journald killed by SIGBUS
Product: [Fedora] Fedora Reporter: wincc
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 22CC: acc-bugz-redhat, dwmw2, faizanqazi, johannbg, jsynacek, lnykryn, mikhail.v.gavrilov, msekleta, nalimilan, s, systemd-maint, tr-rh, zbyszek
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/739a81f8b4a894906534100721ed24a98de336b9
Whiteboard: abrt_hash:77e4c558dab7a30e73a1c29cc8f92f79c188b019
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-20 14:06:02 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 wincc 2015-03-06 10:06:40 UTC
Version-Release number of selected component:
systemd-208-30.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: journal_file_link_data
executable:     /usr/lib/systemd/systemd-journald
kernel:         4.0.0-0.rc2.git0.1.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 journal_file_link_data at ../src/journal/journal-file.c:732
 #1 journal_file_append_data at ../src/journal/journal-file.c:1025
 #2 journal_file_append_entry at ../src/journal/journal-file.c:1366
 #3 write_to_journal at ../src/journal/journald-server.c:464
 #4 dispatch_message_real at ../src/journal/journald-server.c:793
 #5 server_dispatch_message at ../src/journal/journald-server.c:893
 #6 server_process_native_message at ../src/journal/journald-native.c:269
 #7 process_event at ../src/journal/journald-server.c:1272

Comment 1 wincc 2015-03-06 10:06:44 UTC
Created attachment 998750 [details]
File: backtrace

Comment 2 wincc 2015-03-06 10:06:46 UTC
Created attachment 998751 [details]
File: cgroup

Comment 3 wincc 2015-03-06 10:06:47 UTC
Created attachment 998752 [details]
File: core_backtrace

Comment 4 wincc 2015-03-06 10:06:48 UTC
Created attachment 998753 [details]
File: dso_list

Comment 5 wincc 2015-03-06 10:06:50 UTC
Created attachment 998754 [details]
File: environ

Comment 6 wincc 2015-03-06 10:06:51 UTC
Created attachment 998755 [details]
File: exploitable

Comment 7 wincc 2015-03-06 10:06:52 UTC
Created attachment 998756 [details]
File: limits

Comment 8 wincc 2015-03-06 10:06:54 UTC
Created attachment 998757 [details]
File: maps

Comment 9 wincc 2015-03-06 10:06:55 UTC
Created attachment 998758 [details]
File: open_fds

Comment 10 wincc 2015-03-06 10:06:57 UTC
Created attachment 998759 [details]
File: proc_pid_status

Comment 11 wincc 2015-03-06 10:06:58 UTC
Created attachment 998760 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 13:43:42 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2015-06-30 00:13:08 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 14 Milan Bouchet-Valat 2015-08-24 09:38:47 UTC
*** Bug 1204155 has been marked as a duplicate of this bug. ***

Comment 15 Milan Bouchet-Valat 2015-08-24 09:38:48 UTC
*** Bug 1225256 has been marked as a duplicate of this bug. ***

Comment 16 Milan Bouchet-Valat 2015-08-24 09:38:51 UTC
*** Bug 1192085 has been marked as a duplicate of this bug. ***

Comment 17 Milan Bouchet-Valat 2015-08-24 09:49:58 UTC
I've just seen this on F22 with systemd-219-21, and indeed there are three more recent reports with the same backtrace. I've filed a bug upstream at https://github.com/systemd/systemd/issues/1015

Comment 18 Milan Bouchet-Valat 2015-08-24 14:01:09 UTC
Upstream said it would likely be fixed in systemd 223 or higher (which is in Rawhide currently).

Comment 19 Milan Bouchet-Valat 2015-09-04 07:25:42 UTC
Another user experienced a similar problem:

I see this crash quite often, and it apparently prompts my GNOME session to exit.

reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: journal_file_link_data
executable:     /usr/lib/systemd/systemd-journald
global_pid:     425
kernel:         4.0.7-300.fc22.x86_64
package:        systemd-219-21.fc22
reason:         systemd-journald killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 20 Milan Bouchet-Valat 2015-09-04 07:27:42 UTC
Any chance systemd will be updated to version 223 in Fedora 22?

Comment 21 Milan Bouchet-Valat 2016-01-10 21:59:28 UTC
I've just seen this crash again on F23. Would it be possible to update to systemd 223, or to backport journal-related patches mentioned at https://github.com/systemd/systemd/issues/1015?

Comment 22 Milan Bouchet-Valat 2016-01-10 22:01:03 UTC
Ah, sorry, I confused with bug 1297229.

Comment 23 Jan Synacek 2016-01-20 14:06:02 UTC

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