I have a stable proxmox environment. After a while, when I try to reboot or shut down a vm, it gives me the following error:
If I try to take same action from console with command 'qm 109 stop', I face with same error. After some research, I have found a solution to save the day. It seems that somehow regex doesn't match to a UPID. If the regex is redesigned, problem will be solved.
Two files need to be edited. Back up following files and do necessary edit on them as shown below:
On /usr/share/perl5/PVE/Tools.pm:
Replace:
On /usr/share/pve-manager/ext4/pvemanagerlib.js:
Replace:
After saving both files, restart pvedaemon. You should be able to restart VMs.
My environment is Proxmox2.3 on Debian7.0. This may have been solved in the latest version. So upgrading may be a solution too. But it is always a good practice to do an upgrade on working environment. This is where our solution is needed.
starting worker failed: unable to parse worker upid 'UPID:fsm-05:0005E6C2:13CC0EA5A:539EB0E9:qmshutdown:109:root@pam:'
If I try to take same action from console with command 'qm 109 stop', I face with same error. After some research, I have found a solution to save the day. It seems that somehow regex doesn't match to a UPID. If the regex is redesigned, problem will be solved.
Two files need to be edited. Back up following files and do necessary edit on them as shown below:
On /usr/share/perl5/PVE/Tools.pm:
Replace:
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]+):$/) {
With:
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]+):$/) {
On /usr/share/pve-manager/ext4/pvemanagerlib.js:
Replace:
var res = upid.match(/^UPID:(\S+):([0-9A-Fa-f]{8}):([0-9A-Fa-f]{8}):([0-9A-Fa-f]{8}):([^:\s]+):([^:\s]*):([^:\s]+):$/);
With:
var res = upid.match(/^UPID:(\S+):([0-9A-Fa-f]{8}):([0-9A-Fa-f]{8}):([0-9A-Fa-f]{8,9}):([^:\s]+):([^:\s]*):([^:\s]+):$/);
After saving both files, restart pvedaemon. You should be able to restart VMs.
My environment is Proxmox2.3 on Debian7.0. This may have been solved in the latest version. So upgrading may be a solution too. But it is always a good practice to do an upgrade on working environment. This is where our solution is needed.
Thanks a lot my friend!! you saved my day!!
ReplyDeleteAnd mine! Couldn't open a console into my machines.
ReplyDeleteRestarted pve deamon with service pvedaemon restart
Thank you for saving my day too!
ReplyDelete