LXD 5.21.1 LTS has been released

Yes it’s output of command (but it’s not all, full output too long for this forum ) see here output.log

andrei@quasarapp:~$  sudo ls -lah /var/snap/lxd/common/lxd/database/global
[sudo] password for andrei: 
total 211M
drwxrwxr-x 2 root root 708K Apr 16 19:24 .
drwx------ 4 root root 4.0K Apr 15 20:37 ..

-rw------- 1 root root  17K Apr 15 20:22 0000000000181895-0000000000181895
-rw------- 1 root root  17K Apr 15 20:22 0000000000181896-0000000000181896
-rw------- 1 root root  17K Apr 15 20:23 0000000000181897-0000000000181897
-rw------- 1 root root  17K Apr 15 20:23 0000000000181898-0000000000181898
-rw------- 1 root root  17K Apr 15 20:23 0000000000181899-0000000000181899
-rw------- 1 root root  17K Apr 15 20:23 0000000000181900-0000000000181900
-rw------- 1 root root  17K Apr 15 20:23 0000000000181901-0000000000181901
-rw------- 1 root root  17K Apr 15 20:23 0000000000181902-0000000000181902
-rw------- 1 root root  17K Apr 15 20:23 0000000000181903-0000000000181903
-rw------- 1 root root  17K Apr 15 20:23 0000000000181904-0000000000181904
-rw------- 1 root root  17K Apr 15 20:23 0000000000181905-0000000000181905
-rw------- 1 root root  17K Apr 15 20:23 0000000000181906-0000000000181906
-rw------- 1 root root  17K Apr 15 20:23 0000000000181907-0000000000181907
-rw------- 1 root root  17K Apr 15 20:24 0000000000181908-0000000000181908
-rw------- 1 root root  17K Apr 15 20:24 0000000000181909-0000000000181909
-rw------- 1 root root  17K Apr 15 20:24 0000000000181910-0000000000181910
-rw------- 1 root root  17K Apr 15 20:24 0000000000181911-0000000000181911
-rw------- 1 root root  17K Apr 15 20:24 0000000000181912-0000000000181912
-rw------- 1 root root  17K Apr 15 20:24 0000000000181913-0000000000181913
-rw------- 1 root root  17K Apr 15 20:24 0000000000181914-0000000000181914
-rw------- 1 root root  17K Apr 15 20:24 0000000000181915-0000000000181915
-rw------- 1 root root  17K Apr 15 20:24 0000000000181916-0000000000181916
-rw------- 1 root root  17K Apr 15 20:24 0000000000181917-0000000000181917
-rw------- 1 root root  17K Apr 15 20:24 0000000000181918-0000000000181918
-rw------- 1 root root  17K Apr 15 20:24 0000000000181919-0000000000181919
-rw------- 1 root root  17K Apr 15 20:25 0000000000181920-0000000000181920
-rw------- 1 root root  17K Apr 15 20:25 0000000000181921-0000000000181921
-rw------- 1 root root  17K Apr 15 20:25 0000000000181922-0000000000181922
-rw------- 1 root root  17K Apr 15 20:25 0000000000181923-0000000000181923
-rw------- 1 root root  17K Apr 15 20:25 0000000000181924-0000000000181924
-rw------- 1 root root  17K Apr 15 20:25 0000000000181925-0000000000181925
-rw------- 1 root root  17K Apr 15 20:25 0000000000181926-0000000000181926
-rw------- 1 root root  17K Apr 15 20:25 0000000000181927-0000000000181927
-rw------- 1 root root  17K Apr 15 20:25 0000000000181928-0000000000181928
-rw------- 1 root root  17K Apr 15 20:25 0000000000181929-0000000000181929
-rw------- 1 root root  17K Apr 15 20:25 0000000000181930-0000000000181930
-rw------- 1 root root  17K Apr 15 20:25 0000000000181931-0000000000181931
-rw------- 1 root root  17K Apr 15 20:26 0000000000181932-0000000000181932
-rw------- 1 root root  17K Apr 15 20:26 0000000000181933-0000000000181933
-rw------- 1 root root  17K Apr 15 20:26 0000000000181934-0000000000181934
-rw------- 1 root root  17K Apr 15 20:26 0000000000181935-0000000000181935
-rw------- 1 root root  17K Apr 15 20:26 0000000000181936-0000000000181936
-rw------- 1 root root  17K Apr 15 20:26 0000000000181937-0000000000181937
-rw------- 1 root root  17K Apr 15 20:26 0000000000181938-0000000000181938
-rw------- 1 root root  17K Apr 15 20:26 0000000000181939-0000000000181939
-rw------- 1 root root  17K Apr 15 20:26 0000000000181940-0000000000181942
-rw------- 1 root root  17K Apr 15 20:26 0000000000181943-0000000000181943
-rw------- 1 root root  17K Apr 15 20:26 0000000000181944-0000000000181944
-rw------- 1 root root  17K Apr 15 20:26 0000000000181945-0000000000181945
-rw------- 1 root root  17K Apr 15 20:26 0000000000181946-0000000000181946
-rw------- 1 root root  17K Apr 15 20:27 0000000000181947-0000000000181947
-rw------- 1 root root  17K Apr 15 20:27 0000000000181948-0000000000181948
-rw------- 1 root root  17K Apr 15 20:27 0000000000181949-0000000000181949
-rw------- 1 root root  17K Apr 15 20:27 0000000000181950-0000000000181950
-rw------- 1 root root  17K Apr 15 20:27 0000000000181951-0000000000181951
-rw------- 1 root root  17K Apr 15 20:27 0000000000181952-0000000000181952
-rw------- 1 root root  17K Apr 15 20:27 0000000000181953-0000000000181953
-rw------- 1 root root  17K Apr 15 20:27 0000000000181954-0000000000181954
-rw------- 1 root root  17K Apr 15 20:27 0000000000181955-0000000000181955
-rw------- 1 root root  17K Apr 15 20:27 0000000000181956-0000000000181956
-rw------- 1 root root  17K Apr 15 20:27 0000000000181957-0000000000181957
-rw------- 1 root root  17K Apr 15 20:28 0000000000181958-0000000000181958
-rw------- 1 root root  17K Apr 15 20:28 0000000000181959-0000000000181959
-rw------- 1 root root  17K Apr 15 20:28 0000000000181960-0000000000181960
-rw------- 1 root root  17K Apr 15 20:28 0000000000181961-0000000000181961
-rw------- 1 root root  17K Apr 15 20:28 0000000000181962-0000000000181962
-rw------- 1 root root  17K Apr 15 20:28 0000000000181963-0000000000181963
-rw------- 1 root root  17K Apr 15 20:28 0000000000181964-0000000000181964
-rw------- 1 root root  17K Apr 15 20:28 0000000000181965-0000000000181965
-rw------- 1 root root  17K Apr 15 20:28 0000000000181966-0000000000181966
-rw------- 1 root root  17K Apr 15 20:28 0000000000181967-0000000000181967
-rw------- 1 root root  17K Apr 15 20:29 0000000000181968-0000000000181968
-rw------- 1 root root  17K Apr 15 20:29 0000000000181969-0000000000181969
-rw------- 1 root root  17K Apr 15 20:29 0000000000181970-0000000000181970
-rw------- 1 root root  17K Apr 15 20:29 0000000000181971-0000000000181971
-rw------- 1 root root  17K Apr 15 20:29 0000000000181972-0000000000181972
-rw------- 1 root root  17K Apr 15 20:29 0000000000181973-0000000000181973
-rw------- 1 root root  17K Apr 15 20:29 0000000000181974-0000000000181974
-rw------- 1 root root  17K Apr 15 20:29 0000000000181975-0000000000181975
-rw------- 1 root root  17K Apr 15 20:29 0000000000181976-0000000000181976
-rw------- 1 root root  17K Apr 15 20:29 0000000000181977-0000000000181977
-rw------- 1 root root  17K Apr 15 20:29 0000000000181978-0000000000181978
-rw------- 1 root root  17K Apr 15 20:30 0000000000181979-0000000000181979
-rw------- 1 root root  17K Apr 15 20:30 0000000000181980-0000000000181980
-rw------- 1 root root  17K Apr 15 20:30 0000000000181981-0000000000181981
-rw------- 1 root root  17K Apr 15 20:30 0000000000181982-0000000000181982
-rw------- 1 root root  17K Apr 15 20:30 0000000000181983-0000000000181983
-rw------- 1 root root  17K Apr 15 20:30 0000000000181984-0000000000181984
-rw------- 1 root root  17K Apr 15 20:30 0000000000181985-0000000000181985
-rw------- 1 root root  17K Apr 15 20:30 0000000000181986-0000000000181986
-rw------- 1 root root  17K Apr 15 20:30 0000000000181987-0000000000181987
-rw------- 1 root root  17K Apr 15 20:30 0000000000181988-0000000000181988
-rw------- 1 root root  17K Apr 15 20:30 0000000000181989-0000000000181989
-rw------- 1 root root  17K Apr 15 20:31 0000000000181990-0000000000181990
-rw------- 1 root root  17K Apr 15 20:31 0000000000181991-0000000000181991
-rw------- 1 root root  17K Apr 15 20:31 0000000000181992-0000000000181992
-rw------- 1 root root  17K Apr 15 20:31 0000000000181993-0000000000181993
-rw------- 1 root root  17K Apr 15 20:31 0000000000181994-0000000000181994
-rw------- 1 root root  17K Apr 15 20:31 0000000000181995-0000000000181995
-rw------- 1 root root  17K Apr 15 20:31 0000000000181996-0000000000181996
-rw------- 1 root root  17K Apr 15 20:31 0000000000181997-0000000000181997
-rw------- 1 root root  17K Apr 15 20:31 0000000000181998-0000000000181998
-rw------- 1 root root  17K Apr 15 20:31 0000000000181999-0000000000181999
-rw------- 1 root root  17K Apr 15 20:31 0000000000182000-0000000000182000
-rw------- 1 root root  17K Apr 15 20:32 0000000000182001-0000000000182001
-rw------- 1 root root  17K Apr 15 20:32 0000000000182002-0000000000182002
-rw------- 1 root root  17K Apr 15 20:32 0000000000182003-0000000000182003
-rw------- 1 root root  17K Apr 15 20:32 0000000000182004-0000000000182004
-rw------- 1 root root  17K Apr 15 20:32 0000000000182005-0000000000182005
-rw------- 1 root root  17K Apr 15 20:32 0000000000182006-0000000000182006
-rw------- 1 root root  17K Apr 15 20:32 0000000000182007-0000000000182007
-rw------- 1 root root  17K Apr 15 20:32 0000000000182008-0000000000182008
-rw------- 1 root root  17K Apr 15 20:32 0000000000182009-0000000000182009
-rw------- 1 root root  17K Apr 15 20:32 0000000000182010-0000000000182010
-rw------- 1 root root  17K Apr 15 20:32 0000000000182011-0000000000182011
-rw------- 1 root root  17K Apr 15 20:32 0000000000182012-0000000000182012
-rw------- 1 root root  17K Apr 15 20:33 0000000000182013-0000000000182013
-rw------- 1 root root  17K Apr 15 20:33 0000000000182014-0000000000182014
-rw------- 1 root root  17K Apr 15 20:33 0000000000182015-0000000000182015
-rw------- 1 root root  17K Apr 15 20:33 0000000000182016-0000000000182016
-rw------- 1 root root  17K Apr 15 20:33 0000000000182017-0000000000182017
-rw------- 1 root root  17K Apr 15 20:33 0000000000182018-0000000000182018
-rw------- 1 root root  17K Apr 15 20:33 0000000000182019-0000000000182019
-rw------- 1 root root  17K Apr 15 20:33 0000000000182020-0000000000182020
-rw------- 1 root root  17K Apr 15 20:33 0000000000182021-0000000000182021
-rw------- 1 root root  17K Apr 15 20:33 0000000000182022-0000000000182022
-rw------- 1 root root  17K Apr 15 20:33 0000000000182023-0000000000182023
-rw------- 1 root root  17K Apr 15 20:33 0000000000182024-0000000000182024
-rw------- 1 root root  17K Apr 15 20:34 0000000000182025-0000000000182025
-rw------- 1 root root  17K Apr 15 20:34 0000000000182026-0000000000182026
-rw------- 1 root root  17K Apr 15 20:34 0000000000182027-0000000000182027
-rw------- 1 root root  17K Apr 15 20:34 0000000000182028-0000000000182028
-rw------- 1 root root  17K Apr 15 20:34 0000000000182029-0000000000182029
-rw------- 1 root root  17K Apr 15 20:34 0000000000182030-0000000000182030
-rw------- 1 root root  17K Apr 15 20:34 0000000000182031-0000000000182031
-rw------- 1 root root  17K Apr 15 20:34 0000000000182032-0000000000182032
-rw------- 1 root root  17K Apr 15 20:34 0000000000182033-0000000000182033
-rw------- 1 root root  17K Apr 15 20:34 0000000000182034-0000000000182034
-rw------- 1 root root  17K Apr 15 20:34 0000000000182035-0000000000182035
-rw------- 1 root root  17K Apr 15 20:35 0000000000182036-0000000000182036
-rw------- 1 root root  17K Apr 15 20:37 0000000000182037-0000000000182037
-rw------- 1 root root  17K Apr 15 20:37 0000000000182038-0000000000182038
-rw------- 1 root root  17K Apr 15 20:37 0000000000182039-0000000000182039
-rw------- 1 root root  17K Apr 15 20:37 0000000000182040-0000000000182040
-rw------- 1 root root  17K Apr 15 20:37 0000000000182041-0000000000182041
-rw------- 1 root root  17K Apr 15 20:37 0000000000182042-0000000000182042
-rw------- 1 root root  17K Apr 15 20:37 0000000000182043-0000000000182043
-rw------- 1 root root  17K Apr 15 20:37 0000000000182044-0000000000182044
-rw------- 1 root root 1.1M Apr 16 18:24 0000000000182044-0000000000182065
-rw------- 1 root root 260K Apr 15 20:37 0000000000182045-0000000000182056
-rwxrwxr-x 1 root root 964K Apr 16 19:19 db.bin
-rwxrwxr-x 1 root root   32 Dec 21  2020 metadata1
-rw------- 1 root root 114K Apr 15 18:17 snapshot-1-180224-10496039203
-rw------- 1 root root   56 Apr 15 18:17 snapshot-1-180224-10496039203.meta
-rw------- 1 root root 132K Apr 15 19:36 snapshot-1-181248-10500816582
-rw------- 1 root root   56 Apr 15 19:36 snapshot-1-181248-10500816582.meta

