Added SNAPD_DEBUG=1 to /etc/environment, restarted snapd.service and running ‘journalctl -xe | grep -i snapd | less’ returns me the following:
audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapd comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
systemd[1]: snapd.service: Unit entered failed state.
systemd[1]: snapd.service: Failed with result 'exit-code'.
systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapd comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapd comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-- Subject: Unit snapd.service has finished shutting down
-- Unit snapd.service has finished shutting down.
-- Subject: Unit snapd.service has begun start-up
-- Unit snapd.service has begun starting up.
snapd[21986]: AppArmor status: apparmor is enabled and all features are available
snapd[21986]: 2018/01/16 18:13:27.612463 cmd.go:212: DEBUG: restarting into "/snap/core/current/usr/lib/snapd/snapd"
snapd[21986]: AppArmor status: apparmor is enabled and all features are available
snapd[21986]: error: invalid character '#' looking for beginning of value
systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit snapd.service has failed
-- Unit snapd.service has failed.
Running ‘ls -la /var/lib/snapd/state.json’ returns me the following:
-rw------- 1 debian-tor debian-tor 35909 Jan 12 17:31 /var/lib/snapd/state.json
I did not manually edit /var/lib/snapd/state.json . It seems to me the file state.json is being generated by debian-tor last Friday, about time that snapd.service failed to work the next day. Do you need me to attach the ‘state.json’ file? Thanks for advice.