Skip to main content

Error when trying to reboot a VM in Proxmox

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:

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.

Comments

  1. Thanks a lot my friend!! you saved my day!!

    ReplyDelete
  2. And mine! Couldn't open a console into my machines.

    Restarted pve deamon with service pvedaemon restart

    ReplyDelete

Post a Comment

Popular posts from this blog

Migration from Proxmox to Openstack

I needed to migrate virtual machines in proxmox to openstack. VMs are in raw format. I needed to take some actions for a succesfull migration. I have perform all actions on Ubuntu 12.04 with virt-manager. qemu-kvm is installed. Here is the list of actions that I took: First, close the machine and copy the image file into your Ubuntu. Convert raw image to qcow2 format: qemu-img convert -O qcow2 image1.raw image1.qcow2 You need the image in qcow2 format for compatibility with openstack platform.  Open the converted image in virt-manager. Before opening, edit disk options. Under ' advanced options ' section, select ' qcow2 ' as ' storage forma t '. Start the virtual machine. You should see the login screen soon. (If you don't set storage format, vm will not find a bootable device. )   If everything is ok so far, close the vm. Take qcow2 image and upload it into glance. It may take time depending on size of it. After this process is completed, open a

Integration of MuPDF Project as a Library into an Android Studio Project

I have needed to use MuPDF library in my android project. After some research, I have seen that there are many integration tutorials but, but integrated projects are developed on Eclipse. For projects on AndroidStudio+Gradle, there is no example. I mean there is no specific example which exactly refers to this issue. So, after achieving my goal, I want to share the steps publicly so that it can be reused by others.

How to avoid API-level warning of Android Studio

Before giving the solution, let's start with a scenario. setSelectionFromTop() is a new method in Android Lollipop API. This method is basically beneficial to precisely keep scroll state of a ListView. By keeping that info, a developer can go back to old scroll state after doing some operation like data set change. You are aware of API level and you do your control before you call this function: if (currentapiVersion >= Build.VERSION_CODES.LOLLIPOP) { srlistview.setSelectionFromTop(index, top); } But if project minSdk is set to a lower level (in this case it is 15), this warning will still be displayed in Android Studio: