Error "safex: error while loading shared libraries: libZThread-2․3․so․2" during EEM policy upgrade after upgrading to AAI 24.4

Products

• Automation Analytics & Intelligence

Issue/Introduction

Users upgrading Automation Analytics & Intelligence to version 24․4 may encounter a shared library loading error when executing EEM configuration scripts during the upgrade process․​​​​​‌​​‍ This issue prevents the eEMConfigUpgrader․sh or eEMUsers Migration․sh scripts from running successfully because the safex binary cannot locate required system files․

ERROR MESSAGE: "safex: error while loading shared libraries: libZThread-2․3․so․2: cannot open shared object file: No such file or directory Error: safex command failed with exit code 127"

SYMPTOMS:

• Running eEMConfigUpgrader․sh fails immediately

• Running eEMUsers Migration․sh fails immediately

• The system reports a missing libZThread-2․3․so․2 file

CONTEXT: This occurs on Linux EEM platforms during the AAI 24․4 post upgrade steps to update the EEM polcies

IMPACT: Users cannot complete the EEM policy migration or configuration upgrade, delaying the overall AAI environment upgrade․

Environment

Automation Analytics & Intelligence Integration

EEM

Resolution

PREREQUISITES:

• Access to the AAI installation media/scripts

• Access to the EEM installation directory

• Sufficient permissions to export environment variables

STEPS:

1․ IDENTIFY THE LIBRARY LOCATION: Locate the missing libZThread-2․3․so․2 file within your EEM installation directory․ It is typically located in the bin or lib subfolders of the EEM home path․

Path Example: /opt/CA/SharedComponents/EmbeddedEntitlementsManager/bin

2․ SET THE LIBRARY PATH: Add the EEM bin and lib directories to the LD_LIBRARY_PATH environment variable in your current terminal session․ This allows the safex binary to find the required libraries at runtime․

Command: export LD_LIBRARY_PATH=[EEM_HOME]/bin:[EEM_HOME]/lib:$LD_LIBRARY_PATH

Note: Replace [EEM_HOME] with your actual EEM installation path (e․g․, /opt/CA/SharedComponents/EmbeddedEntitlementsManager)․

3․ VERIFY AND EXECUTE SCRIPTS: Confirm the variable is set and then re-run the failed EEM script․

Command: echo $LD_LIBRARY_PATH ․/eEMConfigUpgrader․sh [parameters]

VERIFY SUCCESS:

• The safex command authenticates successfully

• The script proceeds to export or import EEM objects without library errors

• The message "OK: Successfully Authenticated" appears in the output