vxesd failed to start because of error: ld.so.1: vxesd: fatal: libHBAAPI.so.1: open failed:No such file or directory .

 

This error was observed after the VxVM 5.0MP1RP5 patch was installed on Solaris 8 systems.

 

vxesd has been modified to use the shared library from the OSlibHBAAPI.so.1 instead of the one provided by the VxVM. This results in the vxesd failure at its starting attempt if this library is not installed into the system.

 

Solaris: The version 2.0 shared library libHBAAPI.so is available on Solaris 8, 9, 10 andx86 on build environments and most test machines (some older releases of 8 need to be patched)

AIX: The version 2.0 shared library libHBAAPI.a is available on AIX 5.2, 5.3, 6.1 on both the build environment and test machines

HP: Only version 1.0 shared library libHBAAPI.sl is available on test machines but the build environment does not contain it.

Linux: Most machines, including build and test machines don't have libHBAAPI.* in both static or shared flavors.

 

Solaris: use shared library provided by the OS

AIX: use shared library provided by the OS

HP:use the static library present on unixvm-cvs tree (vxesd requires version2.0)

Linux: use the static library present on unixvm-cvs tree

 

Sol 8----- 113766-05

Sol 9----- 114477-04

Sol 10----- 120346-09 (for X86: 120347-09)

 

The CPI team is aware of this fact and is working to let the installation script raising up a "missing dependency" message halting the installation process if the libHBAAPI won't be found onto the system which is being installed. So far though the only way to work the issue out is to install the OS libHBAAPI onto the system. Int his specific case installing the 113766-05 patch onto his systems the customer was able to let vxesd start and work fine.