1 Like

In fact, I don’t know what could be wrong here, unfortunately it just stopped working.
Updating the kernel and the distribution to 22.04 did not help

What does snap info lxd show?

Sounds like you have db corruption somehow.

Did you refresh to 5.21/stable or latest/stable?

You should refresh to 5.21/stable to get zfs 0.8 support.

Yes, I refresh all.
*snap LXd
*Distribution (now is 22.04)

andrei@quasarapp:~$ snap info lxd 
name:      lxd
summary:   LXD - container and VM manager
publisher: Canonical✓
store-url: https://snapcraft.io/lxd
contact:   https://github.com/canonical/lxd/issues
license:   AGPL-3.0
description: |
  LXD is a system container and virtual machine manager.
  
  It offers a simple CLI and REST API to manage local or remote instances,
  uses an image based workflow and support for a variety of advanced
  features.
  
  Images are available for all Ubuntu releases and architectures as well
  as for a wide number of other Linux distributions. Existing
  integrations with many deployment and operation tools, makes it work
  just like a public cloud, except everything is under your control.
  
  LXD containers are lightweight, secure by default and a great
  alternative to virtual machines when running Linux on Linux.
  
  LXD virtual machines are modern and secure, using UEFI and secure-boot
  by default and a great choice when a different kernel or operating
  system is needed.
  
  With clustering, up to 50 LXD servers can be easily joined and managed
  together with the same tools and APIs and without needing any external
  dependencies.
  
  
  Supported configuration options for the snap (snap set lxd
  [<key>=<value>...]):
  
    - ceph.builtin: Use snap-specific Ceph configuration [default=false]
    - ceph.external: Use the system's ceph tools (ignores ceph.builtin)
    [default=false]
    - criu.enable: Enable experimental live-migration support [default=false]
    - daemon.debug: Increase logging to debug level [default=false]
    - daemon.group: Set group of users that have full control over LXD
    [default=lxd]
    - daemon.user.group: Set group of users that have restricted LXD access
    [default=lxd]
    - daemon.preseed: Pass a YAML configuration to `lxd init` on initial
    start
    - daemon.syslog: Send LXD log events to syslog [default=false]
    - daemon.verbose: Increase logging to verbose level [default=false]
    - lvm.external: Use the system's LVM tools [default=false]
    - 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]
    - lxcfs.debug: Increase logging to debug level [default=false]
    - openvswitch.builtin: Run a snap-specific OVS daemon [default=false]
    - openvswitch.external: Use the system's OVS tools (ignores
    openvswitch.builtin) [default=false]
    - ovn.builtin: Use snap-specific OVN configuration [default=false]
    - ui.enable: Enable the web interface [default=false]
  
  For system-wide configuration of the CLI, place your configuration in
  /var/snap/lxd/common/global-conf/ (config.yml and servercerts)
