Article ID: 118464, created on Nov 6, 2013, last review on Jun 17, 2016

  • Applies to:
  • Operations Automation
  • Virtuozzo
  • Virtuozzo containers
  • Virtuozzo hypervisor
  • Virtual Automation

Symptoms

Backup tasks fails with different errors, for example:

 Task 'Backup VPS 'vps1.node.com' from HN 'pvcl44.test.com'' (id=6548952) execution failed. Connection to VZAgent was closed: poll_read efds 

 Task 'Backup VPS 'mail2.test.com' from HN 'pvcl22.test.com'' (id=6549563) execution failed. Connection to VZAgent was closed: recv - 0 

Also, you can see a high amount of the established connections on the backup node (the first column of the output shows the number of connections):

# netstat -ntpu | egrep ':443[3-4].*ESTAB' | awk 'BEGIN{FS="[ \t]+|:"};{print $6}' | uniq -c | sort -r
 42 192.168.0.2 
 21 192.168.0.1 
 9 192.168.0.3 
 1 192.168.0.4 
 1 192.168.0.5 

Cause

An outdated PVA Agent version on the source node may cause unclosed network connections, therefore filling up the amount of free sockets.

Resolution

  1. Check the version of the PVA Agent installed on the source node:

    # rpm -q pva-release 
      pva-release-4.6-1509
    
  2. Update the Agent to the latest build. You can find the latest build and installation instructions in this article:

    Parallels Virtual Automation builds, releases, and supported virtualization products

Search Words

backup fails

Connection to VZAgent was closed

pva-release

execution failed

poll_read efds

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 319940068c5fa20655215d590b7be29b 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 0dd5b9380c7d4884d77587f3eb0fa8ef 400e18f6ede9f8be5575a475d2d6b0a6 614fd0b754f34d5efe9627f2057b8642

Email subscription for changes to this article
Save as PDF