systemd-journald crashed with SIGABRT in journal_file_rotate_suggested()

[Daniel Lynton]

System was in sleep mode, I logged back in and this system error was waiting for me.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 09:34:50 2017
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Alienware Alienware X51 R3
ProcCmdline: /lib/systemd/systemd-journald
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 journal_file_rotate_suggested () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
 ?? ()
 ?? ()
 ?? ()
SystemdDelta:
 [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf

 2 overridden configuration files found.
Title: systemd-journald crashed with SIGABRT in journal_file_rotate_suggested()
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
UserGroups:

dmi.bios.date: 09/11/2015
dmi.bios.vendor: Alienware
dmi.bios.version: 1.1.0
dmi.board.name: 026CD3
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.modalias: dmi:bvnAlienware:bvr1.1.0:bd09/11/2015:svnAlienware:pnAlienwareX51R3:pvr:rvnAlienware:rn026CD3:rvrA00:cvnAlienware:ct3:cvr:
dmi.product.name: Alienware X51 R3
dmi.sys.vendor: Alienware

[Apport retracing service (apport)]

StacktraceTop:
 journal_file_rotate_suggested (f=0x55dd07aa2190, max_file_usec=2629800000000) at ../src/journal/journal-file.c:3674
 write_to_journal (priority=4, n=25, iovec=0x55dd07aa6de0, uid=1000, s=0x7ffcd6142670) at ../src/journal/journald-server.c:673
 dispatch_message_real (s=0x7ffcd6142670, iovec=0x55dd07aa6de0, n=25, m=76, ucred=<optimized out>, tv=0x7ffcd6142330, label=0x0, label_len=0, unit_id=0x0, priority=4, object_pid=0, cgroup=0x55dd07ab94d0 "/user.slice/user-1000.slice/session-18.scope") at ../src/journal/journald-server.c:1068
 server_dispatch_message (s=<optimized out>, iovec=0x55dd07aa6de0, n=<optimized out>, m=76, ucred=0x7ffcd6142350, tv=0x7ffcd6142330, label=0x0, label_len=0, unit_id=0x0, priority=4, object_pid=0) at ../src/journal/journald-server.c:1188
 server_process_entry (label_len=0, label=0x0, tv=0x7ffcd6142330, ucred=<optimized out>, remaining=<synthetic pointer>, buffer=0x55dd07a47c40, s=0x7ffcd6142670) at ../src/journal/journald-native.c:306

[Sebastien Bacher (seb128)]

the error is
"systemd-journald.service: Watchdog timeout (limit 3min)!"

which seems to match https://github.com/systemd/systemd/issues/1353

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.