commands:
  - lxd.buginfo
  - lxd.check-kernel
  - lxd.lxc
  - lxd
services:
  lxd.activate:    oneshot, disabled, inactive
  lxd.daemon:      simple, disabled, inactive
  lxd.user-daemon: simple, disabled, inactive
snap-id:      J60k4JY0HppjwOjW8dZdYc8obXKxujRu
tracking:     latest/stable
refresh-date: today at 19:33 UTC
channels:
  5.21/stable:      5.21.1-f9da96a 2024-04-16 (28269) 108MB -
  5.21/candidate:   5.21.1-f9da96a 2024-04-16 (28269) 108MB -
  5.21/beta:        ↑                                       
  5.21/edge:        git-79d3327    2024-04-16 (28270) 108MB -
  latest/stable:    5.21.1-43998c6 2024-04-11 (28155) 107MB -
  latest/candidate: 5.21.1-2c1a323 2024-04-16 (28263) 107MB -
  latest/beta:      ↑                                       
  latest/edge:      git-eb94ad4    2024-04-16 (28289) 107MB -
  5.20/stable:      5.20-f3dd836   2024-02-09 (27049) 155MB -
  5.20/candidate:   ↑                                       
  5.20/beta:        ↑                                       
  5.20/edge:        ↑                                       
  5.19/stable:      5.19-8635f82   2024-01-29 (26200) 159MB -
  5.19/candidate:   ↑                                       
  5.19/beta:        ↑                                       
  5.19/edge:        ↑                                       
  5.0/stable:       5.0.3-babaaf8  2024-03-26 (27948)  91MB -
  5.0/candidate:    5.0.3-babaaf8  2024-03-22 (27948)  91MB -
  5.0/beta:         ↑                                       
  5.0/edge:         git-11f6228    2024-04-08 (28110) 117MB -
  4.0/stable:       4.0.9-a29c6f1  2022-12-04 (24061)  96MB -
  4.0/candidate:    4.0.9-a29c6f1  2022-12-02 (24061)  96MB -
  4.0/beta:         ↑                                       
  4.0/edge:         git-407205d    2022-11-22 (23988)  96MB -
  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 -
