I’m new here and this is my first post on this forum.
I’m a first year student in computer science and i recently setup for the first time a LXD environnement in the enterprise when i work.
In fact this environnement serve to host somes sites in production.
Explanation of my problem :
In first, i had not a problem before, all working fine but recently, an error appear suddently without me touching anything when i use lxc command (for exemple
This is this error :
Error: Get "http://unix.socket/1.0": EOF
Of course, i have searched for a solution on the forums but I am afraid that some solutions turn off my LXD service without me being able to restart and thus make the production sites inaccessible.
Concretely, i would like to correct this error while being sure not to stop my LXD service.
I have tried this manipulation :
lxd --debug --group lxd
2 errors observed :
Failed to start the daemon: Failed initializing storage pool “default”: Failed to mount “/dev/loop0” on “/var/snap/lxd/common/lxd/storage-pools/default” using “btrfs”: file exists
Error: Failed initializing storage pool “default”: Failed to mount “/dev/loop0” on “/var/snap/lxd/common/lxd/storage-pools/default” using “btrfs”: file exists
From memory i had this new error :
Error: Get http://unix.socket/1.0: dial unix /var/snap/lxd/common/lxd/unix.socket: connect: no such file or directory
After that I went to
/var/snap/lxd/common/lxd and the file
unix.socket was not here. (why ?)
I decided to create this file manualy and after that a new error appear :
Error: Get "http://unix.socket/1.0": dial unix /var/snap/lxd/common/lxd/unix.socket: connect: connection refused
The next day the file mysteriously disappeared by itself but this last error remains the same.
I see this topic but i’m not sure if this the correct way to fix this : Best way to solve unproper mounting issue in LXD (snap related) - #9 by Kcold
Since i don’t know the cause of the problem, i don’t know how to reproduce it in another environment and thus test different manipulations without being afraid to break everything.
I was thinking of restarting snap.lxd.daemon.unix.socket and see what happens but as i said I want to be sure not to stop the LXD service.
To conclude, I would like to have clarifications on the reason of my problem, how to avoid its recurrence and how to solve it without fearing to make the production sites inaccessible.
I rarely post problems on forums but here i have to find my problem as soon as possible (urgent) because i use lxd/lxc commands obviously to manage containers but also to backup them.
This is important for me because i am in a company and this problem is really blocking.
I hope someone can help me because I am still a novice and i have no one who can help me now.
Thanks in advance !
PS : sorry if my english is bad, this is not my first langage.
lxd 4.17 (snap)