Bug 1003222

Summary: [abrt] systemd-204-9.fc19: journal_file_append_data: Process /usr/lib/systemd/systemd-journald was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: dontbother
Component: systemdAssignee: systemd-maint
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dontbother, johannbg, lnykryn, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7fed89ab5ee1c78a02ddbe30b009d93ad82946c8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-11 02:51:22 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 dontbother 2013-09-01 01:26:04 UTC 
Version-Release number of selected component:
systemd-204-9.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: journal_file_append_data
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.10.5-201.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 journal_file_append_data
 #1 journal_file_append_entry
 #2 dispatch_message_real
 #3 server_dispatch_message
 #4 server_process_syslog_message
 #5 process_event
Comment 1 dontbother 2013-09-01 01:26:09 UTC 
Created attachment 792501 [details]
File: backtrace
Comment 2 dontbother 2013-09-01 01:26:13 UTC 
Created attachment 792502 [details]
File: cgroup
Comment 3 dontbother 2013-09-01 01:26:17 UTC 
Created attachment 792503 [details]
File: core_backtrace
Comment 4 dontbother 2013-09-01 01:26:21 UTC 
Created attachment 792504 [details]
File: dso_list
Comment 5 dontbother 2013-09-01 01:26:25 UTC 
Created attachment 792505 [details]
File: environ
Comment 6 dontbother 2013-09-01 01:26:28 UTC 
Created attachment 792506 [details]
File: exploitable
Comment 7 dontbother 2013-09-01 01:26:32 UTC 
Created attachment 792507 [details]
File: limits
Comment 8 dontbother 2013-09-01 01:26:36 UTC 
Created attachment 792508 [details]
File: maps
Comment 9 dontbother 2013-09-01 01:26:40 UTC 
Created attachment 792509 [details]
File: open_fds
Comment 10 dontbother 2013-09-01 01:26:44 UTC 
Created attachment 792510 [details]
File: proc_pid_status
Comment 11 dontbother 2013-09-01 01:26:49 UTC 
Created attachment 792511 [details]
File: var_log_messages
Comment 12 Zbigniew Jędrzejewski-Szmek 2013-10-11 02:51:22 UTC 
The backtrace is missing, essentially. There's no chance how we're going to guess what's wrong here.