installed:          5.21.1-43998c6            (28155) 107MB -

fresh log available here

This is very strange, because apart from this advice I did nothing.

How I can restore my containers ? It’s very important for me.

You’re still on the wrong snap channel that doesn’t have zfs 0.8 support .

I’m pretty confused now as you are apparently not on an os that is affected by lack of zfs 0.8 support and you have been applying custom database patches so I can’t reason about the state of your db.

Suggest restoring from your last backup or @colemiller from the dqlite team maybe able to help you fix the db corruption.

1 Like

The error message that mentions closed segments is a dqlite thing. These are the problematic files in that list:

-rw------- 1 root root  17K Apr 15 20:37 0000000000182044-0000000000182044
-rw------- 1 root root 1.1M Apr 16 18:24 0000000000182044-0000000000182065
-rw------- 1 root root 260K Apr 15 20:37 0000000000182045-0000000000182056

There’s some overlap between the ranges here which should never happen and indicates a dqlite bug. To get back to a working cluster you should most likely remove either both of these two files (option A)

0000000000182044-0000000000182044
0000000000182045-0000000000182056

or this single file (option B)

0000000000182044-0000000000182065

I would suggest trying it both ways, after backing up all three files, and seeing in each case whether (1) the node starts successfully and (2) the cluster has all the state you expect (to the extent that you can tell). My instinct is that option A is going to be the way to go because it results in a higher index, but since I don’t know the nature of what went wrong here I can’t say for certain.

