Bug 890463

Summary: [abrt] systemd-195-10.fc18: journal_file_rotate_suggested: Process /usr/lib/systemd/systemd-journald was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: sheepdestroyer <sheepdestroyer>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dcleal, jlneill, johannbg, lnykryn, metherid, msekleta, notting, plautrba, sergio, systemd-maint, vpavlin, zbyszek
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b4fa0613a4f19f9486a983f4c8009b5b3723c688
Fixed In Version: systemd-201-2.fc18.9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-10 07:37: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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages none

Description sheepdestroyer 2012-12-27 05:31:16 UTC 
Version-Release number of selected component:
systemd-195-10.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: journal_file_rotate_suggested
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.7.1
remote_result:  NOTFOUND
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 journal_file_rotate_suggested at src/journal/journal-file.c:2723
 #1 write_to_journal at src/journal/journald-server.c:481
 #2 dispatch_message_real at src/journal/journald-server.c:678
 #3 server_dispatch_message at src/journal/journald-server.c:795
 #4 server_process_syslog_message at src/journal/journald-syslog.c:403
 #5 process_event at src/journal/journald-server.c:1151
Comment 1 sheepdestroyer 2012-12-27 05:31:21 UTC 
Created attachment 669506 [details]
File: backtrace
Comment 2 sheepdestroyer 2012-12-27 05:31:28 UTC 
Created attachment 669507 [details]
File: cgroup
Comment 3 sheepdestroyer 2012-12-27 05:31:31 UTC 
Created attachment 669508 [details]
File: core_backtrace
Comment 4 sheepdestroyer 2012-12-27 05:31:33 UTC 
Created attachment 669509 [details]
File: dso_list
Comment 5 sheepdestroyer 2012-12-27 05:31:35 UTC 
Created attachment 669510 [details]
File: environ
Comment 6 sheepdestroyer 2012-12-27 05:31:36 UTC 
Created attachment 669511 [details]
File: limits
Comment 7 sheepdestroyer 2012-12-27 05:31:39 UTC 
Created attachment 669512 [details]
File: maps
Comment 8 sheepdestroyer 2012-12-27 05:31:41 UTC 
Created attachment 669513 [details]
File: open_fds
Comment 9 sheepdestroyer 2012-12-27 05:31:43 UTC 
Created attachment 669514 [details]
File: proc_pid_status
Comment 10 sheepdestroyer 2012-12-27 05:31:45 UTC 
Created attachment 669515 [details]
File: smolt_data
Comment 11 sheepdestroyer 2012-12-27 05:31:47 UTC 
Created attachment 669516 [details]
File: var_log_messages
Comment 12 Dominic Cleal 2013-04-27 11:39:45 UTC 
Seemed to be during an upgrade of selinux-policy-targeted and about the time the policy was reloaded in memory:

[.. many other updates ..]
Apr 21 19:05:58 iridium yum[5046]: Updated: policycoreutils-sandbox-2.1.13-59.fc18.x86_64
Apr 21 19:06:17 iridium dbus[2789]: avc:  received policyload notice (seqno=2)
Apr 21 19:06:17 iridium kernel: [ 2723.921001] systemd-journal[470]: segfault at 7f2bff587058 ip 00007f2c097aa5c5 sp 00007fffdee233f0 error 4 in systemd-journald (deleted)[7f2c0978d000+2c000]
Apr 21 19:06:19 iridium dbus[2607]: avc:  received policyload notice (seqno=2)
Apr 21 19:06:19 iridium dbus[1860]: avc:  received policyload notice (seqno=2)
Apr 21 19:06:19 iridium dbus[1860]: [system] Reloaded configuration
Apr 21 19:06:19 iridium abrt[17536]: File '/usr/lib/systemd/systemd-journald' seems to be deleted
Apr 21 19:06:19 iridium abrt[17536]: Saved core dump of pid 470 (/usr/lib/systemd/systemd-journald) to /var/tmp/abrt/ccpp-2013-04-21-19:06:17-470 (1277952 bytes)
Apr 21 19:06:19 iridium abrtd: Directory 'ccpp-2013-04-21-19:06:17-470' creation detected
Apr 21 19:06:19 iridium abrtd: Generating backtrace
Apr 21 19:06:19 iridium systemd[1]: systemd-journald.service: main process exited, code=dumped, status=11/SEGV
Apr 21 19:06:19 iridium systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1
Apr 21 19:06:19 iridium systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Apr 21 19:06:21 iridium abrtd: Backtrace is generated, 1379 bytes
Apr 21 19:06:21 iridium abrtd: Core backtrace is generated and saved, 55 bytes
Apr 21 19:06:21 iridium abrtd: New problem directory /var/tmp/abrt/ccpp-2013-04-21-19:06:17-470, processing
Apr 21 19:07:22 iridium yum[5046]: Updated: selinux-policy-targeted-3.11.1-91.fc18.noarch
[.. updates continue ..]

backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
core_backtrace: 734719c799d83a396dfd762bb71110645064f59d 0x1d5c5 - - -
crash_function: journal_file_rotate_suggested
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.7.9-201.fc18.x86_64
package:        systemd-197-1.fc18.2
reason:         Process /usr/lib/systemd/systemd-journald was killed by signal 11 (SIGSEGV)
uid:            0
ureports_counter: 1
Comment 13 Zbigniew Jędrzejewski-Szmek 2013-10-10 02:40:40 UTC 
Fixed upstream in http://cgit.freedesktop.org/systemd/systemd/commit/?id=2b98f75.
Comment 14 Zbigniew Jędrzejewski-Szmek 2013-10-10 03:10:03 UTC 
*** Bug 957543 has been marked as a duplicate of this bug. ***
Comment 15 Zbigniew Jędrzejewski-Szmek 2013-10-11 03:14:20 UTC 
*** Bug 984242 has been marked as a duplicate of this bug. ***
Comment 16 Fedora Update System 2013-10-22 16:10:11 UTC 
systemd-208-4.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/systemd-208-4.fc20
Comment 17 Fedora Update System 2013-10-22 16:20:44 UTC 
systemd-204-17.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/systemd-204-17.fc19
Comment 18 Fedora Update System 2013-10-22 18:51:03 UTC 
Package systemd-208-4.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-208-4.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-19680/systemd-208-4.fc20
then log in and leave karma (feedback).
Comment 19 Fedora Update System 2013-10-25 01:52:37 UTC 
systemd-204-17.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 20 Fedora Update System 2013-10-29 16:05:07 UTC 
systemd-201-2.fc18.9 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/systemd-201-2.fc18.9
Comment 21 Fedora Update System 2013-10-30 01:52:51 UTC 
Package systemd-201-2.fc18.9:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.9'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20267/systemd-201-2.fc18.9
then log in and leave karma (feedback).
Comment 22 Fedora Update System 2013-11-10 07:37:17 UTC 
systemd-208-4.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 23 Fedora Update System 2013-11-13 02:24:28 UTC 
systemd-201-2.fc18.9 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.