Article ID: 120613, created on Mar 19, 2014, last review on Feb 22, 2016

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


  1. Virtual Automation Agent has been updated by means of VA Management Node web interface through 'Software updates' screen.
  2. The task to install the update fails with the following messages:

    Starting the process    Completed
    Initializing repository (   
    #312 Connection to remote host cannot be open or is closed  Failed
  3. After the task fails, the node is shown as offline in VA and the related services are down on the respective hardware node:

    [root@pcs ~]# pvaagent status
    pvaagentd dead but pid file exists
    [root@pcs ~]# pvapp status
    pvappd is stopped
  4. pvappd service cannot be started with the following errors:

    [root@pcs ~]# pvapp start
    Starting pvappd:
    Starting httpd: Syntax error on line 6 of /etc/opt/pva/pp/plugins/httpd/include.ssl.conf:
    SSLCertificateFile: file '/etc/httpd/$$ssl_cert_root/ssl.crt/server.crt' does not exist or is empty
  5. The corresponding VA update log (/var/log/pva/setup/<date_time>_pva-setup.log) ends abruptly with the following messages:

    02/16/14 01:36:36               > Performing PVA 6.0 postupgrade configuration
    02/16/14 01:36:36                       - Configuring component 'PVA Agent Core Libraries'
    02/16/14 01:36:36                       - Reconfiguring PVA Agent Core Libraries
    02/16/14 01:36:36                       * LinuxHelper::execute_command - executing
                                                     sh /etc/opt/pva/setup/cached_repo//linux/x86_64/11/6.0-2160/hints/ --packages "linux/x86_64/11/6.0-2160/files/RPMS/pva-agent-core-6.0-968.x86_64.rpm linux/x86_64/11/6.0-2160/files/RPMS/pva-agent-core-third-6.0-968.x86_64.rpm"
  6. As a result, Power Panel does not work for any Containers and Virtual Machines, hosted on the node.

  7. Network adapter type cannot be changed for virtual machines in VA MN interface.


The issue is recognized as a product bug with internal ID PVA-33626. The process of updating VA Agent from VA should be improved.


Install VA updates through the backend command-line interface with pva-setup tool:

# pva-setup --install

Refer to this article for more information about installing/removing specific versions of VA MN and Agent

To fix the broken system, it is required to reinstall VA Agent completely:

113071 How to install/reinstall/upgrade VA Agent

Search Words

guest operating system

VZAgent returns error #312: "Connection to remote host cannot be open or is closed"

pvaagent dead but pid file still exists

syntax error on line 6


power panel not working

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 319940068c5fa20655215d590b7be29b 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF