** infos **
sudo /usr/bin/snap version
** problem **
my lxd conf:
it happened april 19 and april 9 when snap refresh automaticaly snaps i think:
last one:
snap changes
185 Done 2018-04-18T17:00:02Z 2018-04-18T17:00:09Z Actualiser le paquet Snap “lxd”
i filled an issue on lxd too:https://github.com/lxc/lxd/issues/4427#issuecomment-382760893
Regards
FYI it is every time snap refreshes lxd.
FWIW what snapd does is a cp -av, so I struggle to understand what’s going on.
Is there anything interesting about your filesystem or its layout?
again today:
gaetanquentin-sfr@gquentin-ssd-t3:~$ ls -la snap/lxd/
total 0
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 1680 mai 7 09:15 .
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 336 févr. 14 14:06 ..
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 févr. 14 14:06 5866
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 févr. 14 14:06 6492
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 avril 9 09:24 6643
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 avril 19 08:23 6729
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 avril 19 08:23 6729.bak
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 avril 19 08:23 6862
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 mai 2 14:38 6879
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 168 mai 7 09:15 6954
drwxr-xr-x 1 gaetanquentin-sfr gaetanquentin-sfr 0 févr. 14 14:06 common
lrwxrwxrwx 1 gaetanquentin-sfr gaetanquentin-sfr 4 mai 7 09:15 current -> 6954
gaetanquentin-sfr@gquentin-ssd-t3:~$ ls -la snap/lxd/current/.config/lxc/
total 12
drwxr-x--- 1 gaetanquentin-sfr gaetanquentin-sfr 168 mai 7 09:15 .
drwxr-x--- 1 gaetanquentin-sfr gaetanquentin-sfr 168 mai 7 09:15 ..
-rw-r--r-- 1 gaetanquentin-sfr gaetanquentin-sfr 403 mai 7 09:15 config.yml
gaetanquentin-sfr@gquentin-ssd-t3:~$ ls -la snap/lxd/6879/.config/lxc/
total 84
drwxr-x--- 1 gaetanquentin-sfr gaetanquentin-sfr 1344 mai 3 15:01 .
drwxr-x--- 1 gaetanquentin-sfr gaetanquentin-sfr 168 mai 2 14:38 ..
-rw-r--r-- 1 gaetanquentin-sfr gaetanquentin-sfr 1988 févr. 19 23:51 _client.crt
-rw-rw-r-- 1 gaetanquentin-sfr gaetanquentin-sfr 2021 juin 2 2016 client.crt
-rw------- 1 gaetanquentin-sfr gaetanquentin-sfr 3247 févr. 19 23:51 _client.key
-rw------- 1 gaetanquentin-sfr gaetanquentin-sfr 3243 juin 2 2016 client.key
-rw-r--r-- 1 gaetanquentin-sfr gaetanquentin-sfr 727 avril 24 12:34 config.yml
-rw------- 1 gaetanquentin-sfr gaetanquentin-sfr 5 mai 2 16:51 cookies
-rw-r--r-- 1 gaetanquentin-sfr gaetanquentin-sfr 1952 avril 19 17:07 lxd-cert.crt
drwxr-x--- 1 gaetanquentin-sfr gaetanquentin-sfr 504 avril 24 12:34 servercerts
i dont’ think there i something special on my filesystem. it is btrfs.
If you don’t mind losing any extra data you added between 6879 and now, and confusing lxd even more (I don’t know for sure this will do the latter, but it might), could you, please,
snap revert --revision 6879 lxd
enable debug in snapd/etc/systemd/system/snapd.service.d/debug.conf (you might need to create the directory first):[Service]
Environment=SNAPD_DEBUG=1
systemctl daemon-reload && systemctl restart snapd.serviceSNAPD_DEBUG=1 in /etc/environment and then systemctl restart snapd.service, but that has other consequences like making any commandline snap app very very chatty).journalctl -u snapd.service; if it contains lines with DEBUG (e.g. DEBUG: activation done in ...), then it worked.
snap refresh --revision 6954 lxd (i.e. undo the blacklisting we did with revert).
You should see the same issues of missing files. If so, I’d like the contents of journalctl -u snapd.service. If not, … then we need to carry on looking.
hi, sorry for the late answer.
So it did it again:
total 0
trying to revert to 6954:
but current is still on 7275, is this normal?
gaetanquentin-sfr@gquentin-ssd-t3:~$ ls -la snap/lxd/
my remotes have come back!
going back to 7275:
remotes disappeared…
logs:
mai 31 09:11:02 gquentin-ssd-t3 snapd[26728]: 2018/05/31 09:11:02.978772 taskrunner.go:403: DEBUG: Running task 620 on Do: Assurez-vous que les prérequis pour “lxd” sont disponibles
gaetanquentin-sfr@gquentin-ssd-t3:~$ snap version
did it again:
logs:
juin 04 09:08:32 gquentin-ssd-t3 snapd[1229]: 2018/06/04 09:08:32.748657 daemon.go:252: DEBUG: pid=16357;uid=1002;socket=/run/snapd.socket;@ GET /v2/interfaces 269.603µs 200https://api.snapcraft.io/api/v1/snaps/details/lxd?channel=&fields=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_384%2Csumma https://api.snapcraft.io/api/v1/snaps/details/lxd?channel=&fields=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_3 https://api.snapcraft.io/api/v1/snaps/details/core?channel=&fields=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_384%2Csumm https://api.snapcraft.io/api/v1/snaps/details/core?channel=&fields=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_ https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/99T7MUlRhtI3U0QFgl5mXXESAiSwt776?max-format=2 , attempt 1, elapsed thttps://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/99T7MUlRhtI3U0QFgl5mXXESAiSwt776?max-format=2 finished afhttps://api.snapcraft.io/api/v1/snaps/assertions/account-key/BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul?max-format https://api.snapcraft.io/api/v1/snaps/assertions/account-key/BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul ?https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/Ee7LGphwQR669pcfCCdl0oJQouta69to?max-format=2 , attempt 1, elapsed thttps://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/Ee7LGphwQR669pcfCCdl0oJQouta69to?max-format=2 finished afhttps://api.snapcraft.io/api/v1/snaps/assertions/account/eEoV9TnaNkCzfJBu9SRhr2678vzyYV43?max-format=0 , attempt 1, elapsed time=2.15µshttps://api.snapcraft.io/api/v1/snaps/assertions/account/eEoV9TnaNkCzfJBu9SRhr2678vzyYV43?max-format=0 finished after 1 retriehttps://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/J60k4JY0HppjwOjW8dZdYc8obXKxujRu?max-format=2 , attempt 1, elapsed thttps://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/J60k4JY0HppjwOjW8dZdYc8obXKxujRu?max-format=2 finished afhttps://api.snapcraft.io/v2/snaps/refresh , attempt 1, elapsed time=2.891µshttps://api.snapcraft.io/v2/snaps/refresh finished after 1 retries, elapsed time=79.577991ms, status: 200
did it again…
sudo snap version
Again:
lxc exec vipteam_lab:xenial-java bash
gaetanquentin-sfr@gquentin-ssd-t3:~$ ls -la snap/lxd/current/.config/lxc/
gaetanquentin-sfr@gquentin-ssd-t3:~$ ls -la snap/lxd/8011/.config/lxc/
i had to copy again the last contents:
cp -a snap/lxd/8011/.config/lxc/* snap/lxd/current/.config/lxc/
chipaca
August 17, 2018, 10:07am
12
instead of saying ‘again’ every time it happens to you, could you please try the steps I asked you to try to get us actionable information ?
I may have found the root cause.
It did it again
In fact , it took it from the old ~/.config/lxc/config.yml
diff ~/.config/lxc/config.yml ~/snap/lxd/current/.config/lxc/config.yml
->the same
Is this normal for a snap to copy config from old non-snap config?
Doings your steps with revisions 10102 and 10150:
Current is 10150.
sudo snap revert --revision 10102 lxd
ls -la /snap/lxd/:
calling a lxc command , to update user’s config files:
config files are now reverted:
ls -la ~/snap/lxd/: current -> 10102
doing refresh:
sudo snap refresh --revision 10150 lxd
ls -la /snap/lxd/: current -> 10150
lxc list, to update config files
ls -la ~/snap/lxd/ : current -> 10150
My config file is now ok.
and gave me back an old configuration, which weren’t in none of the snap configuration history.