Public bug reported:
I installed some updated and was prompted to reboot. The shutdown part
of the reboot took a long time (over 1 minute 30 seconds), and I saw
that systemd was waiting for snapd to shut down cleanly before killing
it with SIGKILL 90 seconds later.
journalctl -b -1 -e shows this:
spal. 28 11:03:02 blynas systemd[1]: NetworkManager.service: Succeeded.
spal. 28 11:03:02 blynas systemd[1]: Stopped Network Manager.
spal. 28 11:03:02 blynas systemd[1]: Stopping D-Bus System Message Bus...
spal. 28 11:03:02 blynas systemd[1]: dbus.service: Succeeded.
spal. 28 11:03:02 blynas systemd[1]: dbus.service: Unit process 989
(dbus-daemon) remains running after unit stopped.
spal. 28 11:03:02 blynas systemd[1]: dbus.service: Unit process 322309
(python3) remains running after unit stopped.
spal. 28 11:03:02 blynas systemd[1]: Stopped D-Bus System Message Bus.
spal. 28 11:03:02 blynas thermald[1025]: terminating on user request ..
spal. 28 11:03:03 blynas systemd[1]: thermald.service: Succeeded.
spal. 28 11:03:03 blynas systemd[1]: Stopped Thermal Daemon Service.
spal. 28 11:03:03 blynas clamd[1036]: Wed Oct 28 11:03:03 2020 -> --- Stopped
at Wed Oct 28 11:03:03 2020
spal. 28 11:03:03 blynas clamd[1036]: Wed Oct 28 11:03:03 2020 -> Socket file
removed.
spal. 28 11:03:03 blynas systemd[1]: clamav-daemon.service: Succeeded.
spal. 28 11:03:03 blynas systemd[1]: Stopped Clam AntiVirus userspace daemon.
spal. 28 11:03:26 blynas snapd[1013]: daemon.go:586: WARNING: cannot gracefully
shut down in-flight snapd API activity within: 25s
spal. 28 11:04:31 blynas systemd[1]: snapd.service: State 'stop-sigterm' timed
out. Killing.
spal. 28 11:04:31 blynas systemd[1]: snapd.service: Killing process 1013
(snapd) with signal SIGKILL.
spal. 28 11:04:31 blynas systemd[1]: snapd.service: Main process exited,
code=killed, status=9/KILL
spal. 28 11:04:31 blynas systemd[1]: snapd.service: Failed with result
'timeout'.
spal. 28 11:04:31 blynas systemd[1]: Stopped Snap Daemon.
spal. 28 11:04:31 blynas systemd[1]: snapd.service: Triggering OnFailure=
dependencies.
spal. 28 11:04:31 blynas systemd[1]: Requested transaction contradicts existing
jobs: Transaction for snapd.failure.service/start is destructive
(systemd-remount-fs.service has 'stop' job queued, but 'start' is included in
transaction).
spal. 28 11:04:31 blynas systemd[1]: snapd.service: Failed to enqueue
OnFailure= job, ignoring: Transaction for snapd.failure.service/start is
destructive (systemd-remount-fs.service has 'stop' job queued, but 'start' is
included in transaction).
spal. 28 11:04:31 blynas systemd[1]: Stopped target Basic System.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: snapd 2.47.1+20.10.1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 28 12:29:28 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (503 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: snapd
UpgradeStatus: Upgraded to groovy on 2020-10-23 (5 days ago)
modified.conffile..etc.sudoers.d.99-snapd.conf: [inaccessible: [Errno 13]
Permission denied: '/etc/sudoers.d/99-snapd.conf']
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901847
Title:
snapd fails to shut down, gets killed after 1m30s during reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1901847/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
