OpenVZ7 - Migrate options: vzmigrate, ovztransfer.sh or prlctl migrate? [message #53286] |
Fri, 18 May 2018 07:19 |
TomB
Messages: 30 Registered: July 2017 Location: -Root-
|
Member |
|
|
Hi all,
I have several servers in different datacenters with public ip addresses assigned, think of ovh etc. There is no better solution for public containers than OVZ7, that is a fact.
I am stuck on migrating containers between the datacenters.
VZMigrate
vzmigrate is deprecated.
-r, --remove-area no = no longer works, the container is deleted after the migration..
OVZ Migrate
ovzmigrate.sh is for container migration from virtuozzo 6 to virtuozzo 7+ and works, but is this the official way for OVZ7 to OVZ7?
prlctl migrate
https://docs.openvz.org/openvz_command_line_reference.webhel p/_prlctl_migrate_2.html
This does not work.. I have different SSH ports on each machine.
But even on port 22 I get a network broken error. python3 is active on the destination server after the command prlctl migrate command (for 3 seconds), but it fails.
How can I migrate from Server 1 SSH Port 2210 to Server 2 SSH Port 2211 without ovzmigrate.sh and without destroying my container on server 1?
prlctl migrate 92b9870b root@ x.x.x.x--ssh "-o Port=2211"
or
prlctl migrate 92b9870b root@ x.x.x.x:2211
Results with firewall disabled:
Failed to migrate the VM: Unable to establish a connection between "x.x.x.x" and "ovz7.xx.com". The network connection between these servers may be broken, or one of the servers may be down. Contact your Virtuozzo administrator for assistance.
I would love to hear from someone who knows this
Details:
Linux ovz7.xx.com 3.10.0-693.21.1.vz7.46.7 #1 SMP Fri Apr 20 17:42:34 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux
[Updated on: Fri, 18 May 2018 07:29] Report message to a moderator
|
|
|
Re: OpenVZ7 - Migrate options: vzmigrate, ovztransfer.sh or prlctl migrate? [message #53287 is a reply to message #53286] |
Fri, 18 May 2018 15:14 |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
Hi,
[root@node ~]# prlctl migrate $UUID $IP --ssh "-o Port=2222"
Host key verification failed.
Migrate the CT teatstest on $IP ()
root@$IP's password:
Checking preconditions
Copying static data
Live migration stage started
The CT has been successfully migrated.
So, basically if works with prlctl.
i think there is still something with firewall.
i'd start with disabling firewall completely, putting sshd on default 22 port and attempt to migrate.
If it works, move sshd on same port on both nodes, say, 2222 and retry.
If it works, move sshd on one node on a different port like you have now and try again.
Hope that helps.
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|