Big sur showing list failed: cannot connect to the multipass socket Please ensure multipassd is running and '/var/run/multipass_socket' is accessible #1983
Comments
|
@dmuiX if you forcefully shut it down, there's a chance our data storage got corrupted. Can you please share the contents of your |
|
Thanks for responding so fast :) |
What is the correct way to shut multipass down if something is wrong or not responding? |
|
This should do: But it may well result in the same problem, if multipassd got stuck somehow. I can see in the log why it never came up again: Can you please share the contents of Unfortunately I can't see what went wrong in the first place… Everything seems ok right up to the above errors, at which point I imagine you killed it. |
{
"ubuntu": {
"deleted": false,
"disk_space": "0",
"extra_interfaces": [
],
"mac_addr": "",
"mem_size": "0",
"metadata": {
},
"mounts": [
],
"num_cores": 0,
"ssh_username": "",
"state": 2
},
"ubuntuVM": {
"deleted": false,
"disk_space": "5368709120",
"extra_interfaces": [
],
"mac_addr": "52:54:00:19:23:bc",
"mem_size": "1073741824",
"metadata": {
},
"mounts": [
{
"gid_mappings": [
{
"host_gid": 20,
"instance_gid": -1
}
],
"source_path": "/Volumes/Data/Computerspende/computerspende",
"target_path": "~/computerspende",
"uid_mappings": [
{
"host_uid": 501,
"instance_uid": -1
}
]
},
{
"gid_mappings": [
{
"host_gid": 20,
"instance_gid": -1
}
],
"source_path": "/Volumes/Data/Computerspende/computerspende",
"target_path": "/Volumes/Data/Computerspende/computerspende",
"uid_mappings": [
{
"host_uid": 501,
"instance_uid": -1
}
]
}
],
"num_cores": 1,
"ssh_username": "ubuntu",
"state": 4
}
}{
"ubuntu": {
"deleted": false,
"disk_space": "0",
"extra_interfaces": [
],
"mac_addr": "",
"mem_size": "0",
"metadata": {
},
"mounts": [
],
"num_cores": 0,
"ssh_username": "",
"state": 2
},
"ubuntuVM": {
"deleted": false,
"disk_space": "5368709120",
"extra_interfaces": [
],
"mac_addr": "52:54:00:19:23:bc",
"mem_size": "1073741824",
"metadata": {
},
"mounts": [
{
"gid_mappings": [
{
"host_gid": 20,
"instance_gid": -1
}
],
"source_path": "/Volumes/Data/Computerspende/computerspende",
"target_path": "~/computerspende",
"uid_mappings": [
{
"host_uid": 501,
"instance_uid": -1
}
]
},
{
"gid_mappings": [
{
"host_gid": 20,
"instance_gid": -1
}
],
"source_path": "/Volumes/Data/Computerspende/computerspende",
"target_path": "/Volumes/Data/Computerspende/computerspende",
"uid_mappings": [
{
"host_uid": 501,
"instance_uid": -1
}
]
}
],
"num_cores": 1,
"ssh_username": "ubuntu",
"state": 4
}
} |
|
Actually I deleted ubuntu and ubuntuTest with multipass delete ubuntu and multipass delete ubuntuTest. Seems like its not showing here. |
|
Everytime I have tried multipass purge so far it ended with taking very long time. And then I stopped it with ctrl+c or last time with the activity thing and then when I ran multipass list it showed the error above. |
|
I remember a detail now: |
|
How is it possible to get more output with these commands? If i try -vvvv nothing changes. |
about the restart => Yeah it ends in the same error again. |
|
OK, to recover, {
"ubuntuVM": {
"deleted": false,
"disk_space": "5368709120",
"extra_interfaces": [
],
"mac_addr": "52:54:00:19:23:bc",
"mem_size": "1073741824",
"metadata": {
},
"mounts": [
{
"gid_mappings": [
{
"host_gid": 20,
"instance_gid": -1
}
],
"source_path": "/Volumes/Data/Computerspende/computerspende",
"target_path": "~/computerspende",
"uid_mappings": [
{
"host_uid": 501,
"instance_uid": -1
}
]
},
{
"gid_mappings": [
{
"host_gid": 20,
"instance_gid": -1
}
],
"source_path": "/Volumes/Data/Computerspende/computerspende",
"target_path": "/Volumes/Data/Computerspende/computerspende",
"uid_mappings": [
{
"host_uid": 501,
"instance_uid": -1
}
]
}
],
"num_cores": 1,
"ssh_username": "ubuntu",
"state": 4
}
}That should bring |
Yes, if it failed to boot properly (or just failed to get IP), that's likely to be the result of that. If you can show me what the cloud init was, I can maybe suggest what's wrong with them. And yes, we're not exactly great dealing with unresponsive VMs… there's a couple issues we have around and we're planning a |
So at the moment its not really possible to shut a not responding vm down properly? Or do you know a way to do it properly? |
And multipass list is working again? |
|
These are the two yaml files. #cloud-config
groups:
- docker
users:
- default
- name: ubuntu
groups: docker
sudo: ALL=(ALL) NOPASSWD:ALL
ssh_authorized_keys:
- ssh-rsa <somekey>
package_upgrade: true
power_state:
mode: reboot
message: Restarting after installing docker & docker-compose
The only difference to the one before is the docker install script. #cloud-config
groups:
- docker
users:
- default
- name: ubuntu
groups: docker
sudo: ALL=(ALL) NOPASSWD:ALL
ssh_authorized_keys:
- ssh-rsa <somekey>
package_upgrade: true
packages:
- apt-transport-https
- ca-certificates
- curl
- gnupg-agent
- software-properties-common
runcmd:
# install docker following the guide: https://docs.docker.com/install/linux/docker-ce/ubuntu/
- curl -sSL https://get.docker.com/ | sh
# install docker-compose following the guide: https://docs.docker.com/compose/install/
- sudo curl -L "https://github.com/docker/compose/releases/download/1.25.4/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
- sudo chmod +x /usr/local/bin/docker-compose
power_state:
mode: reboot
message: Restarting after installing docker & docker-compose |
|
Thanks a lot for helping out :) |
|
Don't know if you need it but here is the output of Name: ubuntuVM
State: Running
IPv4: 192.168.236.11
172.17.0.1
Release: Ubuntu 20.04.2 LTS
Image hash: c5f2f08c6a1a (Ubuntu 20.04 LTS)
Load: 1.21 0.29 0.10
Disk usage: 2.7G out of 4.7G
Memory usage: 195.4M out of 981.4M
Mounts: /Volumes/Data/Computerspende/computerspende => /Volumes/Data/Computerspende/computerspende
UID map: 501:default
GID map: 20:default
/Volumes/Data/Computerspende/computerspende => ~/computerspende
UID map: 501:default
GID map: 20:default |
|
So this is at least part of the problem: users:
- default
- name: ubuntu
ssh_authorized_keys:
- ssh-rsa <somekey>
...We rely on the It'd be safest if you used a custom user instead. |
|
Thats weird. #cloud-config
groups:
- docker
users:
- default
- name: ubuntu
groups: docker
sudo: ALL=(ALL) NOPASSWD:ALL
ssh_authorized_keys:
- ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC1+Ji93zXpPqYjFUVWmNWooqUBwAbc0zUefCZVzP012RXgDQAR2LZtr6t1Yx35/jr4E9oBFvCFHvMBmUpmQEIehLb7RR4ksSdmEEQB3QHqlS0fTmEdnrjg3pgVOuXYKVySGoyiUPaVo5wV/lcyLD2xZQaXWKtu25bn+EaE9Eo58TnvEHiVWyf0avgUXx6xoXpuy0n3VFZ3QXSq1ll7wmEzfxOEIBqDJVkfVGJA9bUdYY05kEq5IZhLMxyyKFgCdYwhDau7HCkBwkhuJoM2RZYNaCoiIU2+hmirYtkvXdz8agiXhzqThYYPJUE2+Ash2sUMoQtWxS7LxkW/7EXKtW/3
package_upgrade: true
packages:
- apt-transport-https
- ca-certificates
- curl
- gnupg-agent
- software-properties-common
runcmd:
# install docker following the guide: https://docs.docker.com/install/linux/docker-ce/ubuntu/
- curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
- sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
- sudo apt-get -y update
- sudo apt-get -y install docker-ce docker-ce-cli containerd.io
- sudo systemctl enable docker
# install docker-compose following the guide: https://docs.docker.com/compose/install/
- sudo curl -L "https://github.com/docker/compose/releases/download/1.25.4/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
- sudo chmod +x /usr/local/bin/docker-compose
power_state:
mode: reboot
message: Restarting after installing docker & docker-composeBut I am runnning another launch with this config again at the moment. Maybe it was just luck :D. Finished and working. I don't understand whats going on here.... |
|
Maybe it has something to do if I start another instance of the same image although the other instance is still running? |
Killing the |
Oh indeed, it concatenates the SSH keys :] |
|
FWIW I just launched with your "full" cloud init, and it launched fine, so it must be some bad luck on those that failed to start… |
so this is the correct way to add ssh-keys? |
Yes, I can't see anything wrong with your cloud-init after all. Well, except for this, but that won't prevent Multipass from working :) |
I am not that lucky now. |
is this output from the vm? how did you get this? |
This is from cloud-init logs at |
|
I just ran this and it worked fine: $ multipass launch --cloud-init - <<EOF
#cloud-config
groups:
- docker
users:
- default
- name: ubuntu
groups: docker
sudo: ALL=(ALL) NOPASSWD:ALL
ssh_authorized_keys:
- ssh-rsa $( cat ~/.ssh/id_rsa.pub )
package_upgrade: true
packages:
- apt-transport-https
- ca-certificates
- curl
- gnupg-agent
- software-properties-common
runcmd:
# install docker following the guide: https://docs.docker.com/install/linux/docker-ce/ubuntu/
- curl -sSL https://get.docker.com/ | sh
# install docker-compose following the guide: https://docs.docker.com/compose/install/
- sudo curl -L "https://github.com/docker/compose/releases/download/1.25.4/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
- sudo chmod +x /usr/local/bin/docker-compose
power_state:
mode: reboot
message: Restarting after installing docker & docker-compose
EOF |
if i try that it says permission denied? although i am root with sudo su? screen tells the same..? |
|
I have now three vms running. all with the three different cloud-init files. None of the is starting correctly...looks like none of them is getting a ip? |
Because it's trying to execute the file rather than connect to it… I could've sworn that worked at some point, but can't get it to, now… Any case, the logs in
What about if you don't provide a You could try clearing I'm going EOD now, will pick it up in the morning if you don't resolve it yourself by then. One last thing, I occasionally see instances as |
Ah, because suddenly they're not symlinks, but rather just contain the name of the TTY device: |
|
okay thanks a lot so far :). I will try again and report what happens. |
About that you are right. I can use the shell although its still starting. If I am in the shell it is showing the ip address. |
This error ocurred one time. Haven't checked the log files at this moment. |
|
I just newly installed multiples via homebrew as bellow and there is an error happening now. |
|
Hi @ChangheeOh, can you please show your |
Here is the json file you want. |
|
@ChangheeOh and you're on Multipass 1.6.2? |
@Saviq, this is the version of multipass I have installed. Do you mean that I can remove the above |
|
@ChangheeOh yes |
I removed |
|
@ChangheeOh oh you're on Apple M1? We don't support it yet, sorry. It's on our list, but it will be some months still. Subscribe yourself to #1857 for news. |
@Saviq |
|
To anyone else with this issue, the workaround is to clear any instances that look like this from {
"deleted": false,
"disk_space": "0",
"extra_interfaces": [
],
"mac_addr": "",
"mem_size": "0",
"metadata": {
},
"mounts": [
],
"num_cores": 0,
"ssh_username": "",
"state": 2
}We'll follow up with a bugfix release. |
I also encountered the problem |
it happened in multipass 1.6.2+mac |
|
The issue still persists on 1.6.2 version. |
|
@Saviq Would you pls tell me how to fix it pls? |
fix my problem on macOS Monterey |
|
[error] [daemon] Caught an unhandled exception: Internal error: qemu-img failed (Process returned exit code: 1) with output: please help , what should i do ? |
|
just run command |
|
Hi I uninstalled multipass 1.11, and used brew install multipass to get 1.12 on Ventura. Now I have the same problem. Looking down this thread, I have tried: On the restart, I note that To confirm: I'm going to have to back out of 1.12 and try and download 1.11 as mps is on the critical workflow path for me. I assumed that lack of M1 support in 2021 was fixed by July 2023 - do please correct me if I'm wrong. Thanks |
Describe the bug
I have closed multipassd forcefully with the activity view thing. I don't know how its called correctly in english. Now multipass list is now showing:
The only thing how to get it working again was for me so far to completely delete everything. Maybe there is another way?
My overall impression so far:*
Have used it for a while now and my impression is its not quite stable on mac big sur. After digging around with it a while I am getting more annoyed of it as its not really providing value for me with these errors. Hopefully getting better in the future as I think its a quite good software.
The text was updated successfully, but these errors were encountered: