Article ID: 119885, created on Jan 29, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Linux
  • Virtual Automation

Symptom

Sometimes it is impossible to stop the repair mode through Power Panel. How can I finish repair mode from the server side?

Resolution

WAY 1

Login to the hardware node and restart container 10000000 from inside:

[root@vz ~]# vzlist 10000000
      CTID      NPROC STATUS    IP_ADDR         HOSTNAME
  10000000          8 running   10.39.81.73     amesh.centos6

[root@vz ~]# vzctl exec 10000000 reboot

WAY 2

  1. Obtain the EID of the container in question:

    [root@vz ~]# vzlist 821
          CTID      NPROC STATUS    IP_ADDR         HOSTNAME
           821          - stopped   10.39.81.73     test.centos6
    [root@vz ~]# cat /vz/private/821/.vza/eid.conf
    6cd0894e-e833-b447-a71a-ef3e96085c13
    
  2. Send the following XML API packet to PVA Agent:

    <packet>
    <target>vzaenvm</target>
    <data>
    <vzaenvm>
    <stop_repair>
    <eid>6cd0894e-e833-b447-a71a-ef3e96085c13</eid>
    </stop_repair>
    </vzaenvm>
    </data>
    </packet>
    

For example, this can be done locally on the same host this way:

# echo "<packet><target>vzaenvm</target><data><vzaenvm><stop_repair><eid>08de7d92-1322-7044-a7a4-1b19e87c3ace</eid></stop_repair></vzaenvm></data></packet>" | /opt/pva/agent/bin/sendRequestViaTCP.pl local -

Note!: replace eid in the packet above with eid obtained from step 1

Other ways to send XML API packets to PVA Agent can be found in the following article.

Note!: container 10000000 should exist for this operation to be successful, so if, for some reason, it is gone, a fake one can be created:

# vzctl create 10000000 --ostemplate centos-6-x86_64

Search Words

virtuozzo container repairing

virtuozzo container repair mode

319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f

Email subscription for changes to this article
Save as PDF