Rescan operation fails when adding a server to a Protection Group in RHEL 6.6.

Hi ​@Yong 

Check the server-side SSH Timeout: Check sshd_config
ClientAliveInterval 300
ClientAliveCountMax 3

Is there disk space in /tmp?

df -h /tmp

Can you check the installation logs on the target server?

/var/log/veeam/veeaminstaller.log /var/log/messages

can you try remove cert cache

rm -rf /var/lib/veeam/*

Redeploy the agent and ensure the certificate is accepted.

Check if all libraries are up to date by comparing them on the server that is running, ---> glibc gcc libgcc , or also update them ssh.

yum install -y glibc gcc libgcc

we await updates

I doubt it’s about a timeout, sorry to disagree.

From the log:

[23.12.2024 16:24:41.045]    <01>    Info (3)    [Ssh] Creating new connection f6563d52-54d6-4552-9a1e-b41773b3e40e [host: 'TARGET SERVER', port: 22, elevation to root: 'no', autoSudo: no, use su if sudo fails: no, host name: TARGET SERVER, IPs: [TARGET SERVER], AuthenticationData: [UserName: root, AuthTypes: [KeyboardInteractive, Password]]]

«truncated for readability» 

[23.12.2024 16:24:56.339]    <01>    Info (3)    [LinuxManagedPackageInstaller] Uploading the package
[23.12.2024 16:24:56.343]    <01>    Info (3)    [UploadManager] Uploading linux package 'veeamdeployment-12.2.0.334-1.x86_64.rpm'
[23.12.2024 16:24:56.403]    <01>   Error (3)    Failed to upload file D:\veeam\Backup\Packages\veeamdeployment-12.2.0.334-1.x86_64.rpm to /tmp/veeamdeployment-12.2.0.334-1.x86_64.rpm
[23.12.2024 16:24:56.403]    <01>   Error (3)    The server has closed the connection. (Rebex.Net.ScpException)
[23.12.2024 16:24:56.403]    <01>   Error (3)       위치: mwgvd.ymphv.wwrbt(Boolean p0)
[23.12.2024 16:24:56.403]    <01>   Error (3)       위치: Rebex.Net.Scp.bwyfn(String p0, String p1, Stream p2, Int64 p3, ypfpi p4)
[23.12.2024 16:24:56.403]    <01>   Error (3)       위치: Rebex.Net.Scp.yfukn(String p0, String p1, Int64 p2, ypfpi p3)
[23.12.2024 16:24:56.403]    <01>   Error (3)       위치: Veeam.Backup.SSH.RebexLib.CSshRebexScpFileLoader.UploadFileImpl(String from, String to, Boolean needToElevate, String mode, IFileLoaderOptions fileLoaderOptions)

Less than a second passes before the connection is closed from the remote server.

https://www.veeam.com/kb4250

Try the steps here, though i’m doubtful it’s about this. For reference, Veeam in current version will try to use one of three .NET SSH Libraries for SSH connections:

Granados => Very old library, almost certainly no modern system (post 2015? loose date here) will use it and it likely will never work. Kept for legacy systems that require it. Can almost guarantee you can ignore all Granados related errors, they’re almost certainly expected.

Renci => Probably the most common one that will work for most people

Rebex => Newest one, most secure of the three, but the security hardening sometimes is not compatible with other hardening.

Anyways, give the KB a shot, and if it won’t go, open a Support Case for the issue: https://veeam.com/1771.

Sorry for the late update.

​@Link State 

Check the server-side SSH Timeout: Check sshd_config
→ It doesn’t work.

Is there disk space in /tmp?

→ /tmp has sufficient capacity.

Can you check the installation logs on the target server?

→ The log file itself does not exist.

can you try remove cert cache

→ The certificate also doesn't exist.

Check if all libraries are up to date by comparing them on the server that is running, ---> glibc gcc libgcc , or also update them ssh.

→ The file list is as follows:

→ RHEL 6.6 has become EOS, so it cannot be installed using yum. Are there any packages I need to install from the following list?

​@ddomask 

I tried the solution according to the Veeam KB, but I could not find the tmux-related settings, perhaps because the server where the problem occurred was RHEL 6.6.
I created and ran the fapolicyd script and tried Rescan, but the same problem occurs.

Got it, thanks for the efforts. I would open a support case at this stage and let Support take a look. Probably this will not be solvable over forums alone.

​@ddomask 

Thank you for your concern. 

The issue was resolved using a workaround. 

Since you told us that there were problems with the SSH method, I decided to use a method that does not use SSH.When registering the backup target server, I tried registering it based on a certificate.

https://helpcenter.veeam.com/docs/backup/plugins/mongo_protection_group_certificate.html?ver=120

After registering using the certificate method, the backup target server was registered and the Rescan operation was possible. And as a result of today's confirmation, the backup job has also been completed.

Thanks again for your help.