test@localhost:~$ systemctl status snapd.service
● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Tue 2017-03-14 19:48:44 UTC; 3s ago
 Main PID: 1459 (code=exited, status=0/SUCCESS)

test@localhost:~$ sudo journalctl -u snapd
-- Logs begin at Tue 2017-03-14 19:48:13 UTC, end at Fri 2017-11-10 14:28:52 UTC. --
Mar 14 19:48:22 localhost.localdomain systemd[1]: Starting Snappy daemon...
Mar 14 19:48:23 localhost.localdomain snapd[1459]: AppArmor status: apparmor is enabled and all features are available
Mar 14 19:48:24 localhost.localdomain snapd[1459]: 2017/03/14 19:48:24.223070 daemon.go:306: started snapd/2.29.3 (series 16) ubuntu-core/16 (arm64) linux/4.4.0-1078-snapdragon.
Mar 14 19:48:24 localhost.localdomain systemd[1]: Started Snappy daemon.
Mar 14 19:48:24 localhost.localdomain snapd[1459]: 2017/03/14 19:48:24.280153 snapmgr.go:404: Cannot prepare auto-refresh change: cannot refresh snap-declaration for "dragonboard-kernel": Get https://api.
Mar 14 19:48:24 localhost.localdomain snapd[1459]: 2017/03/14 19:48:24.283665 stateengine.go:98: state ensure error: cannot refresh snap-declaration for "dragonboard-kernel": Get https://api.snapcraft.io/
Mar 14 19:48:43 localhost.localdomain snapd[1459]: 2017/03/14 19:48:43.810823 snapmgr.go:378: cannot use refresh.schedule configuration: "thu@12:00-14:00" uses weekdays which is currently not supported
Mar 14 19:48:44 localhost.localdomain systemd[1]: Stopping Snappy daemon...
Mar 14 19:48:44 localhost.localdomain snapd[1459]: 2017/03/14 19:48:44.115541 main.go:78: Exiting on terminated signal.
Mar 14 19:48:44 localhost.localdomain systemd[1]: Stopped Snappy daemon.