systemd-journald crashed with SIGABRT in socket()

Bug #1508263 reported by Logan Rosen on 2015-10-21
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)

Bug Description

Happened after resuming my VM after it was paused due to the host's disk being almost full.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Tue Oct 20 20:12:05 2015
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2014-09-18 (397 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140917)
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdline: /lib/systemd/systemd-journald
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=ff25ae92-8872-4d77-9510-b560a64e8d53 ro quiet splash init=/lib/systemd/systemd
Signal: 6
SourcePackage: systemd
 socket () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x5607d101a440, argc=1, argv=0x7ffdc5128ba8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdc5128b98) at libc-start.c:289
Title: systemd-journald crashed with SIGABRT in socket()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

Logan Rosen (logan) wrote :

 socket () at ../sysdeps/unix/syscall-template.S:81
 sd_pid_notify_with_fds.constprop.123 (state=0x5607d104c741 "WATCHDOG=1", fds=0x0, n_fds=0, unset_environment=0, pid=0) at ../src/libsystemd/sd-daemon/sd-daemon.c:379
 process_watchdog (e=0x5607d1bf61e0) at ../src/libsystemd/sd-event/sd-event.c:2296
 sd_event_wait (e=0x5607d1bf61e0, timeout=<optimized out>) at ../src/libsystemd/sd-event/sd-event.c:2411
 sd_event_run (timeout=<optimized out>, e=0x5607d1bf61e0) at ../src/libsystemd/sd-event/sd-event.c:2496

Changed in systemd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in systemd (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers