Bug 1190176

Summary: [abrt] systemd: __fsync_nocancel(): systemd-journald killed by SIGABRT
Product: [Fedora] Fedora Reporter: Michal Nowak <mnowak>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bugzilla, johannbg, jsynacek, lnykryn, msekleta, smocktaylor, s, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e03ea2d085a76b320e0f8135e21c82b5871d2d84
Whiteboard: abrt_hash:51c1d6658d7a7b318e83b9091af02dc5ade9017a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-20 14:01:46 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: var_log_messages
none
journalctl -b
none
Journald log from 06 Feb 2015 none

Description Michal Nowak 2015-02-06 14:57:07 UTC 
Version-Release number of selected component:
systemd-218-3.fc22

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: __fsync_nocancel
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.19.0-0.rc7.git0.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __fsync_nocancel at ../sysdeps/unix/syscall-template.S:81
 #1 journal_file_set_online.lto_priv.200 at ../src/journal/journal-file.c:89
 #2 journal_file_append_object at ../src/journal/journal-file.c:531
 #3 journal_file_append_data.lto_priv.146 at ../src/journal/journal-file.c:1007
 #4 journal_file_append_entry.constprop.105 at ../src/journal/journal-file.c:1374
 #5 write_to_journal at ../src/journal/journald-server.c:506
 #6 dispatch_message_real.lto_priv.232 at ../src/journal/journald-server.c:823
 #7 server_dispatch_message at ../src/journal/journald-server.c:923
 #8 server_process_syslog_message at ../src/journal/journald-syslog.c:415
 #9 process_datagram at ../src/journal/journald-server.c:1211
Comment 1 Michal Nowak 2015-02-06 14:57:10 UTC 
Created attachment 988900 [details]
File: backtrace
Comment 2 Michal Nowak 2015-02-06 14:57:11 UTC 
Created attachment 988901 [details]
File: cgroup
Comment 3 Michal Nowak 2015-02-06 14:57:13 UTC 
Created attachment 988902 [details]
File: core_backtrace
Comment 4 Michal Nowak 2015-02-06 14:57:14 UTC 
Created attachment 988903 [details]
File: dso_list
Comment 5 Michal Nowak 2015-02-06 14:57:15 UTC 
Created attachment 988904 [details]
File: environ
Comment 6 Michal Nowak 2015-02-06 14:57:16 UTC 
Created attachment 988905 [details]
File: limits
Comment 7 Michal Nowak 2015-02-06 14:57:18 UTC 
Created attachment 988906 [details]
File: maps
Comment 8 Michal Nowak 2015-02-06 14:57:19 UTC 
Created attachment 988907 [details]
File: open_fds
Comment 9 Michal Nowak 2015-02-06 14:57:20 UTC 
Created attachment 988908 [details]
File: proc_pid_status
Comment 10 Michal Nowak 2015-02-06 14:57:21 UTC 
Created attachment 988909 [details]
File: var_log_messages
Comment 11 Zbigniew Jędrzejewski-Szmek 2015-02-06 22:36:29 UTC 
Can you attach the full logs for the boot ('journalctl -b')? fsync() should not result in sigabrt afaics.
Comment 12 Michal Nowak 2015-02-07 08:52:55 UTC 
Created attachment 989138 [details]
journalctl -b
Comment 13 Zbigniew Jędrzejewski-Szmek 2015-02-07 14:58:03 UTC 
Hm, this is for the current boot... I'd need the one for the boot where the crash occurred. You can get a list with 'journalctl --list-boots', find the one for 06/02, and than extract it with 'journalctl -b-8' or whatever.
Comment 14 Michal Nowak 2015-02-09 07:50:27 UTC 
Created attachment 989552 [details]
Journald log from 06 Feb 2015
Comment 15 Zbigniew Jędrzejewski-Szmek 2015-02-09 14:30:58 UTC 
I don't think this can be it either: the log runs all the way to "Journal stopped" without any sign of the crash in systemd. There's a problem with the journal though:

Feb 06 15:53:25 localhost.localdomain systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!

but no additional information. It is possible that some messages were lost.
Comment 16 Jaroslav Reznik 2015-03-03 16:50:43 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 17 Zbigniew Jędrzejewski-Szmek 2015-03-14 15:59:36 UTC 
*** Bug 1188857 has been marked as a duplicate of this bug. ***
Comment 18 Zbigniew Jędrzejewski-Szmek 2015-03-14 15:59:46 UTC 
*** Bug 1162266 has been marked as a duplicate of this bug. ***
Comment 19 Jan Synacek 2016-01-20 14:01:46 UTC 

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