DE527148: CABI 7.9.x: CABI deployment fails due to Postgres Installation error (19032) on RHEL/CentOs 8.4+
search cancel

DE527148: CABI 7.9.x: CABI deployment fails due to Postgres Installation error (19032) on RHEL/CentOs 8.4+

book

Article ID: 234170

calendar_today

Updated On:

Products

CA Spectrum DX NetOps CA Performance Management - Usage and Administration

Issue/Introduction

When installing CABI Jaspersoft 7.9.1 the install fails with a Postgres Installation error (19032). Below is a more detailed error message from the installation log:

DEBUG CABIProcessBuilder.cabiProcess():70 - Creting the processbuilder object
DEBUG CABIProcessBuilder.cabiProcess():74 - Setting the processbuilder directory to /opt/CABI/postgresql
DEBUG CABIProcessBuilder.cabiProcess():78 - Starting the process
DEBUG CABIProcessBuilder.cabiProcess():80 - Waiting for the process to finish
DEBUG CABIProcessBuilder.cabiProcess():82 - Process exit value is 127
NFO CABIProcessBuilder.cabiProcess():86 - cabiProcess method returned with value-127
ERROR ConfigurePostgresql.changePwd():184 - Error in configuring the postgresql database user127
ERROR ComponentInstall.startPostgresql():510 - Error in starting postgresql database
ERROR CABIUtil.printCABIException():109 - ErrorCode : 19032 ErrorMessage :
ERROR CABIUtil.printCABIException():109 - ErrorCode : 19033 ErrorMessage :
DEBUG ProgressThread.run():88 - Error code from component install is: 1
DEBUG ProgressThread.run():90 - Getting the error codes list from CABIInstallException object
INFO ProgressThread.run():93 - Error code is: 19032
DEBUG ProgressThread.run():95 - Error key is: ERROR_STARTING_POSTGRESQL
DEBUG ProgressThread.run():97 - Error message is: Error while starting postgreSQL database
INFO ProgressThread.run():103 - 1

Environment

DX Netops 21.2.8, 22.2.x

CABI 7.9.X

Cause

Missing libreadline.so.6 library.
Execute below command to verify:

# ls -lar /usr/lib64/libreadline.so*
-rwxr-xr-x. 1 root root 335808 Aug 12  2018 /usr/lib64/libreadline.so.7.0
lrwxrwxrwx. 1 root root     18 Aug 12  2018 /usr/lib64/libreadline.so.7 -> libreadline.so.7.0

Resolution

In the command line create a link with the name "libreadline.so.6" pointing to the existing in CentOS 8.4 libreadline.so.7:

# ln -s /usr/lib64/libreadline.so.7.0 /usr/lib64/libreadline.so.6

 

Verify the result; all shared libraries should be listed as resolved, including the libreadline.so.6:

# ldd /opt/CA/SharedComponents/CA\ Business\ Intelligence/postgresql/bin/psql
        linux-vdso.so.1 (0x00007ffc0ccf6000)
        libpq.so.5 => /lib64/libpq.so.5 (0x00007f3e9e04c000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f3e9de2c000)
        libreadline.so.6 => /lib64/libreadline.so.6 (0x00007f3e9dbdd000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f3e9d9d5000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f3e9d653000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f3e9d28e000)
        libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007f3e9cffa000)
        libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007f3e9cb11000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f3e9c8bc000)
        libldap_r-2.4.so.2 => /lib64/libldap_r-2.4.so.2 (0x00007f3e9c664000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f3e9e29e000)
        libtinfo.so.6 => /lib64/libtinfo.so.6 (0x00007f3e9c437000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f3e9c21f000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f3e9c01b000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f3e9bd31000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f3e9bb1a000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f3e9b916000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f3e9b705000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f3e9b501000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f3e9b2ea000)
        liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f3e9b0da000)
        libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f3e9aebc000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f3e9ac92000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f3e9aa69000)
        libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f3e9a7e5000)

 

Optional:

If you still see some not found libraries, like in the below case:

# ldd /opt/CA/SharedComponents/CA\ Business\ Intelligence/postgresql/bin/psql
        linux-vdso.so.1 (0x00007ffea8bd3000)
        libpq.so.5 => not found
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fef5d043000)
        libreadline.so.6 => not found
        librt.so.1 => /lib64/librt.so.1 (0x00007fef5ce3b000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fef5cab9000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fef5c6f3000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fef5d263000)

The solution is:

  • libreadline.so.6 => not found
    • # ln -s /lib64/libreadline.so.7.0 /lib64/libreadline.so.6
  • libpq.so.5 => not found 
    • yum install postgresql-libs


-----------------------------------------------------------

UPDATED: 

You can face the following error after executing all the procedure mentioned above, when trying to run the CABI installer:

root@xxxxxxxx]# ./setup.sh -f cabi_install.properties -i silent

Installation started. Please refer latest the log file in temp directory which starts with CABusinessIntelligence_install.
awk: error while loading shared libraries: /lib64/libreadline.so.7: file too short
awk: error while loading shared libraries: /lib64/libreadline.so.7: file too short

This means that the libreadline.so.7 library was somehow damaged after running the "ln -s" command to create the link mentioned previously.
This was observed happening with some customers.

So, you can first run the following command to confirm the Linux package that contains this library:

[root@xxxxxxxx]]# yum provides \*/libreadline.so.7

Updating Subscription Management repositories.
Last metadata expiration check: 1:03:31 ago on Wed 26 Apr 2023 01:34:35 PM UTC.

readline-7.0-10.el8.x86_64 : A library for editing typed command lines
Repo        : @System
Matched from:
Filename    : /usr/lib64/libreadline.so.7

readline-7.0-10.el8.x86_64 : A library for editing typed command lines
Repo        : rhel-8-for-x86_64-baseos-rpms
Matched from:
Filename    : /usr/lib64/libreadline.so.7


Then, just run the following command to reinstall the related package:

[root@xxxxxxxx]# yum reinstall readline-7.0-10.el8.x86_64


The CABI installer should run fine now.

Additional Information

As you've already attempted an install, to fix this up, do the following:

The sequence of the steps is as follows:

  • Execute the ln command above regarding the missing libreadline.so.6 lib.
  • Clean up the failed CABI installation (If you can revert to a clean system snapshot - that would be perfect as no manual cleaning would be needed).
    • Delete CABI HOME folder (/opt/CA by default)
    • Remove files (if they exist, you can use the locate command):
      • cd ~ (i.e. home folder of the user used for CABI installation)
      • rm -f .cabusinessintelligence

NOTE:  Move the following files to an alternate location (DO NOT DELETE): 

      • .jrsks
      • .jrsksp
      • .jslic  (These files are needed if you have an exported CABI Dataset that has encryption enabled they are needed for the re-import) 
  • Re-run the installation.

Bundled CABI Reports JKS Key error on importing reports

 

Bundled CABI Reports JKS Key error on importing reports

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=205687

Powered by Wolken Software