Edit: to me this suggests that dqlite started up at some point and didn’t notice the trailing segments or segments.

2 Likes

Yes!!!, works. its really corrupted database !

Thank you very much ) You saved my life)

2 Likes

Thanks @colemiller !

2 Likes

ZFS 0.8 support is now included in the 5.21/stable channel for all architectures.

1 Like

I do have the same issue.
Running lxd 5.2.1 on Bionic. I already upgraded to HWE kernel

uname -r
5.4.0-150-generic
snap list --all lxd core20 core22 core24 snapd
Name    Version         Rev    Tracking       Publisher   Notes
core20  20240111        2182   latest/stable  canonical✓  base,disabled
core20  20240227        2264   latest/stable  canonical✓  base
core22  20231123        1033   latest/stable  canonical✓  base,disabled
core22  20240111        1122   latest/stable  canonical✓  base
lxd     5.21.1-10f4115  28322  5.21/stable    canonical✓  disabled
lxd     5.21.1-98dad8f  28323  5.21/stable    canonical✓  -
snapd   2.61.2          21184  latest/stable  canonical✓  snapd,disabled
snapd   2.62            21465  latest/stable  canonical✓  snapd

I can’t get the container to start:

Apr 20 08:11:28 bionic lxd.daemon[1850]: Error: Failed to initialize global database: failed to ensure schema: Failed to ensure schema: not an error
Apr 20 08:11:29 bionic lxd.daemon[1850]: Killed
Apr 20 08:11:29 bionic lxd.daemon[1850]: => LXD failed to start
Apr 20 08:11:29 bionic systemd[1]: snap.lxd.daemon.service: Main process exited, code=exited, status=1/FAILURE
Apr 20 08:11:29 bionic systemd[1]: snap.lxd.daemon.service: Failed with result 'exit-code'.

