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

Sesam integration: add sesam bin directory to LD_LIBRARY_PATH #1817

Merged
merged 1 commit into from May 28, 2018
Merged

Sesam integration: add sesam bin directory to LD_LIBRARY_PATH #1817

merged 1 commit into from May 28, 2018

Conversation

abbbi
Copy link
Contributor

@abbbi abbbi commented May 22, 2018

  • Type: Bug Fix

  • Impact: Normal /

On some systems (for example centos6 and/or ubuntu) REAR backup with Backup type SESAM
fails during verify of the rootfs due to missing libraries:

/opt/sesam/bin/sesam/Crypto.Hash._SHA256.so requires additional libraries (fatal error)
libpython2.7.so.1.0 => not found
/opt/sesam/bin/sesam/cPickle.so requires additional libraries (fatal error)
libpython2.7.so.1.0 => not found
ERROR: ReaR recovery system in '/tmp/rear.LyKD3Rt2V4XgYs2/rootfs' not usable

these libraries are part of the Sesam client integration itself but unfortunately are not found
due to the sesam installation directory not beeing part of LD_LIBRARY_PATH.

For TSM an alike issue has already been fixed as TSM sets the LD_LIBRARY_PATH:

./usr/share/rear/prep/TSM/default/400_prep_tsm.sh:# Find gsk lib diriectory and add it to the TSM_LD_LIBRARY_PATH
./usr/share/rear/prep/TSM/default/400_prep_tsm.sh:      TSM_LD_LIBRARY_PATH=$TSM_LD_LIBRARY_PATH:$gsk_dir

This patch does the same for the sesam client, installation directory is used from the
configuration file and not hardcoded.

@gdha gdha self-assigned this May 23, 2018
@gdha gdha added minor bug An alternative or workaround exists external tool The issue depends on other software e.g. third-party backup tools. labels May 23, 2018
@gdha gdha added this to the ReaR v2.4 milestone May 23, 2018
@gdha gdha requested a review from jsmeix May 23, 2018 11:35
Copy link
Member

@jsmeix jsmeix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now it looks perfectly clean, i.e.
#1810 (comment)
is now fixed.

@gdha gdha merged commit c41e7bb into rear:master May 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external tool The issue depends on other software e.g. third-party backup tools. fixed / solved / done minor bug An alternative or workaround exists
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants