Veeam B&R Linux Proxy issues (c++ libraries missing)

[mikeg5]

If anyone encounters this error after installing and attemping a backup on a fresh Linux (RHEL 8/9) Veeam Backup Proxy. You would be led to this KB and probably already experinced the same frustration as me.

The error:

Code: Select all

error: backup proxy is missing c++ runtime components, download from http://vee.am/runtime

The supposed solution:
https://www.veeam.com/kb2678
(For linux the solution is to reinstall the agent, etc. following this KB: https://www.veeam.com/kb4298?ad=in-text-link)

I tried this to no avail, reinstalled several times, rebuilt the OS 2 times, tried both RHEL 8 and 9, disabled selinux, reenabled selinux, disabled firewalld, enabled firewalld... you get the point .

The next steps were to dig into logs a bit deeper to see what is going on. After walking through the log line by line during a failed backup attempt, I saw this:

Code: Select all

[12.08.2023 09:41:38.909] <140559851157056> dsk      | ERR |Unable to set install hook libcrypt.so.1: cannot open shared object file: No such file or directory: failed to open library libdiskLibPlugin.so
[12.08.2023 09:41:38.909] <140559851157056> dsk      | Settings VDDK hooks Failed.
[12.08.2023 09:41:38.909] <140559851157056> dsk      | Created new temporary directory for VDDK: /root/tmp/veeamagent_45566
[12.08.2023 09:41:38.909] <140559851157056> dsk      | Creating new VDDK configuration file: /root/tmp/veeamagent_45566/tmpconfig.ini
[12.08.2023 09:41:38.909] <140559851157056> vdl      | Loading VDDK library, compatible with version: 7.0, directory: '/opt/veeam/transport/VeeamAgentTmp_{711c97c4-1b12-4019-90f4-113eaf113a61}/vddk', module: '/opt/veeam/transport/VeeamAgentTmp_{711c97c
4-1b12-4019-90f4-113eaf113a61}/vddk/lib64/libvixDiskLib.so', configuration file: '/root/tmp/veeamagent_45566/tmpconfig.ini'
[12.08.2023 09:41:38.921] <140559851157056> vdl      |   [vddk] OBJLIB-LIB: Objlib initialized.
[12.08.2023 09:41:38.921] <140559851157056> vdl      |   [vddk] VixDiskLib: Attempting to locate advanced transport module in "/opt/veeam/transport/VeeamAgentTmp_{711c97c4-1b12-4019-90f4-113eaf113a61}/vddk".
[12.08.2023 09:41:38.923] <140559851157056> vdl      |   [vddk] VixDiskLib: Could not load default plugins from /opt/veeam/transport/VeeamAgentTmp_{711c97c4-1b12-4019-90f4-113eaf113a61}/vddk/lib64/libdiskLibPlugin.so: Cannot open library: libcrypt.so.1
: cannot open shared object file: No such file or directory.
[12.08.2023 09:41:38.923] <140559851157056> vdl      | WARN|Failed to load library from path /opt/veeam/transport.

And now it makes some more sense once I checked to see if the libcrypt library had been installed, which it had not.

I then found the correct package (its been the same name for many iterations of RHEL, but always good to check anyways):

Code: Select all

dnf provides libcrypt.so.1

This turned up the following results:

Code: Select all

libxcrypt-compat-4.4.18-3.el9.i686 : Compatibility library providing legacy API functions
Repo        : rhel-9-for-x86_64-appstream-rpms
Matched from:
Provide    : libcrypt.so.1

And finally I installed the package, restarted the agents and whalla! All is good in the world of Veeam B&R again.

Code: Select all

dnf install libxcrypt-compat

Hopefully this will save someone else some time.

[Mildur]

Hello mikeg5

Thanks for the solution. Did you by any chance have checked this issue with our customer support team?

Best,
Fabian

[mikeg5]

I did not, I solved this one on my own.

[d3nz]

Hello. This issue appearing from time to time on different proxy servers with RHEL 8.7 at VBR 12.0.0.1420 P20230718. Was it fixed at any release?

[Sturniolo]

Hi d3nz,

Thank you for sharing this information. I have reached out to our team to seek further clarification.

[Sturniolo]

In Linux operating systems like RHEL 8/9, it's essential to install specific packages as prerequisites for our Linux Proxy components. We are currently reviewing a KB article to update and reflect these package requirements accordingly.

[pirx]

I see this frequently when a proxy was hard rebooted due to power outage etc. No packages are missing, fsck reports clean filesystem. The vddk folders on Linux proxy are then empty. Last time I simply copied the files from a differn proxy as offloads were running.

[d3nz]

@pirx,
Exactly. At proxy servers folder /opt/veeam/transport/vddk_7_0/ after some time loses his content and issue appearing.

[Sturniolo]

Thank you for the updated info. Do you have a support ticket number to reference?