[PVE-User] Issues with unable to parse worker upid

[Mikhail]

Greetings,

I just faced the following issue with backups - it fails from both web
interface and console:

# vzdump 1004 1001 --mode snapshot --mailto a at b.c --storage backups
unable to parse worker upid
'UPID:pm2:000AAD3F:108B4A714:54479976:vzdump::root at pam:'
#

I found the following thread dated almost 1 year ago:

http://pve.proxmox.com/pipermail/pve-devel/2013-November/009108.html

Last message from Dietmar was: "But we need to fix this bug, because it
can occur also with actual code."

My node's uptime is 514 days.

Has this been fixed since? Is the only way to fix this is to reboot the
machine?

proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-20-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Thanks.