Hi Ian, I've shutdown and restarted several times since my comment above and I'm not seeing any delays on shutting down or rebooting now. But here are a some extracts from the last two weeks:
Apr 08 11:46:59 n1644 systemd[1]: Stopping Snap Daemon... Apr 08 11:47:24 n1644 snapd[980]: daemon.go:583: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s Apr 08 11:48:29 n1644 systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing. Apr 08 11:48:29 n1644 systemd[1]: snapd.service: Killing process 980 (snapd) with signal SIGKILL. Apr 08 11:48:29 n1644 systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL Apr 08 11:48:29 n1644 systemd[1]: snapd.service: Failed with result 'timeout'. Apr 08 11:48:29 n1644 systemd[1]: Stopped Snap Daemon. Apr 08 11:48:29 n1644 systemd[1]: snapd.service: Triggering OnFailure= dependencies. Apr 08 11:48:29 n1644 systemd[1]: snapd.service: Failed to enqueue OnFailure= job, ignoring: Transaction for snapd.failure.service/start is destructive (systemd-fsck@dev-disk-by\x2duuid-bb3ea850\x2d7b5c\x2d435f\x2d82d4\x2dd9961eecfbd4.service has 'stop' job queued, but 'start' is included in transaction). Apr 09 22:45:14 n1644 systemd[1]: Stopping Snap Daemon... Apr 09 22:45:39 n1644 snapd[981]: daemon.go:583: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s Apr 09 22:46:44 n1644 systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing. Apr 09 22:46:44 n1644 systemd[1]: snapd.service: Killing process 981 (snapd) with signal SIGKILL. Apr 09 22:46:44 n1644 systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL Apr 09 22:46:44 n1644 systemd[1]: snapd.service: Failed with result 'timeout'. Apr 09 22:46:44 n1644 systemd[1]: Stopped Snap Daemon. Apr 09 22:46:44 n1644 systemd[1]: snapd.service: Triggering OnFailure= dependencies. Apr 09 22:46:44 n1644 systemd[1]: snapd.service: Failed to enqueue OnFailure= job, ignoring: Transaction for snapd.failure.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction). Apr 18 15:10:21 n1644 systemd[1]: Stopping Snap Daemon... Apr 18 15:10:21 n1644 snapd[985]: main.go:155: Exiting on terminated signal. Apr 18 15:10:46 n1644 snapd[985]: daemon.go:583: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s Apr 18 15:11:51 n1644 systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing. Apr 18 15:11:51 n1644 systemd[1]: snapd.service: Killing process 985 (snapd) with signal SIGKILL. Apr 18 15:11:51 n1644 systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL Apr 18 15:11:51 n1644 systemd[1]: snapd.service: Failed with result 'timeout'. Apr 18 15:11:51 n1644 systemd[1]: Stopped Snap Daemon. Apr 18 15:11:51 n1644 systemd[1]: snapd.service: Triggering OnFailure= dependencies. Apr 18 15:11:51 n1644 systemd[1]: snapd.service: Failed to enqueue OnFailure= job, ignoring: Transaction for snapd.failure.service/start is destructive (swapfile.swap has 'stop' job queued, but 'start' is included in transaction). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873550 Title: Snappy daemon reaches 1min30s timeout during shutdown process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
