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
Created attachment 988900 [details] File: backtrace
Created attachment 988901 [details] File: cgroup
Created attachment 988902 [details] File: core_backtrace
Created attachment 988903 [details] File: dso_list
Created attachment 988904 [details] File: environ
Created attachment 988905 [details] File: limits
Created attachment 988906 [details] File: maps
Created attachment 988907 [details] File: open_fds
Created attachment 988908 [details] File: proc_pid_status
Created attachment 988909 [details] File: var_log_messages
Can you attach the full logs for the boot ('journalctl -b')? fsync() should not result in sigabrt afaics.
Created attachment 989138 [details] journalctl -b
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.
Created attachment 989552 [details] Journald log from 06 Feb 2015
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.
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
*** Bug 1188857 has been marked as a duplicate of this bug. ***
*** Bug 1162266 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1300212 ***