Start-Date: 2018-04-03  22:22:21
Commandline: apt full-upgrade
Requested-By: xnox (1000)
...
lxc:amd64 (3.0.0~beta3-0ubuntu1, 3.0.0-0ubuntu2), lxd:amd64 
(3.0.0~beta5-0ubuntu2, 3.0.0-0ubuntu1),
...
Meanwhile
> Apr 04 09:45:04 sochi lxd[27714]: Error: failed to open
> cluster database: failed to ensure schema: failed to begin
> transaction: gRPC BEGIN response error: rpc error: code =
> Unknown desc = failed to handle BEGIN request: FSM out of
> sync: timed out enqueuing operation
...
End-Date: 2018-04-04  09:50:09

Meaning it kind was stuck, and I guess i had to kill things, like lxd
possibly since at about this time.

And I guess i tried to upgrade again, straight after because I also
have:

Start-Date: 2018-04-04  09:52:08
Commandline: apt full-upgrade
Requested-By: xnox (1000)
...
lxd:amd64 (3.0.0-0ubuntu1, 3.0.0-0ubuntu2)
...
Apr 04 09:57:43 sochi lxd[15068]: Error: failed to open cluster database: 
failed to ensure schema: failed to begin transaction: gRPC BEGIN response 
error: rpc error: code = Unknown desc = failed to handle BEGIN request: FSM out 
of sync: timed out enqueuing operation
...
End-Date: 2018-04-04  10:07:02

And many more "failed to open cluster database" since. Like a few on the
Apr 20.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765699

Title:
  lxd fails to start main process, yet waitready doesn't bail out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1765699/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to