SAS Enterprise Guide connected to a Linux Remote Machine LD_LIBRARY_PATH Environment variables

[kh4]

Hi,

We are having some LD_LIBRARY_PATH issues. SAS Enterprise Guide connected  to a remote Linux machine . Would like to know from which location on the remote machine does SAS EG set up its LD_LIBRARY_PATH env variables? please advise.

[gwootton]

The Workspace Server script (<SASConfig>/Lev1/SASApp/WorkspaceServer/WorkspaceServer.sh) sources a number of files that can affect the final value of LD_LIBRARY_PATH if modified. (WorkspaceServer_usermods.sh, appservercontext_env_usermods.sh, level_env_usermods.sh, <SASHome>/SASFoundation/9.4/bin/sasenv_local). While no modifications should be made to the non usermods suffixed files they are also sourced and could also be making changes.

I think by default (no modifications made to the usermods files) this would only come from <SASHome>/SASFoundation/9.4/bin/sasenv, where it adds some JAVA_HOME and SASHOME paths to whatever is currently set as LD_LIBRARY_PATH.

[Sajid01]

Hello @kh4 
To your question "Would like to know from which location on the remote machine does SAS EG set up its LD_LIBRARY_PATH env variables?"
This is typically setup at [SASHome]/SASFoundation/9.4/bin/sasenv_local.
What was the error ? Can you please share it?

[kh4]

When executing X commands for transfer protocols like Rsync, SFTP, Scp , PIPE on EG  seeing below error

ssh: symbol lookup error: /lib64/libgssapi_krb5.so.2: undefined symbol: k5_internalize_principal, version krb5_3_MIT
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: remote command not found (code 127) at io.c(226) [sender=3.1.3

[kh4]

Thanks @gwootton  for your response.  LD_LIBRARY_PATH env variable are being set from SASHome>/SASFoundation/9.4/bin/sasenv_local , but the issue is there  are some additional Paths which are being appended to LD_LIBRARY_PATH on EG.

[gwootton]

The way things get appended to LD_LIBRARY_PATH is you have something in one of those files I mentioned that says:
export LD_LIBRARY_PATH=/some/new/path:$LD_LIBRARY_PATH
or
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/some/new/path

It is also possible to set environment variables using an options statement or -set option.

If you run the WorkspaceServer.sh command directly with -nodms, and run
%put %sysget(LD_LIBRARY_PATH);
does the LD_LIBRARY_PATH value contain the additions?

If so, try editing WorkspaceServer.sh and uncommenting the "set -x" command at the top and run again. This will show in the terminal display each file it is sourcing and the commands being run.

[Sajid01]

Hello @kh4 
Please have a look here https://access.redhat.com/solutions/6968539