Error: Get "http://unix.socket/1.0": dial unix /var/snap/lxd/common/lxd/unix.socket: connect: resource temporarily unavailable

LXD
1

Hi,
I suppose that I have recently changed one of my cluster node config like that, ```lxc config set core.metrics_address “<Wrong_IP_Adress>:3456”. Now I get the following error.

Oct 03 23:07:20 pinehost1 lxd.daemon[28620]: => Starting LXD
Oct 03 23:07:20 pinehost1 lxd.daemon[28620]: t=2021-10-03T23:07:20+0300 lvl=warn msg=" - Couldn't find the CGroup blkio.weight, disk priority will be ignored"
Oct 03 23:07:20 pinehost1 lxd.daemon[28620]: t=2021-10-03T23:07:20+0300 lvl=warn msg="Instance type not operational" driver=qemu err="KVM support is missing" type=virtual-machine
Oct 03 23:07:21 pinehost1 lxd.daemon[28620]: t=2021-10-03T23:07:21+0300 lvl=eror msg="Failed to start the daemon" err="Bind network address: listen tcp 192.168.1.5:3456: bind: cannot assign requested address"
Oct 03 23:07:22 pinehost1 lxd.daemon[28620]: Error: Bind network address: listen tcp 192.168.1.5:3456: bind: cannot assign requested address
Oct 03 23:07:22 pinehost1 lxd.daemon[28620]: => LXD failed to start
Oct 03 23:07:22 pinehost1 systemd[1]: snap.lxd.daemon.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 23:07:22 pinehost1 systemd[1]: snap.lxd.daemon.service: Failed with result 'exit-code'.
Oct 03 23:07:23 pinehost1 systemd[1]: snap.lxd.daemon.service: Service RestartSec=100ms expired, scheduling restart.
Oct 03 23:07:23 pinehost1 systemd[1]: snap.lxd.daemon.service: Scheduled restart job, restart counter is at 568.
Oct 03 23:07:23 pinehost1 systemd[1]: Stopped Service for snap application lxd.daemon.
Oct 03 23:07:23 pinehost1 systemd[1]: Started Service for snap application lxd.daemon.

Can someone enlighten me that where can I find that parameter in the sqlite database?
Thanks.

2

The easiest and cleanest way out of this is with ip -4 addr add dev lo 192.168.1.5/32

Which basically adds that IP address to your loopback device, LXD can then bind it and after that you can reconfigure it.

It’s also possible to sort this through database surgery, but in this case, it’s just easier to have the address temporarily exist.

3

Thanks @stgraber for the tip.