Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NBU libs in /usr/openv/netbackup/sec/at/lib not included #2105

Closed
ofalk opened this issue Apr 2, 2019 · 13 comments
Closed

NBU libs in /usr/openv/netbackup/sec/at/lib not included #2105

ofalk opened this issue Apr 2, 2019 · 13 comments
Assignees
Labels
enhancement external tool The issue depends on non common software e.g. third-party backup tools. fixed / solved / done minor bug support / question
Milestone

Comments

@ofalk
Copy link
Contributor

ofalk commented Apr 2, 2019

  • ReaR version ("/usr/sbin/rear -V"): 2.4

  • OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): RHEL7.6

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

/etc/rear/os.conf:
OS_VENDOR=RedHatEnterpriseServer
OS_VERSION=7

/etc/rear/local.conf:
OUTPUT=ISO
OUTPUT_URL=file:///var/lib/rear/output/
BACKUP=NBU
COPY_AS_IS_EXCLUDE_NBU=( "/usr/openv/netbackup/logs/*" "/usr/openv/netbackup/bin/bpjava*" /usr/openv/netbackup/bin/xbp /usr/openv/netbackup/bin/private /usr/openv/lib/java /usr/openv/lib/shared/vddk /usr/openv/netbackup/baremetal )
export TMPDIR=/var/tmp
  • Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): n/a

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): x86_64

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): n/a

  • Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe): n/a (I guess you want this template to read 'local disk', not 'lokal disk' :-))

  • Description of the issue (ideally so that others can reproduce it):
    While running rear mkrescue -v, it reports the following

<snip>
There are binaries or libraries in the ReaR recovery system that need additional libraries
/usr/openv/lib/plugins/libauthpam_t.so requires additional libraries
        libvrtsat_t.so => not found
ReaR recovery system in '/var/tmp/rear.NMVYmoi2gx7hvX0/rootfs' needs additional libraries, check /var/log/rear/rear-hostname.log for details
</snip>
  • Workaround, if any:

Currently we're checking if setting NBU_LD_LIBRARY_PATH to the following will solve the issue:

NBU_LD_LIBRARY_PATH="/usr/openv/lib:/usr/openv/netbackup/sec/at/lib/"
  • Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files): n/a
@jsmeix jsmeix added support / question external tool The issue depends on non common software e.g. third-party backup tools. labels Apr 2, 2019
@jsmeix
Copy link
Member

jsmeix commented Apr 2, 2019

I do not use NBU (Symantec/Veritas NetBackup)
because I do not have any kind of proprietary software
like third-party backup tools.

Perhaps
#1907 (comment)
could help here as a workaround?

Perhaps this issue here has the same root cause as
#1974
that is fixed via
#1980

How to try out our current ReaR GitHub master code
where #1980 is merged:

Basically "git clone" our current ReaR upstream GitHub master code
into a separated directory and then configure and run ReaR
from within that directory like:

# git clone https://github.com/rear/rear.git

# mv rear rear.github.master

# cd rear.github.master

# vi etc/rear/local.conf

# usr/sbin/rear -D mkbackup

Note the relative paths "etc/rear/" and "usr/sbin/".

@ofalk
Copy link
Contributor Author

ofalk commented Apr 15, 2019

Hi!
Sorry for not getting back to you earlier.
My customer reported that adding the following to the configuration fixed the situation.

NBU_LD_LIBRARY_PATH="/usr/openv/lib:/usr/openv/netbackup/sec/at/lib/"

Maybe you can integrate this?! Or shall I provide the merge request?

@jsmeix jsmeix added this to the ReaR v2.6 milestone Apr 15, 2019
@jsmeix
Copy link
Member

jsmeix commented Apr 15, 2019

@rmetrich
I dared to assign this issue to you because
you had worked on #1974

#2105 (comment)
is about to change default.conf
from

NBU_LD_LIBRARY_PATH="/usr/openv/lib"

to

NBU_LD_LIBRARY_PATH="/usr/openv/lib:/usr/openv/netbackup/sec/at/lib/"

The question (that I cannot answer) is whether or not
adding /usr/openv/netbackup/sec/at/lib/ to NBU_LD_LIBRARY_PATH
by default could have unwanted side-effects (a.k.a. regressions) elsewhere.

@ofalk
Copy link
Contributor Author

ofalk commented Apr 15, 2019

@jsmeix Thanks for pulling in the right person.

@rmetrich
Copy link
Contributor

rmetrich commented Apr 15, 2019 via email

@ofalk
Copy link
Contributor Author

ofalk commented Apr 17, 2019

Created PR for this. Let me know if you need anything additionally changed/done, etc.

gdha added a commit that referenced this issue Apr 17, 2019
@jsmeix jsmeix modified the milestones: ReaR v2.6, ReaR v2.5 Apr 17, 2019
@jsmeix
Copy link
Member

jsmeix commented Apr 17, 2019

With #2122 merged
I consider this issue to be fixed.

@ofalk
thank you for your pull request with the fix!

@jsmeix jsmeix closed this as completed Apr 17, 2019
@jsmeix
Copy link
Member

jsmeix commented Apr 17, 2019

Via
2377d69
I added a comment to default.conf that tells why /usr/openv/netbackup/sec/at/lib/
is needed in NBU_LD_LIBRARY_PATH

@ofalk
Copy link
Contributor Author

ofalk commented Apr 17, 2019

Awesome - thanks for the prompt replies and merge!
@jsmeix No problem - that was low hanging fruit!

@pcahyna
Copy link
Member

pcahyna commented Jul 15, 2022

@ofalk do you know if there was there any reason to add the trailing slash? (Other entries do not have it, so I would prefer to be consistent.)

@ofalk
Copy link
Contributor Author

ofalk commented Jul 19, 2022

@pcahyna I don't think there was any special reason to use trailing slash - I think it was just the preference of my customer back then and I used it as it is, given they had tested it that way.

@pcahyna
Copy link
Member

pcahyna commented Jul 25, 2022

@ofalk thanks, I have another customer who tested it with the slash removed, so I will submit a PR to remove it for consistency.

@ofalk
Copy link
Contributor Author

ofalk commented Jul 25, 2022

@pcahyna Sure!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement external tool The issue depends on non common software e.g. third-party backup tools. fixed / solved / done minor bug support / question
Projects
None yet
Development

No branches or pull requests

4 participants