[PVE-User] migration aborted Can't connect to destination address using public key

Arns, Markus markus.arns at tum.de
Wed Jun 5 13:49:53 CEST 2013


Hi All,

ok, got it. Thanks Luca and Paul. Typing mistake in /etc/hosts which causes the problem.
The migration itself works now, but the CT won't start itself.
Any suggestions on this?

Jun 05 13:46:17 starting migration of CT 104 to node 'node3' (10.162.192.3)
Jun 05 13:46:17 container is running - using online migration
Jun 05 13:46:18 container data is on shared storage 'local'
Jun 05 13:46:18 start live migration - suspending container
Jun 05 13:46:18 dump container state
Jun 05 13:46:18 dump 2nd level quota
Jun 05 13:46:19 initialize container on remote node 'node3'
Jun 05 13:46:19 initializing remote quota
Jun 05 13:46:31 turn on remote quota
Jun 05 13:46:31 load 2nd level quota
Jun 05 13:46:32 # /usr/bin/ssh -o 'BatchMode=yes' root at 10.162.192.3 '(vzdqload 104 -U -G -T < /var/lib/vz/dump/quotadump.104 && vzquota reload2 104)'
Jun 05 13:46:32 ERROR: online migrate failure - Failed to load 2nd level quota: bash: /var/lib/vz/dump/quotadump.104: No such file or directory
Jun 05 13:46:32 start final cleanup
Jun 05 13:46:32 ERROR: migration finished with problems (duration 00:00:15)
TASK ERROR: migration problems

Regards
Markus

-----Ursprüngliche Nachricht-----
Von: pve-user-bounces at pve.proxmox.com [mailto:pve-user-bounces at pve.proxmox.com] Im Auftrag von Paul Gray
Gesendet: Mittwoch, 5. Juni 2013 13:35
An: pve-user at pve.proxmox.com
Betreff: Re: [PVE-User] migration aborted Can't connect to destination address using public key

On 06/05/2013 06:31 AM, Paul Gray wrote:
> On 06/05/2013 03:35 AM, Arns, Markus wrote:
>> Hi all,
> -snip
>> Jun 05 10:15:22 # /usr/bin/ssh -o 'BatchMode=yes' root at 10.162.195.3 
>> /bin/true Jun 05 10:15:22 ssh: connect to host 10.162.195.3 port 22: 
>> No route to host Jun 05 10:15:22 ERROR: migration aborted (duration 
>> 00:00:03): Can't
> 
> Markus - please note that in your follow up to Luca, you're ping'ing 
> and ssh'ing into 10.162.193.3, not 10.162.195.3, which is what has failed above.
> 
> (193 vs. 195 in the 3rd quad)
> 

Actually, *192* (in your response to Luca) vs. 195 (proxmox log for migration).  Nonetheless, your 3rd quad in the IP isn't matching up and is the crux of your issue.

-- 
Paul Gray                                         -o)
314 East Gym, Dept. of Computer Science           /\\
University of Northern Iowa                      _\_V
 Message void if penguin violated ...  Don't mess with the penguin  No one says, "Hey, I can't read that ASCII attachment ya sent me."
_______________________________________________
pve-user mailing list
pve-user at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user



More information about the pve-user mailing list