Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Aleph 22: AIK Step 5.3 fails with error message "libcrypto.so.0.9.8: cannot open shared object file: No such file or directory"

    Aleph 22: AIK Step 5.3 fails with error message "libcrypto.so.0.9.8: cannot open shared object file: No such file or directory"

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 22

    Problem Symptoms:
    AIK Step 5.3 fails with the following error message:
    get_ora_passwd: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory
    /exlibris/aleph/a22_1/aleph/exe/rts32: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory


    Cause:
    Defect in the extract_product.sh script.
       The COBOL run-time system (executable file /exlibris/aleph/a22_1/aleph/exe/rts32) is linked to the shared object file libcrypto.so.0.9.8.
    The file libcrypto.so.0.9.8 exists in the directory /exlibris/product/openssl-0.9.8y/lib.
    However, this file is owned by UNIX user ID 501 and group dba. Its file mode is 770.
    Therefore UNIX user aleph cannot read this file when trying to execute the program rts32.

    Root cause:
    -----------
    -- AIK Step 4.1 is supposed to install all 3rd-party products for Aleph 22, including OpenSSL.
    -- Line 222 of the script extract_product.sh (called by AIK Step 4.1) is supposed to ensure that UNIX user aleph and group exlibris own all files and subdirectories in the directory /exlibris/product:
    nohup chown -Rh ${exl_prod}:exlibris $PRODUCT_DIR 2>>$log &
    -- However, in lines 47 - 49 of the script extract_product.sh the variable $exl_prod is set to the value aleph22:
    if [ "$exl_prod" = "aleph" ] ; then
    exl_prod="$exl_prod$ALEPH_VERSION"
    fi

    -- There is no UNIX user aleph22 on the server. Therefore the command chown fails and prints the following error message to the AIK log file /exlibris/ftp_from_exlibris/AIK22/log/aleph_installation_kit.log:
    Thu Mar 27 15:40:55 CDT 2014 Step ikit_4_1 [ Done ]
    nohup: appending output to `nohup.out'
    nohup: appending output to `nohup.out'
    chown: invalid user: `aleph22:exlibris'

    This is a bug in the script extract_product.sh of the AIK.

    Resolution:
    Workaround:

    (1)
    Make UNIX user aleph and group exlibris own all files and subdirectories in the directory /exlibris/product by executing the following command as UNIX user root:
    # chown -Rh aleph:exlibris /exlibris/product

    (2)
    Execute AIK Step 5.3 again.
    Correction made in the kit to extract_product.sh as of Apr 1, 2014.


    • Article last edited: 4/16/2014
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Aleph 22: AIK Step 3.3 fails with error message "ERR: Oracle software versions are different on the target and source servers"
      • Aleph 22: Can't show search results from GUI z39.50 search, closeconnection parameter
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 22
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved