Article ID: 120075, created on Feb 11, 2014, last review on Apr 11, 2016

  • Applies to:
  • Operations Automation 5.5
  • Virtuozzo
  • Virtuozzo hypervisor


  1. Customers cannot open VNC Console for virtual machines from PACI CP.
  2. Update 4 for POA 5.5 is not installed.
  3. Parallels Server hosts many other VMs (>15).


Due to the number of VMs and running VNC services for those VMs, the task to (re)start VNC service for VM on opening Console from PACI CP might take more than 1 minute. PACI CP currently has the timeout for this operation of 1 minute, thus the error is displayed.


  1. Update POA installation to 5.5.4.

    This does not fix the issue completely, however VNC console is not restarted if it is accessed from the same session. That is why accessing VNC console again in 1-2 minute should load VNC applet.

  2. Decrease the number of running VMs to 12-15 to decrease VNC service start time.

    It is understandable that this can lead to underutilization of the hardware. In this matter, there are the following requests submitted:

    CCU-7704 to increase the timeout in PACI CP and make this timeout configurable. PSBM-24928 to decrease the time needed to start a VNC console on a busy server.

Search Words




vnc console

paci cp

PACI console not able to access both from lab and production

status changes

can't access PACI console

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 0dd5b9380c7d4884d77587f3eb0fa8ef 614fd0b754f34d5efe9627f2057b8642

Email subscription for changes to this article
Save as PDF