[lxc-users] Error: failed to begin transaction: database is locked

[Fajar A. Nugraha]

On Wed, Sep 12, 2018 at 9:33 PM, Kees Bakker <keesb at ghs.com> wrote:

> Hey,
>
> This with a LXD/LXC on a Ubuntu 18.04 server. Storage is done
> with LVM. It was installed as a cluster with just one node.
> It was also added as remote for three other LXD servers (all Ubuntu 16.04
> and LXD 2.0.x). These old servers have BTRFS storage.
>
>
Only added as remote? not lxd clustering (
https://lxd.readthedocs.io/en/latest/clustering/)?



> Suddenly I cannot do any lxc command anymore. They all give
>
>     Error: failed to begin transaction: database is locked
>
> In /var/log/lxd/lxd.log it prints the following message every 10 seconds
>
>     lvl=warn msg="Failed to get current raft nodes: failed to fetch raft
> server address: failed to begin transaction: database is locked"
> t=2018-09-12T16:28:44+0200
>
> Extra information. This afternoon I have upgraded one of the "old" servers
> to LXD 3.0 (from xenial-backports). This was triggered by the problems we
> have with a container in ERROR state and a kworker at 100% cpu load.
>


Do package versions on upgraded servers match? i.e. all lxd, liblxc1, etc
all 3.0 from xenial-backports, without any 2.x or ppa packages mixed in?

Have you restart lxd on the upgraded server?

If you temporarily move ~/.config/lxc somehere else (to "remove" all the
remotes, among other things), does lxc command work?

-- 
Fajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20180913/60e55fcc/attachment.html>