Nov 28 18:54:55 hostname systemd[1]: Started Snap Daemon. Nov 28 18:55:06 hostname snapd[770]: main.go:155: Exiting on terminated signal. Nov 28 18:55:06 hostname systemd[1]: Stopping Snap Daemon... Nov 28 18:55:19 hostname snapd[770]: autorefresh.go:398: Cannot prepare auto-refresh change due to a permanent network error: persistent network error: Get https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/xxx/xxx?max-format=4: dial tcp: lookup api.snapcraft.io: Temporary failure in name resolution Nov 28 18:56:04 hostname snapd[770]: stateengine.go:150: state ensure error: persistent network error: Get https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/xxx/xxx?max-format=4: dial tcp: lookup api.snapcraft.io: Temporary failure in name resolution Nov 28 18:56:04 hostname systemd[1]: snapd.service: Succeeded. Nov 28 18:56:04 hostname systemd[1]: Stopped Snap Daemon.
For anyone looking for a workaround: $ sudo systemctl edit snapd.service If empty, only add the following: [Service] TimeoutSec=15 I guess the value of TimeoutSec depends on how much you value the data integrity of snaps/containers that you run. I prefer not having snaps at all. I only still have it for LXD because it stopped doing apt packages. Anyway the LXC containers I run are not important, so 3 seconds is more than enough for me personally. -- 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
