Comment 18 for bug 1873550

Revision history for this message
Paul White (paulw2u) wrote :

First report of timeout since April 29:

May 14 21:28:54 n1644 systemd[1]: Stopping Snap Daemon...
May 14 21:28:54 n1644 snapd[979]: main.go:155: Exiting on terminated signal.
May 14 21:29:19 n1644 snapd[979]: daemon.go:583: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s
May 14 21:30:24 n1644 systemd[1]: snapd.service: State 'stop-sigterm' timed out. Killing.
May 14 21:30:24 n1644 systemd[1]: snapd.service: Killing process 979 (snapd) with signal SIGKILL.
May 14 21:30:24 n1644 systemd[1]: snapd.service: Main process exited, code=killed, status=9/KILL
May 14 21:30:24 n1644 systemd[1]: snapd.service: Failed with result 'timeout'.
May 14 21:30:24 n1644 systemd[1]: Stopped Snap Daemon.
May 14 21:30:24 n1644 systemd[1]: snapd.service: Triggering OnFailure= dependencies.
May 14 21:30:24 n1644 systemd[1]: snapd.service: Failed to enqueue OnFailure= job, ignoring: Transaction for snapd.failure.service/start is destructive (systemd-update-utmp.service has 'stop' job queued, but 'start' is included in transaction).

paul@n1644:~$ snap changes
ID Status Spawn Ready Summary
630 Done yesterday at 15:18 BST yesterday at 15:18 BST Refresh all snaps: no updates
631 Done yesterday at 21:05 BST yesterday at 21:05 BST Refresh all snaps: no updates
632 Done today at 10:04 BST today at 10:04 BST Connect chromium:password-manager-service to core:password-manager-service