Search Engine: Elastic

Article ID: 128027, created on Jan 12, 2016, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 6.0


All VPS backup tasks regularly start failing with the following error:

422 : Failed to connect to backup server: Can't connect: System errors : unauthorized request

The backup node has 20 established connections on port 4434:

[root@vzbackup01 ~]# netstat -antp | grep 4434
tcp        0      0      *                   LISTEN      17245/pvaagent [gen
tcp        0      0          ESTABLISHED 17245/pvaagent [gen
tcp        0      0          ESTABLISHED 17245/pvaagent [gen

[root@vzbackup01 ~]# netstat -antp | grep 4434 | wc -l

While the other end does not have any connections open:

[root@vz01 ~]# netstat -antp | grep 4434
tcp        0      0      *                   LISTEN      39194/pvaagent [gen
tcp        0      0 :::4434                     :::*                        LISTEN      39194/pvaagent [gen
[root@vz01 ~]# netstat -antp | grep

The backup node was already tweaked according to this article, but the limit is still getting reached.


Bad network configuration between the node(s) and the backup node. The intermediate network equipment interrupts the idle connection that transmits the backup data, and TCP connections remain stuck on the backup node.


Configure the intermediate network equipment to terminate the connections properly, with sending FIN or RST packets to both the source node and the backup node, when terminating idle connections.

As an alternative, but less preferable solution, it is possible to tune TCP keepalive parameters on the backup node, the instructions can be found in the following article:

Backup fails: Connection timed out

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF