Bug 1151848

Summary: [abrt] systemd: journal_file_object_verify(): journalctl killed by SIGBUS
Product: [Fedora] Fedora Reporter: Tomasz Torcz <tomek>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1a1b7ae6c61878d9f48bd8e7de1f0d0b619ad17d
Whiteboard: abrt_hash:5f50f13fa8b4cf53f8efbeaad3535ca77d1fa51f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-05 00:39:17 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 Tomasz Torcz 2014-10-12 15:02:56 UTC 
Version-Release number of selected component:
systemd-216-3.fc21

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        journalctl --verify
crash_function: journal_file_object_verify
executable:     /usr/bin/journalctl
kernel:         3.17.0-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 journal_file_object_verify at ../src/journal/journal-verify.c:312
 #1 journal_file_verify at ../src/journal/journal-verify.c:885
 #2 verify.lto_priv.183 at ../src/journal/journalctl.c:1500
Comment 1 Tomasz Torcz 2014-10-12 15:02:59 UTC 
Created attachment 946109 [details]
File: backtrace
Comment 2 Tomasz Torcz 2014-10-12 15:03:01 UTC 
Created attachment 946110 [details]
File: cgroup
Comment 3 Tomasz Torcz 2014-10-12 15:03:02 UTC 
Created attachment 946111 [details]
File: core_backtrace
Comment 4 Tomasz Torcz 2014-10-12 15:03:03 UTC 
Created attachment 946112 [details]
File: dso_list
Comment 5 Tomasz Torcz 2014-10-12 15:03:04 UTC 
Created attachment 946113 [details]
File: environ
Comment 6 Tomasz Torcz 2014-10-12 15:03:06 UTC 
Created attachment 946114 [details]
File: exploitable
Comment 7 Tomasz Torcz 2014-10-12 15:03:07 UTC 
Created attachment 946115 [details]
File: limits
Comment 8 Tomasz Torcz 2014-10-12 15:03:09 UTC 
Created attachment 946116 [details]
File: maps
Comment 9 Tomasz Torcz 2014-10-12 15:03:10 UTC 
Created attachment 946117 [details]
File: open_fds
Comment 10 Tomasz Torcz 2014-10-12 15:03:11 UTC 
Created attachment 946118 [details]
File: proc_pid_status
Comment 11 Tomasz Torcz 2014-10-12 15:03:12 UTC 
Created attachment 946119 [details]
File: var_log_messages
Comment 12 Zbigniew Jędrzejewski-Szmek 2014-10-13 00:13:50 UTC 
This seems nicely repeatable. Any chance you could upload the journal directory somewhere (can be privately)?
Comment 13 Tomasz Torcz 2014-10-13 16:51:06 UTC 
I've found problematic journal file. Suprise:

 cp: error reading ‘/var/log/journal/bd2f536c5eec7709c68df1884a3434ff/system~’: Input/output error

Even though there are no I/O errors in dmesg. I have to take this particular to btrfs guys.

On the other hand: journal reading should be more robust. One broken file makes system logs inaccessible; also each "systemctl status" ended with SIGBUS.
Comment 14 Lennart Poettering 2014-12-09 02:27:16 UTC 
*** Bug 1151847 has been marked as a duplicate of this bug. ***
Comment 15 Lennart Poettering 2014-12-09 02:27:27 UTC 
*** Bug 1151776 has been marked as a duplicate of this bug. ***
Comment 16 Lennart Poettering 2015-01-05 00:39:17 UTC 

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