unable to parse worker upid When I try to do vzrestore

[hueznar]

Hi. I did a vzdump from a 2.1 proxmox node, and then copied the dump to a proxmox 2.2 node. When I tried to do the vzrestore from the 2.2 node I got this error:unable to parse worker upid 'UPID:mymachine:00094940:1221122CF:539CE448:vzrestore:107:root@pam:'Is possible that error comes for different proxmox versions between nodes?. If yes, how can upgrade from 2.1 to 2.2 safely to lauch again the vzdump/vzrestore?thanks in advance

 

[hueznar]

OK. I have read that 2.1 and 2.2 dumps are not compatible, so the question is: how can upgrade from proxmox 2.1 to 2.2, but not to 2.3 or above? (force 2.1 to 2.2 only).thanks again.

 

[dietmar]

Restore should work anyways. Above warning seems unrelated to me.

 

[hueznar]

Hi Dietmar, thank you for your reply and nice work.

I tried several ways to do de vzdump (snapshot, stop, suspend), and always same error when I try to restore the 2.1 vzdump in the 2.2 system. The vzdump is always ok, but the restore:

unable to parse worker upid 'UPID:myhost:000FC923:122674049:539DC0BC:vzrestore:107:root@pam:

I don't know what can I do... Any idea?.

thanks again

 

[dietmar]

Please can you try to run the restore command from the command line?

 

[spirit]

unable to parse worker upid

As far I remember, it was a bug in proxmox 2.1 or 2.2, with long running host, and upid was too big to be parse.

fixed here :

https://git.proxmox.com/?p=pve-comm...;hpb=d9184f4701f593c48813264341c446069f53a8d5


(make can you try to modify code yourself)

 

[hueznar]

Yeah, it worked!. Was that bug: my proxmox nodes and vms had more than 600 days of uptime, and simply I restarted nodes and VMs and problem was fixed.
thank you for your very nice help and work