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. You're not running low on memory or something like that are you? In any case, dmesg would help check for that as well. ** Changed in: lxd (Ubuntu) Status: Confirmed => Incomplete -- 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 to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1660948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs