Article ID: 10029, created on Mar 4, 2011, last review on Jun 17, 2016

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Operations Automation 5.0
  • Virtuozzo
  • Virtuozzo containers
  • Virtuozzo hypervisor


VPS-related task fails in POA with the following diagnostics:

Connection to VZAgent was closed: recv - 0


Generally, this means that TCP connection to PVA Agent of a Hardware Node was closed unexpectedly. Possible reasons for this to happen are:

  1. PVA Agent service on a PVC server was restarted or stopped during task processing in POA
  2. PVC server is responding very slow and POA drops connection to PVA Agent after 90 seconds of waiting for XML greeting


  1. Check the version of the installed PVA Agent on the node. Use this article to check whether you are using the latest version. If the PVA Agent on the node is out-dated - update it to the latest available version.
  2. Check status of PVA Agent service on PVC server, make sure it is up and running and resubmit failed task in POA.
  3. Try to open connection to PVA Agent from POA core and estimate the time necessary to receive the greeting using one of the following commands:

    # telnet TARGET_SERVER 4433
    # openssl s_client -connect TARGET_SERVER:4434 -cipher ADH-AES256-SHA

    If it takes longer than 90 seconds, this error is likely to occur. It is necessary to decrease the load on the PVC server in question.

Search Words

pvaagent not responding


vps backup

Connection to VZAgent was closed: recv - 0

vzagent not responging

vzagent not responding

Unable to restart vps

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

Email subscription for changes to this article
Save as PDF