Got this little nugget while lxd is starting. How to resolve?
t=2019-02-08T09:23:48-0600 lvl=info msg=“LXD 3.9 is starting in normal mode” path=/var/snap/lxd/common/lxd
t=2019-02-08T09:23:50-0600 lvl=info msg=“Initializing global database”
t=2019-02-08T09:23:50-0600 lvl=eror msg=“Failed to start the daemon: failed to open cluster database: failed to ensure schema: this node’s version is behind, please upgrade”
t=2019-02-08T09:23:50-0600 lvl=info msg=“Starting shutdown sequence”
t=2019-02-08T09:23:50-0600 lvl=info msg=“Stopping REST API handler:”
One of my other servers:
t=2019-02-07T19:30:00-0600 lvl=info msg=“LXD 3.10 is starting in normal mode” path=/var/snap/lxd/common/lxd
t=2019-02-07T19:30:00-0600 lvl=info msg=“Kernel uid/gid map:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - u 0 0 4294967295"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - g 0 0 4294967295"
t=2019-02-07T19:30:00-0600 lvl=info msg=“Configured LXD uid/gid map:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - u 0 1000000 1000000000"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - g 0 1000000 1000000000"
t=2019-02-07T19:30:00-0600 lvl=warn msg=“CGroup memory swap accounting is disabled, swap limits will be ignored.”
t=2019-02-07T19:30:00-0600 lvl=info msg=“Kernel features:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - netnsid-based network retrieval: no"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - uevent injection: no"
t=2019-02-07T19:30:00-0600 lvl=info msg=" - unprivileged file capabilities: yes"
t=2019-02-07T19:30:00-0600 lvl=info msg=“Initializing local database”
t=2019-02-07T19:30:00-0600 lvl=info msg=“Starting /dev/lxd handler:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - binding devlxd socket" socket=/var/snap/lxd/common/lxd/devlxd/sock
t=2019-02-07T19:30:00-0600 lvl=info msg=“REST API daemon:”
t=2019-02-07T19:30:00-0600 lvl=info msg=" - binding Unix socket" inherited=true socket=/var/snap/lxd/common/lxd/unix.socket
t=2019-02-07T19:30:00-0600 lvl=info msg=" - binding TCP socket" socket=snip1:8443
t=2019-02-07T19:30:00-0600 lvl=info msg=“Initializing global database”
t=2019-02-07T19:30:00-0600 lvl=info msg=“Wait for other cluster nodes to upgrade their versions”
t=2019-02-08T08:51:34-0600 lvl=warn msg=“Raft: Heartbeat timeout from “snip2:8443” reached, starting election”
t=2019-02-08T08:51:39-0600 lvl=warn msg=“Raft: Election timeout reached, restarting election”
t=2019-02-08T08:51:43-0600 lvl=warn msg=“Raft: Election timeout reached, restarting election”
t=2019-02-08T08:51:48-0600 lvl=warn msg=“Raft: Election timeout reached, restarting election”
obviously my running server is a newer version of lxd. I see that now, odd that the others didn’t update as well though.
I guess I’m testing the candidate branch =)
LXD clusters detect version mismatch at runtime and self-trigger a refresh, this does require all node to be on the same channel though, I wonder if you may have had one node on the candidate channel and the rest on the stable channel, which would explain why the self-refresh didn’t work in your case.
You can check that with snap info lxd on all nodes, making sure that the current channel is the same on all of them. We obviously don’t recommend having production systems on the candidate channel, but you won’t be able to switch back to stable until we release 3.10 to stable early next week (as downgrades aren’t supported).
Yeah, one was. All good, just a slight heart attack early in the morning. I thought I had switched them all back. Maybe on this next go around.
I have the same problem:
root@lxd0x:/var/snap/lxd/common/lxd/database/global# lxd --debug --group lxd
DBUG[09-25|09:05:25] Connecting to a local LXD over a Unix socket
DBUG[09-25|09:05:25] Sending request to LXD method=GET url=http://unix.socket/1.0 etag=
INFO[09-25|09:05:25] LXD 4.4 is starting in normal mode path=/var/snap/lxd/common/lxd
INFO[09-25|09:05:25] Kernel uid/gid map:
INFO[09-25|09:05:25] - u 0 0 4294967295
INFO[09-25|09:05:25] - g 0 0 4294967295
INFO[09-25|09:05:25] Configured LXD uid/gid map:
INFO[09-25|09:05:25] - u 0 1000000 1000000000
INFO[09-25|09:05:25] - g 0 1000000 1000000000
INFO[09-25|09:05:25] Kernel features:
INFO[09-25|09:05:25] - closing multiple file descriptros efficiently: no
INFO[09-25|09:05:25] - netnsid-based network retrieval: yes
INFO[09-25|09:05:25] - pidfds: yes
INFO[09-25|09:05:25] - uevent injection: yes
INFO[09-25|09:05:25] - seccomp listener: yes
INFO[09-25|09:05:25] - seccomp listener continue syscalls: yes
INFO[09-25|09:05:25] - seccomp listener add file descriptors: no
INFO[09-25|09:05:25] - safe native terminal allocation : no
INFO[09-25|09:05:25] - unprivileged file capabilities: yes
INFO[09-25|09:05:25] - cgroup layout: hybrid
WARN[09-25|09:05:25] - Couldn’t find the CGroup blkio.weight, I/O weight limits will be ignored
WARN[09-25|09:05:25] - Couldn’t find the CGroup memory swap accounting, swap limits will be ignored
INFO[09-25|09:05:25] - shiftfs support: yes
INFO[09-25|09:05:25] Initializing local database
DBUG[09-25|09:05:25] Initializing database gateway
DBUG[09-25|09:05:25] Start database node id=1 address=192.168.100.54:8443 role=voter
DBUG[09-25|09:05:26] Connecting to a local LXD over a Unix socket
DBUG[09-25|09:05:26] Sending request to LXD method=GET url=http://unix.socket/1.0 etag=
DBUG[09-25|09:05:26] Detected stale unix socket, deleting
INFO[09-25|09:05:26] Starting cluster handler:
INFO[09-25|09:05:26] Starting /dev/lxd handler:
INFO[09-25|09:05:26] - binding devlxd socket socket=/var/snap/lxd/common/lxd/devlxd/sock
INFO[09-25|09:05:26] REST API daemon:
INFO[09-25|09:05:26] - binding Unix socket socket=/var/snap/lxd/common/lxd/unix.socket
INFO[09-25|09:05:26] - binding TCP socket socket=192.168.100.54:8443
INFO[09-25|09:05:26] Initializing global database
WARN[09-25|09:05:26] Dqlite: attempt 0: server 192.168.100.53:8443: no known leader
DBUG[09-25|09:05:26] Found cert name=0
DBUG[09-25|09:05:26] Dqlite: attempt 0: server 192.168.100.54:8443: connected
DBUG[09-25|09:05:26] Database error: &errors.errorString{s:“this node’s version is behind, please upgrade”}
EROR[09-25|09:05:26] Failed to start the daemon: failed to open cluster database: failed to ensure schema: this node’s version is behind, please upgrade
INFO[09-25|09:05:26] Starting shutdown sequence
INFO[09-25|09:05:26] Stop database gateway
DBUG[09-25|09:05:26] Found cert name=0
INFO[09-25|09:05:26] Stopping REST API handler:
INFO[09-25|09:05:26] - closing socket socket=192.168.100.54:8443
INFO[09-25|09:05:26] - closing socket socket=/var/snap/lxd/common/lxd/unix.socket
INFO[09-25|09:05:26] Stopping /dev/lxd handler:
INFO[09-25|09:05:26] - closing socket socket=/var/snap/lxd/common/lxd/devlxd/sock
DBUG[09-25|09:05:26] Not unmounting temporary filesystems (containers are still running)
Error: failed to open cluster database: failed to ensure schema: this node’s version is behind, please upgrade
==================
root@lxd0x:/var/snap/lxd/common/lxd/database/global# snap info lxd
name: lxd
summary: System container manager and API
publisher: Canonical✓
store-url: https://snapcraft.io/lxd
contact: https://github.com/lxc/lxd/issues
license: unset
description: |
LXD is a system container manager
With LXD you can run hundreds of containers of a variety of Linux
distributions, apply resource limits, pass in directories, USB devices
or GPUs and setup any network and storage you want.
LXD containers are lightweight, secure by default and a great
alternative to running Linux virtual machines.
Run any Linux distribution you want
Pre-made images are available for Ubuntu, Alpine Linux, ArchLinux,
CentOS, Debian, Fedora, Gentoo, OpenSUSE and more.
A full list of available images can be found here: https://images.linuxcontainers.org
Can’t find the distribution you want? It’s easy to make your own images too, either using our
distrobuilder tool or by assembling your own image tarball by hand.
Containers at scale
LXD is network aware and all interactions go through a simple REST API,
making it possible to remotely interact with containers on remote
systems, copying and moving them as you wish.
Want to go big? LXD also has built-in clustering support,
letting you turn dozens of servers into one big LXD server.
Configuration options
Supported options for the LXD snap (snap set lxd KEY=VALUE):
- ceph.builtin: Use snap-specific ceph configuration [default=false]
- criu.enable: Enable experimental live-migration support [default=false]
- daemon.debug: Increases logging to debug level [default=false]
- daemon.group: Group of users that can interact with LXD [default=lxd]
- daemon.preseed: A YAML configuration to feed lxd init on initial start
- lxcfs.pidfd: Start per-container process tracking [default=false]
- lxcfs.loadavg: Start tracking per-container load average [default=false]
- lxcfs.cfs: Consider CPU shares for CPU usage [default=false]
- openvswitch.builtin: Run a snap-specific OVS daemon [default=false]
- shiftfs.enable: Enable shiftfs support [default=auto]
Documentation: https://lxd.readthedocs.io
commands:
- lxd.benchmark
- lxd.buginfo
- lxd.check-kernel
- lxd.lxc
- lxd.lxc-to-lxd
- lxd
- lxd.migrate
services:
lxd.activate: oneshot, enabled, inactive
lxd.daemon: simple, enabled, inactive
snap-id: J60k4JY0HppjwOjW8dZdYc8obXKxujRu
tracking: 4.4/stable
refresh-date: 18 days ago, at 11:23 UTC
channels:
latest/stable: 4.6 2020-09-21 (17320) 71MB -
latest/candidate: 4.6 2020-09-24 (17441) 71MB -
latest/beta: ↑
latest/edge: git-08f9d81 2020-09-25 (17451) 71MB -
4.6/stable: 4.6 2020-09-21 (17320) 71MB -
4.6/candidate: 4.6 2020-09-24 (17441) 71MB -
4.6/beta: ↑
4.6/edge: ↑
4.5/stable: 4.5 2020-09-18 (17299) 71MB -
4.5/candidate: 4.5 2020-09-18 (17299) 71MB -
4.5/beta: ↑
4.5/edge: ↑
4.4/stable: 4.4 2020-08-19 (16926) 74MB -
4.4/candidate: 4.4 2020-08-19 (16926) 74MB -
4.4/beta: ↑
4.4/edge: ↑
4.3/stable: 4.3 2020-07-09 (16100) 74MB -
4.3/candidate: 4.3 2020-07-20 (16380) 74MB -
4.3/beta: ↑
4.3/edge: ↑
4.0/stable: 4.0.3 2020-08-19 (16922) 73MB -
4.0/candidate: 4.0.3 2020-08-19 (16922) 73MB -
4.0/beta: ↑
4.0/edge: git-9b6e89e 2020-09-24 (17417) 70MB -
3.0/stable: 3.0.4 2019-10-10 (11348) 55MB -
3.0/candidate: 3.0.4 2019-10-10 (11348) 55MB -
3.0/beta: ↑
3.0/edge: git-81b81b9 2019-10-10 (11362) 55MB -
2.0/stable: 2.0.12 2020-08-18 (16879) 38MB -
2.0/candidate: 2.0.12 2020-08-17 (16879) 38MB -
2.0/beta: ↑
2.0/edge: git-82c7d62 2020-08-17 (16867) 39MB -
installed: 4.4 (16926) 74MB -
Other SERVER
quersys@lxd02 ~> snap info lxd
name: lxd
summary: System container manager and API
publisher: Canonical✓
store-url: https://snapcraft.io/lxd
contact: https://github.com/lxc/lxd/issues
license: unset
description: |
LXD is a system container manager
With LXD you can run hundreds of containers of a variety of Linux
distributions, apply resource limits, pass in directories, USB devices
or GPUs and setup any network and storage you want.
LXD containers are lightweight, secure by default and a great
alternative to running Linux virtual machines.
Run any Linux distribution you want
Pre-made images are available for Ubuntu, Alpine Linux, ArchLinux,
CentOS, Debian, Fedora, Gentoo, OpenSUSE and more.
A full list of available images can be found here: https://images.linuxcontainers.org
Can’t find the distribution you want? It’s easy to make your own images too, either using our
distrobuilder tool or by assembling your own image tarball by hand.
Containers at scale
LXD is network aware and all interactions go through a simple REST API,
making it possible to remotely interact with containers on remote
systems, copying and moving them as you wish.
Want to go big? LXD also has built-in clustering support,
letting you turn dozens of servers into one big LXD server.
Configuration options
Supported options for the LXD snap (snap set lxd KEY=VALUE):
- ceph.builtin: Use snap-specific ceph configuration [default=false]
- criu.enable: Enable experimental live-migration support [default=false]
- daemon.debug: Increases logging to debug level [default=false]
- daemon.group: Group of users that can interact with LXD [default=lxd]
- daemon.preseed: A YAML configuration to feed lxd init on initial start
- lxcfs.pidfd: Start per-container process tracking [default=false]
- lxcfs.loadavg: Start tracking per-container load average [default=false]
- lxcfs.cfs: Consider CPU shares for CPU usage [default=false]
- openvswitch.builtin: Run a snap-specific OVS daemon [default=false]
- shiftfs.enable: Enable shiftfs support [default=auto]
Documentation: https://lxd.readthedocs.io
commands:
- lxd.benchmark
- lxd.buginfo
- lxd.check-kernel
- lxd.lxc
- lxd.lxc-to-lxd
- lxd
- lxd.migrate
services:
lxd.activate: oneshot, enabled, inactive
lxd.daemon: simple, enabled, active
snap-id: J60k4JY0HppjwOjW8dZdYc8obXKxujRu
tracking: latest/stable
refresh-date: yesterday at 16:37 UTC
channels:
latest/stable: 4.6 2020-09-21 (17320) 71MB -
latest/candidate: 4.6 2020-09-24 (17441) 71MB -
latest/beta: ↑
latest/edge: git-08f9d81 2020-09-25 (17451) 71MB -
4.6/stable: 4.6 2020-09-21 (17320) 71MB -
4.6/candidate: 4.6 2020-09-24 (17441) 71MB -
4.6/beta: ↑
4.6/edge: ↑
4.5/stable: 4.5 2020-09-18 (17299) 71MB -
4.5/candidate: 4.5 2020-09-18 (17299) 71MB -
4.5/beta: ↑
4.5/edge: ↑
4.4/stable: 4.4 2020-08-19 (16926) 74MB -
4.4/candidate: 4.4 2020-08-19 (16926) 74MB -
4.4/beta: ↑
4.4/edge: ↑
4.3/stable: 4.3 2020-07-09 (16100) 74MB -
4.3/candidate: 4.3 2020-07-20 (16380) 74MB -
4.3/beta: ↑
4.3/edge: ↑
4.0/stable: 4.0.3 2020-08-19 (16922) 73MB -
4.0/candidate: 4.0.3 2020-08-19 (16922) 73MB -
4.0/beta: ↑
4.0/edge: git-9b6e89e 2020-09-24 (17417) 70MB -
3.0/stable: 3.0.4 2019-10-10 (11348) 55MB -
3.0/candidate: 3.0.4 2019-10-10 (11348) 55MB -
3.0/beta: ↑
3.0/edge: git-81b81b9 2019-10-10 (11362) 55MB -
2.0/stable: 2.0.12 2020-08-18 (16879) 38MB -
2.0/candidate: 2.0.12 2020-08-17 (16879) 38MB -
2.0/beta: ↑
2.0/edge: git-82c7d62 2020-08-17 (16867) 39MB -
installed: 4.6 (17320) 71MB -
And
root@lxd0x:/var/snap/lxd/common/lxd/database/global# snap list | grep lxd
lxd 4.4 16926 4.4/stable canonical* -
root@lxd0x:/var/snap/lxd/common/lxd/database/global# sudo snap refresh
error: unable to contact snap store
root@lxd02:/home/quersys# snap list | grep lxd
lxd 4.6 17320 latest/stable canonical* -
root@lxd02:/home/quersys# sudo snap refresh
All snaps up to date.
Which command I should use to solve this issue?
Try systemctl restart snapd on that system, if it still fails to contact the store, then look for firewalls or similar network filters/proxies which could interfere with the connection.
Thaks, I tried.
root@lxd0x:~# systemctl restart snapd
root@lxd0x:~# lxc list
Error: Get “http://unix.socket/1.0”: dial unix /var/snap/lxd/common/lxd/unix.socket: connect: connection refused
root@lxd0x:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=6.80 ms
I do not understand what exactly did not work 
May be do you need some logs?
It won’t magically come back up after restarting snapd, you need that snap refresh to update LXD to match the other nodes.
Does snap refresh succeed now? And if so, does snap list show 4.6 now?
root@lxd0x:~# snap refresh
error: unable to contact snap store
root@lxd0x:~# sudo snap refresh snapd
error: unable to contact snap store
The same issue. But i installed “snap install hello-world”
root@lxd0x:/var/snap/lxd/common/lxd/database/global#
hello-world 6.4 from Canonical✓ installed
root@lxd0x:/var/snap/lxd/common/lxd/database/global# hello-world
Hello World!
This is a bit odd.
Could you show journalctl -u snapd -n 300 see if maybe it logged something useful?
To many lines, I put this into txt file
You seem to have truncated the log to the right a bit.
Maybe try journalctl -u snapd -n 300 | cat ?
This feels like a snapd or network issue though, I see the beginning of a network error in there.
https://forum.snapcraft.io may be able to help you get snap refresh to work properly again which will unstick everything. This still feels a lot like partly broken networking, possibly MTU related which may explain why some queries succeed when others fail.
Hello!
Status service
root@lxd0x:/home/quersys# systemctl status snapd.service
● snapd.service - Snap Daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-09-25 12:59:57 UTC; 2 days ago
TriggeredBy: ● snapd.socket
Main PID: 19486 (snapd)
Tasks: 12 (limit: 4620)
Memory: 26.2M
CGroup: /system.slice/snapd.service
└─19486 /usr/lib/snapd/snapd
Sep 27 00:20:43 lxd0x snapd[19486]: autorefresh.go:403: Cannot prepare auto-refresh change: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: req>
Sep 27 00:20:43 lxd0x snapd[19486]: stateengine.go:150: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: request canceled (C>
Sep 27 10:40:43 lxd0x snapd[19486]: autorefresh.go:403: Cannot prepare auto-refresh change: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: req>
Sep 27 10:40:43 lxd0x snapd[19486]: stateengine.go:150: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: request canceled (C>
Sep 27 15:35:43 lxd0x snapd[19486]: autorefresh.go:403: Cannot prepare auto-refresh change: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: req>
Sep 27 15:35:43 lxd0x snapd[19486]: stateengine.go:150: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: request canceled (C>
Sep 27 19:30:43 lxd0x snapd[19486]: autorefresh.go:403: Cannot prepare auto-refresh change: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: req>
Sep 27 19:30:43 lxd0x snapd[19486]: stateengine.go:150: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: request canceled (C>
Sep 28 04:15:43 lxd0x snapd[19486]: autorefresh.go:403: Cannot prepare auto-refresh change: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: req>
Sep 28 04:15:44 lxd0x snapd[19486]: stateengine.go:150: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: net/http: request canceled (C
Here is result command: journalctl -u snapd -n 300 | cat
https://yadi.sk/i/QSDhfJS2JF6X5w
I also have other issue
root@lxd0x:/home/quersys# lxd
WARN[09-28|08:20:47] - Couldn’t find the CGroup blkio.weight, I/O weight limits will be ignored
WARN[09-28|08:20:47] - Couldn’t find the CGroup memory swap accounting, swap limits will be ignored
EROR[09-28|08:20:47] Failed to start the daemon: Failed to start dqlite server: raft_start(): io: load closed segment 0000000000158008-0000000000158008: entries batch 1 starting at byte 8: read preamble: short read: 0 bytes instead of 16
Error: Failed to start dqlite server: raft_start(): io: load closed segment 0000000000158008-0000000000158008: entries batch 1 starting at byte 8: read preamble: short read: 0 bytes instead of 16
I solved issue with no connect to snap store
Then i use
root@lxd0x:/var/snap/lxd/common/lxd/database/global# sudo snap refresh --channel=4.6/stable lxd
error: cannot perform the following tasks:
- Stop snap “lxd” 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.
) - Start snap “lxd” (17320) 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.
)
Log:
root@lxd0x:/var/snap/lxd/common/lxd/database/global# cat /var/snap/lxd/common/lxd/logs/lxd.log
t=2020-09-28T15:50:16+0000 lvl=info msg=“LXD 4.4 is starting in normal mode” path=/var/snap/lxd/common/lxd
t=2020-09-28T15:50:16+0000 lvl=info msg=“Kernel uid/gid map:”
t=2020-09-28T15:50:16+0000 lvl=info msg=" - u 0 0 4294967295"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - g 0 0 4294967295"
t=2020-09-28T15:50:16+0000 lvl=info msg=“Configured LXD uid/gid map:”
t=2020-09-28T15:50:16+0000 lvl=info msg=" - u 0 1000000 1000000000"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - g 0 1000000 1000000000"
t=2020-09-28T15:50:16+0000 lvl=info msg=“Kernel features:”
t=2020-09-28T15:50:16+0000 lvl=info msg=" - closing multiple file descriptros efficiently: no"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - netnsid-based network retrieval: yes"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - pidfds: yes"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - uevent injection: yes"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - seccomp listener: yes"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - seccomp listener continue syscalls: yes"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - seccomp listener add file descriptors: no"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - safe native terminal allocation : no"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - unprivileged file capabilities: yes"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - cgroup layout: hybrid"
t=2020-09-28T15:50:16+0000 lvl=warn msg=" - Couldn’t find the CGroup blkio.weight, I/O weight limits will be ignored"
t=2020-09-28T15:50:16+0000 lvl=warn msg=" - Couldn’t find the CGroup memory swap accounting, swap limits will be ignored"
t=2020-09-28T15:50:16+0000 lvl=info msg=" - shiftfs support: disabled"
t=2020-09-28T15:50:16+0000 lvl=info msg=“Initializing local database”
t=2020-09-28T15:50:16+0000 lvl=eror msg=“Failed to start the daemon: Failed to start dqlite server: raft_start(): io: closed segment 0000000000158009-0000000000158009 is past last snapshot snapshot-1-157696-82723112”
t=2020-09-28T15:50:16+0000 lvl=info msg=“Starting shutdown sequence”
root@lxd0x:/var/snap/lxd/common/lxd/database/global# ls
0000000000149454-0000000000151012 0000000000157993-0000000000157993 0000000000157999-0000000000157999 db.bin-wal
0000000000151013-0000000000152864 0000000000157994-0000000000157994 0000000000158000-0000000000158000 metadata1
0000000000152865-0000000000154854 0000000000157995-0000000000157995 0000000000158001-0000000000158001 snapshot-1-156672-72574663
0000000000154855-0000000000156847 0000000000157996-0000000000157996 0000000000158002-0000000000158007 snapshot-1-156672-72574663.meta
0000000000156848-0000000000157991 0000000000157997-0000000000157997 0000000000158009-0000000000158009 snapshot-1-157696-82723112
0000000000157992-0000000000157992 0000000000157998-0000000000157998 db.bin snapshot-1-157696-82723112.meta
I did ALL!
Remove segment 0000000000158009-0000000000158009 tiwice and then upgrade LXD