Please advise how to restore the containers…I’m pretty lost

So this particular “not an error” error is coming from dqlite and has been reported to the dqlite team via @colemiller to investigate.

We’ve not seen this one in our own testing, so seems to be related to support for direct I/O on the hosts root filesystem.

What filesystem are you using for your host?
So far we’ve only seen reports of it occurring on btrfs on the bionic 4.15 kernel. But now we know its affecting bionic hwe 5.4 too.

See also https://github.com/canonical/lxd/issues/13326

As it doesn’t appear that the schema changes have been applied you could try switching to the 5.20/stable channel using:

sudo snap refresh lxd --channel=5.20/stable

Alternatively you could also try the steps here LXD 5.21.1 LTS has been released - #24 by lbueno

1 Like

Thanks for your reply.

What filesystem are you using for your host?
BTRFS

As it doesn’t appear that the schema changes have been applied you could try switching to the 5.20/stable channel using:

sudo snap refresh lxd --channel=5.20/stable

You are a life saver, Sir. All containers are back online again.
Thank you so much

1 Like

Ah great good to hear. Keep in mind that channel is frozen so doesn’t get updates. I would recommend looking into switching to a newer Ubuntu version asap.

We are going to work with dqlite team to try and figure out what’s going on here though.

Do you use btrfs on the host?

Yes, its btrfs

Ah great good to hear. Keep in mind that channel is frozen so doesn’t get updates. I would recommend looking into switching to a newer Ubuntu version asap.

I’ll upgrade to 20.04 LTE as soon as possible. Thanks again

1 Like

Hi, for anyone who’s seeing this:

Error: Failed to initialize global database: failed to ensure schema: Failed to ensure schema: not an error

you can help me figure out what’s going on by doing the following:

  • make a copy of /snap/lxd/current/commands/daemon.start that you can edit
  • edit your copy to add export LIBDQLITE_TRACE=1 in the indicated place:
# Spawn LXD
(
    read -r sbpid _ < /proc/self/stat
    export LISTEN_PID="${sbpid}"
    export LIBDQLITE_TRACE=1 # right here

    # shellcheck disable=SC2086
    exec ${CMD}
)&
  • $ sudo mount -o ro,bind daemon.start /snap/lxd/current/commands/daemon.start && sudo snap restart lxd

Hopefully LXD fails to start with the same error message, but there should be a lot of lines with LIBDQLITE around it now in the journalctl log – sharing that log should give me more context for what’s going on. Thanks!

1 Like

Interestingly it seems lxd 5.20 isn’t affected, and so far its only bionic on btrfs affected with lxd 5.21.1

So seems something in a recent version of dqlite has introduced this issue perhaps.