Proxmox 3, starting worker failed: Unable to parse worker upid error

This is a bug in Proxmox 3, when you have a high uptime, usually more than 365 days, and you want to initiate an instance (VM), you get the error:

starting worker failed: unable to parse worker upid 'UPID:proxmox5:0001A7DA:189F3C8F1:57C9A234:qmstart:113:root@pam:' (500)

The bugs originates because the string for the error is larger than expected, so a quick fix it’s to make the string larger, in order to do so we have to modify the next file:


And look for this line somewhere around the 762 line:

# "UPID:$node:$pid:$pstart:$startime:$dtype:$id:$user
 if ($upid =~ m/^UPID:([a-zA-Z0-9]([a-zA-Z0-9\-]*[a-zA-Z0-9])?):([0-9A-Fa-f]{8}):([0-9A-Fa-f]{8}):([0-9A-Fa-f]{8}):([^:\s]+):( [^:\s]*):([^:\s]+):$/) {

And change it to:

# "UPID:$node:$pid:$pstart:$startime:$dtype:$id:$user
 if ($upid =~ m/^UPID:([a-zA-Z0-9]([a-zA-Z0-9\-]*[a-zA-Z0-9])?):([0-9A-Fa-f]{8}):([0-9A-Fa-f]{8,9}):([0-9A-Fa-f]{8}):([^:\s]+):( [^:\s]*):([^:\s]+):$/) {

It’s important to note that if you change the 8 for the 9 when you have less than 365 days of uptime you won’t be able to initiate the VM’s.

Save and close, now just restart the eve daemon:

/etc/init.d/pvedaemon restart

Now you should be able to initiate instances without any problem.

This entry was posted in Misc. Bookmark the permalink.