Unable to use Veeam Agent for IBM AIX after LIBPATH variable has been changed

KB ID: 4273
Product: Veeam Agent for IBM AIX | 1.0 | 2.0 | 3.0 | 4.0
Published: 2022-01-18
Last Modified: 2022-07-07
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

In IBM AIX, it is possible to change the LIBPATH variable globally. However, doing so overrides the library loader domain configuration for all the applications running with system environment on that machine. If the LIBPATH is set to anything other than blank (default), the Veeam Agent for IBM AIX 'veeamconfig' and 'veeamsvc' will fail to operate. 

Example:
# LIBPATH=/usr/lib /opt/veeam/bin/veeamconfig
Could not load program /opt/veeam/bin/veeamconfig:
Could not load module /opt/veeam/lib/libVmbPlatformLib.so.
        Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not be loaded.
        Member libiconv.so.2 is not found in archive
Could not load module veeamconfig.
        Dependent module /opt/veeam/lib/libVmbPlatformLib.so could not be loaded.
Could not load module .

Solution

To resolve this, implement the workaround below, which will set the LIBPATH variable to an empty value before running Veeam Agent for IBM AIX binaries.
  1. Create an alias for veeamconfig, so that when it is called it will operate with an empty LIBPATH:
alias veeamconfig="LIBPATH= /opt/veeam/bin/veeamconfig"
To preserve this alias so it is not lost on reboot, it should be added to .bash_profile, .bashrc, or one of the system-wide equivalents /etc/profile and /etc/bashrc.
  1. Adjust the environment for the veeamsvc system service. To do so run these two commands as root:
rmitab veeamsvc
mkitab veeamsvc:23456789:once:'/usr/bin/startsrc -s veeamsvc -e LIBPATH='
To finalize the changes restart veeamsvc service:
stopsrc -s veeamsvc
startsc -s veeamsvc
With these changes in place, the product will operate despite the LIBPATH set system-wide to any other value.
After every Veeam Agent upgrade, the veeamsvc must be reconfigured as documented in Step 2.

Updating crontab for Scheduled Jobs

After configuring scheduled jobs, you will need to manually edit the crontab entries using the "crontab -e" command. The entries from crontab will need to have "LIBPATH=" before the veeamconfig command, as shown in this example:

00 7 * * * LIBPATH= veeamconfig job start --id {GUID} --retriable --scheduled --highpriority > /dev/null
Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.