public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Lund Svein-Erik <proxmox@selund.se>
To: matthew <matthew@peregrineit.net>,
	 Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] VM Migration Not Happening :-(
Date: Sun, 1 Sep 2024 17:14:26 +0000 (UTC)	[thread overview]
Message-ID: <1926822580.199.1725210866323.JavaMail.zextras@selund.se> (raw)
In-Reply-To: <7ba8acf4-f26f-480f-becf-3603f18c6520@gmail.com>


I Can't give you any exact cause, but the message "channel 2: open failed....." comes from an issue with ssh between the nodes. I can't really tell anything else from the log you've posted.

---
 ---------------------------
From: "duluxoz" 
To: "Proxmox VE user list" 


Sent: Sunday, September 1, 2024 10:12 AM
Subject: [PVE-User] VM Migration Not Happening :-(

Hi All,

I need help with figuring out why I can't migrate a VM from one Proxmox 
Node to another (in the same cluster, of course).

These are the details provided by the Proxmox Task Log:

```

task started by HA resource agent
2024-09-01 18:02:30 use dedicated network address for sending migration 
traffic (192.168.200.103)
2024-09-01 18:02:30 starting migration of VM 100 to node 'pven3' 
(192.168.200.103)
2024-09-01 18:02:30 starting VM 100 on remote node 'pven3'
2024-09-01 18:02:30 [pven3]
2024-09-01 18:02:32 start remote tunnel
2024-09-01 18:02:33 ssh tunnel ver 1
2024-09-01 18:02:33 starting online/live migration on 
unix:/run/qemu-server/100.migrate
2024-09-01 18:02:33 set migration capabilities
2024-09-01 18:02:33 migration downtime limit: 100 ms
2024-09-01 18:02:33 migration cachesize: 256.0 MiB
2024-09-01 18:02:33 set migration parameters
2024-09-01 18:02:33 start migrate command to 
unix:/run/qemu-server/100.migrate
channel 2: open failed: connect failed: open failed
2024-09-01 18:02:34 migration status error: failed - Unable to write to 
socket: Broken pipe
2024-09-01 18:02:34 ERROR: online migrate failure - aborting
2024-09-01 18:02:34 aborting phase 2 - cleanup resources
2024-09-01 18:02:34 migrate_cancel
2024-09-01 18:02:36 ERROR: migration finished with problems (duration 
00:00:07)
TASK ERROR: migration problems
```

If someone could point me in the correct direction to resolve this issue 
I'd be very grateful - thanks

Cheer

Dulux-Oz


_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user


_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user


  reply	other threads:[~2024-09-01 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01  8:10 duluxoz
2024-09-01 17:14 ` Lund Svein-Erik [this message]
2024-09-01 22:02 ` Gilberto Ferreira
2024-09-02  5:50   ` duluxoz
2024-09-02  7:51     ` Fabian Grünbichler
2024-09-02  9:54       ` duluxoz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1926822580.199.1725210866323.JavaMail.zextras@selund.se \
    --to=proxmox@selund.se \
    --cc=matthew@peregrineit.net \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal