ssh connection failed: 'Connection refused' - NIC_RX_FILTER_CHANGED Cannot access instance #3071
Comments
|
Hey, @fsck66! The fact that you get a which should open up a window with a console into the instance. |
|
unfortunately I have by now redeploy the instance and multipass on the problem system. What will this qemu command do? does it launch a session into the VM no matter what, does it change anything? Looking back I believe this occurred after upgrading UTM, which I rarely use, but I also have on my ARM apple silicon system to emulate x86 architecture on VM that doesn't have an ARM version. I know that also uses QEMU but I already had it loaded at the time and used in in conjunction with multipass. Would that have anything to do with it or do these solutions, including multipass, maintain their own QEMU? thanks |
|
Hi @fsck66! As @andrei-toterman mentioned, we would like to see the output of the console that pops up when running the In essence, what the Given these symptoms, it's highly unlikely UTM's qemu is causing issues with Multipass and seems to just be a coincidence. |
|
Hi, I am not sure I can help track my problem anymore since I've since redeployed and reconfigured my instance via netplan and so my config is different now. I did run the command just for sakes (I changed the new Mac addresses to reflect the new ones in the command everything else is the same) and it returns:
|
|
I ran into a similar issue when upgrading to 1.12.0
I uninstalled again and reverted back to 1.11.1 and things are working....so perhaps downgrading would work for someone in the same position... |
|
I'm suffering the same issue on my M1 Mac running OS 14.2.1 and Multipass 1.12.0 I am not aware of any changes to host or guests, but one day the guest stopped booting. I ended up removing Multipass and reinstalling, creating a new VM, but get the same error. VMs are always in an unknown state and the last log entry reads NIC_RX_FILTER_CHANGED I have uninstalled again and installed the 1.13 RC but get the same. Interestingly, the issue was originally reported on 1.11 and the poster above suggests the same happens on 1.12, but was fixed by reverting to a previous version. I have not gone back, but the fact that OP suffered on 1.11 suggests this may not be a reliable fix. How does the issue survive an uninstall / reinstall? I'm purging config when prompted by the uninstall script. Log entry of 1.13 attempt: `[2024-01-03T15:43:42.847] [debug] [update] Latest Multipass release available is version 1.12.2 [2024-01-03T15:47:14.306] [debug] [trim-katydid] QMP: {"return": {}} [2024-01-03T15:47:27.426] [debug] [trim-katydid] QMP: {"timestamp": {"seconds": 1704296847, "microseconds": 426481}, "event": "NIC_RX_FILTER_CHANGED", "data": {"path": "/machine/unattached/device[6]/virtio-backend"}}` |
|
I've got my install fixed now, although I had to delete & purge any installed VM. After reading: I saw I had the same issue with an invalid /var/db/dhcpd_leases file - the file had multiple entries with the same name. I had to stop, delete & purge any running VM, delete the dhcpd_leases file and reboot. Everything worked fine on the freshly started host. I guess this explains why the issue persisted across multiple multipass versions and installs - it was an issue with MacOS. I think I had a multipass crash that left the system in an unstable state. Perhaps multipass should check that the dhcpd_leases list is sane? This should be straightforward to test by editing the file to include duplicate entries. |
|
Hi @IknowJoseph, I'm glad you got it working!
Multipass doesn't manage this file, so I would be very reluctant to edit the file, but perhaps we could report that there are duplicate entries and let the user try to fix it. |
|
Thank you @IknowJoseph, I was stuck too and the total of {sudo kill multipass*, whack dhcp leases, reboot} did the trick. If I get stuck again, I may attempt differential diagnosis. |
|
I had a similar situation today (did a nmcli networking off inside a multipass instance) and after that, I could not start the instance properly (took 5 min until timeout on a 'multipass start ' command, and its status was unknown). I could not use SSH to connect (no IP), nor use multipass shell/multipass exec... what I did:
I know step 3) above only works for the situation I was in, but the way to edit and correct wrong configurations on the VM filesystem can help in many other cases cat /etc/lsb-release multipass --version |
Describe the bug
Cannot connect to instance. It was working fine until today. Now takes forever to start the instance and Multipass doesn't seem to register the state of the VM, always shows as running on menu. Issue is networking. It only shows internal interface 192.168.x It really sucks networking is so fragile with multipass as I truly love the small footprint and flexibility.
MacOS Firewall OFF
After VM starts examples:
multipass shell GALAXY-DOCKshell failed: ssh connection failed: 'Connection refusedmultipass info GALAXY-DOCKinfo failed: ssh connection failed: 'Connection refusedHave tried resetting local.driver to qemu, no difference.
To Reproduce
How, and what happened?
-network name=en0,mac="52:54:00:32:c3:b4to associate it with my wireless NIC. The mac addressed being passed is for the virtual NIC in the VM instance, in this case, enp0s2. I am forcing this MAC address on the instance because I have a static DHCP reservation configured for it..localresolution.Expected behavior
This worked fine for weeks now it doesn't.
Logs
[debug] [GALAXY-DOCK] QMP: {"timestamp": {"seconds": 1683851504, "microseconds": 962322}, "event": "NIC_RX_FILTER_CHANGED", "data": {"path": "/machine/unattached/device[13]/virtio-backend"}}[2023-05-11T20:36:24.608] [debug] [GALAXY-DOCK] Resetting the network[2023-05-11T20:36:24.610] [debug] [GALAXY-DOCK] QMP: {"return": {}}[2023-05-11T20:36:24.621] [debug] [GALAXY-DOCK] QMP: {"return": {}}[2023-05-11T22:44:25.178] [debug] [base_vm] Error getting extra IP addresses: ssh connection failed: 'Connection refused'[2023-05-11T22:50:42.393] [debug] [base_vm] Error getting extra IP addresses: ssh connection failed: 'Connection refused'Additional info
info failed: ssh connection failed: 'Connection refused'multipass get local.driverqemuAdditional context
Recently connected to a new LG monitor and dock that has an ethernet port. Haven't tested yet without the dock as I'd like to understand the issue given as how networking seems so fragile from one use case to another, I would like to make my config as portable as possible without having to wipe out and redeploy so often.
The text was updated successfully, but these errors were encountered: