Today I noticed an error during shutdown of the previous boot.
> journalctl --no-pager -o short-monotonic -b -1 -p err
8.868373] Mobile-PC kernel: Bluetooth: hci0: HCI_REQ-0xfcf0
14.890184] Mobile-PC lightdm[1583]: gkr-pam: unable to locate daemon control file
102.954036] Mobile-PC systemd-coredump[2522]: Failed to connect to coredump service: Connection refused
Since there is only a systemd-coredump.socket, I checked it.
> journalctl --no-pager -b -1 -o short-monotonic -u systemd-coredump.socket
102.875428] Mobile-PC systemd[1]: systemd-coredump.socket: Deactivated successfully.
102.875494] Mobile-PC systemd[1]: Closed Process Core Dump Socket.
It appears to shutdown correctly, so I dug a little deeper.
> journalctl -b -1 -o short-monotonic | grep -C 5 'Failed to connect to coredump service: Connection refused'
102.953296] Mobile-PC systemd[1601]: Removed slice User Application Slice.
102.953364] Mobile-PC systemd[1601]: Reached target Shutdown.
102.953465] Mobile-PC systemd[1601]: Finished Exit the Session.
102.953517] Mobile-PC systemd[1601]: Reached target Exit the Session.
102.953979] Mobile-PC systemd[1]: Stopping Postfix Mail Transport Agent...
102.954036] Mobile-PC systemd-coredump[2522]: Failed to connect to coredump service: Connection refused
102.954964] Mobile-PC systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT
102.955115] Mobile-PC systemd[1]: udisks2.service: Failed with result 'core-dump'.
102.955169] Mobile-PC systemd[1]: Stopped Disk Manager.
102.955478] Mobile-PC systemd[1]: user@1000.service: Deactivated successfully.
102.955560] Mobile-PC systemd[1]: Stopped User Manager for UID 1000.
Something appears to be trying to connect to systemd-coredump.socket after it’s deactivated, and the only thing I can see is the coredump from udisks2.service while it’s shutting down. I’d love to check the back trace for udisks2.service, but I haven’t come with a way to do that yet…
Any ideas?
Thanks,
Gene
