Search Engine: Elastic

Article ID: 130911, created on Jun 2, 2017, last review on Jun 2, 2017

  • Applies to:
  • Operations Automation 7.0

Symptoms

VE console does not work:

console

/var/log/pa/vps.vm2vf.log on the Virtuozzo node, where VE is located, shows the error:

2017-06-02 09:53:02,039 (ab8ef98e-c2eb-47d9-88ce-1dc7947e5f44 start_console_cb callback) ERROR LogConfigureConsoleCallback [Thread-197] - ERR __PrlVm_StartVncServer (CONFIGURE_CONSOLE)__wait_job_chk_result: result PRL_ERR_FAILED_TO_START_VNC_SERVER @[common/generic_sdk_cb.c][180][__wait_job_chk_result][454199])

At the same time in /var/log/parallels.log on the node:

06-02 09:52:58.983 F /disp:14775:472624/ Task '19Task_StartVncServer' with uuid = {65c68041-5eb3-44d7-bafa-ba2f3d988f89} was started. Flags = 0 {1832ff3f-9266-4d41-9edf-466fd8daead2} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30}(DspCmdVmStartVNCServer)
06-02 09:52:58.987 F /disp:14775:472624/ the VNC server starts : prl_vncserver_app --passwd --listen 0.0.0.0 --auto-port --min-port 5800 --max-port 65535 {c719e624-b755-4ec4-9c5f-09ae874d0917} {1832ff3f-9266-4d41-9edf-466fd8daead2} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30}(DspCmdVmStartVNCServer)
06-02 09:53:02.036 F /disp:14775:472624/ Timeout reached while waiting for a reply from the VNC server. {1832ff3f-9266-4d41-9edf-466fd8daead2} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30}(DspCmdVmStartVNCServer)
06-02 09:53:02.037 F /disp:14775:472624/ Start VNC server failed with error code: 80035003 'PRL_ERR_FAILED_TO_START_VNC_SERVER' {1832ff3f-9266-4d41-9edf-466fd8daead2} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30}(DspCmdVmStartVNCServer)
06-02 09:53:02.037 F /disp:14775:472624/ Task '19Task_StartVncServer' with uuid = {65c68041-5eb3-44d7-bafa-ba2f3d988f89} was finished with result PRL_ERR_SUCCESS (0) )  {1832ff3f-9266-4d41-9edf-466fd8daead2} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30} {cc4cb253-43be-438a-a36c-8142d8303f30}(DspCmdVmStartVNCServer)

Cause

The Virtuozzo level issue with the VNC server or Virtuozzo Dispatcher service.

Resolution

As a fast workaround, use the steps from this article to start the VNC console manually for the affected VM.

The VNC server password is stored inside VM's configuration file /pcs/<customer_id>.<VM_NAME>.pvm/config.pvs in RemoteDisplay section:

 <RemoteDisplay dyn_lists="">
     <Mode>1</Mode>
     <Password>***</Password>  <-----------HERE
     <HostName>0.0.0.0</HostName>
     <PortNumber>0</PortNumber>
     <Encrypted>0</Encrypted>
  </RemoteDisplay>

As a possible more permanent solution, restart the Dispatcher service (all VMs will be restarted):

# service parallels-server restart 

Contact Virtuozzo Support to get the root cause analysis of the VNC server start-up slowness.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF