SSH Destination hitting "SSH Multiplexing Limit"

When receiving an error like the following:

[ERROR] Failed transferring account "accountName" backup to destination "destinationName". Error: mux_client_request_session: session request failed: Session open refused by peer

Host key verification failed.

Your SSH destination may be hitting an SSH Multiplexing Limit.

This could be caused by remarking the MaxSessions at /etc/ssh/sshd_config on both your source server and destination and you may have set the 'Concurrent Backup Accounts' and 'Concurrent Restore/Download Accounts' values to 10 on the "Settings -> Performance"

As a workaround, please try disabling MaxSessions, restarting your "sshd" service, and lowering down the 'Concurrent Backup Accounts' and 'Concurrent Restore/Download Accounts' values to 5. Then we ask that you monitor your next backup job run, to see if this has addressed the issue.

  • 0 Kunder som kunne bruge dette svar
Hjalp dette svar dig?

Relaterede artikler

Backblaze/S3 - Excessive Storage Use by JB5

We have received some reports of excessive Storage use by JetBackup 5 in the S3 Bucket. For...

My S3 Vendor is not included in the supported list on JetBackup 5?

You can find a small list of S3 Vendors that are supported with the new S3 Compatible plugin at...

S3 Common Issues / Failed to upload file

S3 destinations can often hit request limits when destinations are configured with high...

S3 Compatible - "Error: The key 'XXXX' is not valid (InvalidAccessKeyId)"

Here are some helpful tips to troubleshoot the error "Error: The key 'XXXX' is not valid...

Unable to Validate Destination - SSH

JetBackup uses public-key authentication to connect to and validate your SSH Destination. This...