[Expired for lxd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660948
Can you include the "dmesg" output from right after such a failure?
Your LXD log doesn't show anything to match your client's behavior, but
your systemd log does seem to indicate lxd dying and being respawned
through socket activation, only to fail again causing the client error
you're seeing.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660948
Title:
juju
This is lxd.log as requested.
I have to mention, that I had this situation several times in the past, not
beeing able to recover...
this time (about 1 hour later than I reported this bug) the lxc list command
returned expected results, so it seemed to have recovered without additional
What's in /var/lib/lxd/lxd.log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660948
Title:
juju deployed openstack: after lxd restart "lxc list" hangs
To manage notifications about this bug go
attaching apport data. please let me know what else info is needed.
** Attachment added: "apport data for lxd component"
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1660948/+attachment/4811691/+files/bug.apport
--
You received this bug notification because you are a member of Ubuntu
