EMS startup error - "Unable to locate libcrypto.so".

EMS startup error - "Unable to locate libcrypto.so".

book

Article ID: KB0094024

calendar_today

Updated On: 01-13-2017

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Description:
This error is seen after starting the EMS server.


Using module path = /usr/app/tibco/ems/8.2/bin/lib/64:/usr/app/tibco/ems/8.2/lib/64
Loaded /usr/app/tibco/ems/8.2/lib/64/libz.so
Unable to locate libcrypto.so

Symptoms:

Cause:

Issue/Introduction

EMS startup error - "Unable to locate libcrypto.so".

Resolution

Beginning with EMS 5.1, the EMS daemon is no longer statically linked. The library is located in the following two folders:

<EMS root>/lib

<EMS root>/lib/64


EMS uses the value of EMS_HOME to find the library and adds /lib and /lib/64 to the value of EMS_HOME. This is the correct value of EMS_HOME. In the case where the "Unable to locate libcrypto.so" error is seen, check the value of EMS_HOME with the “env” or “set” command. If the value of EMS_HOME is incorrect, the value should be removed or set to <TIBCO_HOME>/ems/<EMS_Version>. For example:


EMS_HOME=/tibco/ems/5.1


It may be possible that the EMS daemon starts successfully for one user but not others. In this case, for the user that is not available to start the EMS daemon, the following can be used:


export EMS_HOME=<TIBCO_HOME>/ems/<EMS_Version>


In the case, EMS_HOME is not defined. The issue may be fixed by adding the following to LIBPATH (AIX), LD_LIBRARY_PATH (SOLARIS-LINUX) or SHLIB_PATH (HP-UX).


“<TIBCO_HOME>/ems/<EMS_Version>/lib” or “<TIBCO_HOME>/ems/<EMS_Version>/lib/64”