- Veeam Support Knowledge Base
- Unable to use Veeam Agent for IBM AIX after LIBPATH variable has been changed
Unable to use Veeam Agent for IBM AIX after LIBPATH variable has been changed
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
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:
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 (blank) value before running Veeam Agent for IBM AIX binaries.
- 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.
- Create an SH file that will set the LIBPATH to blank for starting the service, then make that sh file executable.
- Create the following file: /opt/veeam/bin/libpath.sh
- Add the following content to the file:
#!/usr/bin/sh
LIBPATH= /opt/veeam/bin/veeamservice
Note: There is a blank space after
LIBPATH=
- Make the file executable:
chmod +x /opt/veeam/bin/libpath.sh- Stop the veeamsvc service and remove it.
stopsrc -s veeamsvc
rmssys -s veeamsvc- Add the service with the new SH file and then start the service.
mkssys -s veeamsvc -R -p /opt/veeam/bin/libpath.sh -u 0 -S -n15 -f9
startsrc -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 recreated as documented in steps 3 and 4.
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
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.