# rpm -q systemd systemd-233-2.fc27.x86_64 [root@domek coredump]# gdb -c core.systemd-journal.0.ea146e8b63e04fef91a39bbc2b9efdc3.496.1491082613000000 GNU gdb (GDB) Fedora 7.12.50.20170309-5.fc27 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". [New LWP 496] warning: core file may not match specified executable file. Reading symbols from /usr/lib/systemd/systemd-journald...Reading symbols from /usr/lib/debug/usr/lib/systemd/systemd-journald.debug...done. done. warning: Ignoring non-absolute filename: <linux-vdso.so.1> Missing separate debuginfo for linux-vdso.so.1 Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/fd/ccb3de647b4b98668a97afd4cbbee2964d45d6 warning: .dynamic section for "/usr/lib64/libsystemd.so.0.18.0" is not at the expected address (wrong library or version mismatch?) [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib/systemd/systemd-journald'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f06a2c710d1 in journal_file_append_data (f=f@entry=0x55f36908fff0, data=<optimized out>, size=<optimized out>, ret=ret@entry=0x7fff826a38d0, offset=offset@entry=0x7fff826a38d8) at src/journal/journal-file.c:1443 1443 o->data.next_field_offset = fo->field.head_data_offset; (gdb) bt #0 0x00007f06a2c710d1 in journal_file_append_data (f=f@entry=0x55f36908fff0, data=<optimized out>, size=<optimized out>, ret=ret@entry=0x7fff826a38d0, offset=offset@entry=0x7fff826a38d8) at src/journal/journal-file.c:1443 #1 0x00007f06a2c719a1 in journal_file_append_entry (f=0x55f36908fff0, ts=0x7fff826a3b80, iovec=<optimized out>, n_iovec=21, seqnum=0x7fff826a4a10, ret=0x0, offset=0x0) at src/journal/journal-file.c:1831 #2 0x000055f367994efa in write_to_journal (priority=86, n=21, iovec=0x7fff826a40b0, uid=0, s=0x7fff826a4960) at src/journal/journald-server.c:691 #3 dispatch_message_real (s=0x7fff826a4960, iovec=0x7fff826a40b0, n=21, m=<optimized out>, ucred=<optimized out>, tv=0x7fff826a44f0, label=0x0, label_len=0, unit_id=0x0, priority=86, object_pid=0, cgroup=0x55f3690f2f40 "/system.slice/sshd.service") at src/journal/journald-server.c:1068 #4 0x000055f367996968 in server_dispatch_message (s=<optimized out>, iovec=0x7fff826a40b0, n=<optimized out>, m=28, ucred=0x7fff826a4510, tv=0x7fff826a44f0, label=0x0, label_len=0, unit_id=0x0, priority=86, object_pid=0) at src/journal/journald-server.c:1188 #5 0x000055f3679978c0 in server_process_syslog_message (s=0x7fff826a4960, buf=<optimized out>, ucred=0x7fff826a4510, tv=0x7fff826a44f0, label=0x0, label_len=0) at src/journal/journald-syslog.c:379 #6 0x000055f367999e42 in server_process_datagram (es=<optimized out>, fd=3, revents=<optimized out>, userdata=0x7fff826a4960) at src/journal/journald-server.c:1388 #7 0x00007f06a2ce3440 in source_dispatch (s=s@entry=0x55f369085510) at src/libsystemd/sd-event/sd-event.c:2272 #8 0x00007f06a2ce365a in sd_event_dispatch (e=e@entry=0x55f369085170) at src/libsystemd/sd-event/sd-event.c:2631 #9 0x00007f06a2ce4a97 in sd_event_run (e=0x55f369085170, timeout=18446744073709551615) at src/libsystemd/sd-event/sd-event.c:2690 #10 0x000055f36798c299 in main (argc=<optimized out>, argv=<optimized out>) at src/journal/journald.c:107
SIGABRT is probably because of a watchdog timeout. Was the machine under heavy load when this happened?
Yes it was. It was just after login into Gnome session in which autostart I have chrome opening about 40 tabs, evolution, about 8 terminal session + skype + empathy. Seems that this crash caused that whole GUI session failed and gdm was no longer even able to display login screen. From last two or three kernel versions seems some kernel debug options enabled in kernel are slowing my laptop now. Only kernel on which I still can work is 4.10.0-1. Nevertheless as long as still everything is running I don't see why something should receive SIGABRT (?). A bit odd.
There's a watchdog set with a limit of 3 min for systemd-journald. systemd-journald being aborted does (or at least should not) cause an issue for other programs, because systemd will immediately restart journald and hand it the previous set of descriptors. So this should only result in a loss of some messages. You can disable the watchdog, or make it significantly higher: systemctl edit systemd-journald, add [Service] WatchdogSec=30min
I'm sure that in this exact case GUI session crashed after about 1in when in meantime I was able to interact with some applications. OK, will try to change WatchdogSec, PS. can we chat on IRC? I have some issue with tracing some systemd core service on aarm64 HW which seems so far not able to use under Fedora and I'm looking for some help. I'm on freenode.net IRC on #fedora-devel.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Closing