Operational Defect Database

BugZero found this defect 1743 days ago.

Veeam | kb2985

Job to the Linux Repository Fails with "No connection could be made because the target machine actively refused it xx.xx.xx.xx:2500"

Last update date:

6/21/2022

Affected products:

Veeam Backup & Replication

Affected releases:

ALL

Fixed releases:

No fixed releases provided.

Description:

Challenge

When multiple tasks are attempting to use the same Linux repository simultaneously, some connections may fail with the error: No connection could be made because the target machine actively refused it xx.xx.xx.xx:2500. The port shown in the error is a data transmission port, and may be port in the 2500-3300 range.

Cause

This issue may occur if the Linux server has reached the limit of simultaneously opened SSH sessions.

Solution

To resolve this, you may consider increasing the limit on SSH connections. For most Linux servers, this is configured in the, etc/ssh/sshd_conf file. Consider the following values: ClientAliveInterval 30 TCPKeepAlive yes ClientAliveCountMax 99999 MaxSessions 200 MaxStartups 100:30:200 After any sshd_conf values are changed, the SSHD service must be restarted to apply the changes. Keep in mind that restarting the SSHD service may interrupt existing SSH connections.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

Learn More

Search:

...