moving this issue over from the linuxcontainers forum where I was advised this problem to be a not normal behavior of snapd rather then the lxd snap itself.
the entire issue started with not being able to enable the LXD snap any longer
error: cannot perform the following tasks:
- Start snap "lxd" (11381) services ([start snap.lxd.activate.service] failed with exit status 1: Job for snap.lxd.activate.service failed because the control process exited with error code.
See "systemctl status snap.lxd.activate.service" and "journalctl -xe" for details.
)
refreshing the snap does not work obviously because it is in a disabled status. So I am kind of stuck.
**systemctl status snap.lxd.activate.service**
● snap.lxd.activate.service
Loaded: not-found (Reason: No such file or directory)
Active: failed (Result: exit-code) since Thu 2019-08-01 06:47:02 CEST; 24min ago
Main PID: 23486 (code=exited, status=1/FAILURE)
CPU: 122ms
**sudo journalctl -xe**
--
-- Unit UNIT has begun starting up.
Aug 01 07:08:34 debian dbus-daemon[3207]: Successfully activated service 'org.freedesktop.Notifications'
Aug 01 07:08:34 debian systemd[3185]: Started XFCE notifications service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 01 07:08:34 debian xfce4-notifyd[24993]: Failed to set text 'Profil aktualisieren & Nachfrage steigern from Betreut.de
Das sind unsere Tipps für ein aussagekrä' from markup due to error parsing markup: Error on line 1: Enti
Aug 01 07:09:01 debian CRON[24997]: pam_unix(cron:session): session opened for user root by (uid=0)
Aug 01 07:09:01 debian CRON[24998]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean
Aug 01 07:09:01 debian CRON[24997]: pam_unix(cron:session): session closed for user root
Aug 01 07:09:10 debian systemd[1]: Starting Clean php session files...
-- Subject: Unit phpsessionclean.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit phpsessionclean.service has begun starting up.
Aug 01 07:09:12 debian systemd[1]: Started Clean php session files.
-- Subject: Unit phpsessionclean.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit phpsessionclean.service has finished starting up.
--
-- The start-up result is done.
Aug 01 07:13:03 debian sudo[25055]: manolo : TTY=pts/1 ; PWD=/home/[myusername] ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 01 07:13:03 debian sudo[25055]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 01 07:13:18 debian sudo[25055]: pam_unix(sudo:session): session closed for user root
Aug 01 07:13:24 debian sudo[25063]: manolo : TTY=pts/1 ; PWD=/home/[myusername] ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 01 07:13:24 debian sudo[25063]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 01 07:13:50 debian sudo[25063]: pam_unix(sudo:session): session closed for user root
Aug 01 07:14:02 debian sudo[25086]: manolo : TTY=pts/1 ; PWD=/home/[myusername] ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 01 07:14:02 debian sudo[25086]: pam_unix(sudo:session): session opened for user root by (uid=0)
any ideas where to go from here? The logs above do not tell me much I’m afraid