lxd unix socket not accessible reliably

[James Page]

The LXD unix socket does not appear to be reliably present:

root@juju-devel3-machine-23:/var/lib/lxd# lxc list
+------+-------+------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
+------+-------+------+------+-----------+-----------+
+------+-------+------+------+-----------+-----------+
root@juju-devel3-machine-23:/var/lib/lxd# sudo service lxd restart
root@juju-devel3-machine-23:/var/lib/lxd# lxc list
error: Get http://unix.socket/1.0/containers?recursion=1: dial unix ///var/lib/lxd/unix.socket: connect: no such file or directory
root@juju-devel3-machine-23:/var/lib/lxd# lxc list
error: Get http://unix.socket/1.0/containers?recursion=1: dial unix ///var/lib/lxd/unix.socket: connect: no such file or directory
root@juju-devel3-machine-23:/var/lib/lxd# lxc list
error: Get http://unix.socket/1.0/containers?recursion=1: dial unix ///var/lib/lxd/unix.socket: connect: no such file or directory
root@juju-devel3-machine-23:/var/lib/lxd# ls -l
total 68
drwxr-xr-x 2 root root 4096 Sep 9 10:23 containers
drwxr-xr-x 2 root root 4096 Sep 9 10:42 devlxd
drwx------ 2 root root 4096 Sep 9 10:23 images
-rw-r--r-- 1 root root 38912 Sep 9 10:26 lxd.db
-rw-r--r-- 1 root root 2061 Sep 9 10:23 server.crt
-rw------- 1 root root 3243 Sep 9 10:23 server.key
drwx------ 2 root root 4096 Sep 9 10:23 snapshots

a few stop/start's later, and I can access using lxc again.

when I'm not able to access LXD, systemd is reporting that the lxd unix socket is not active - so maybe something todo with socket activation?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lxd 0.17-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18-0ubuntu9
Architecture: amd64
Date: Wed Sep 9 10:40:12 2015
Ec2AMI: ami-00000551
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.medium
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
SourcePackage: lxd
UpgradeStatus: No upgrade log present (probably fresh install)

[Stéphane Graber (stgraber)]

This has been resolved with 0.18