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_startup not working after SP installation

    aleph_startup not working after SP installation

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

    Description:
    I installed the latest Service Pack on our TEST server. Everything went well, except for the aleph_startup. We get a lot of error messages and Aleph does not restart completely.

    We get that kind of lines :

    /exlibris/aleph/a18_2/aleph/exe/rts32: error while loading shared libraries: libjava.so: cannot open shared object file: No such file or directory
    - ABC30
    /exlibris/aleph/a18_2/aleph/exe/rts32: error while loading shared libraries: libjava.so: cannot open shared object file: No such file or directory
    [1] 26165
    /exlibris/aleph/a18_2/aleph/exe/rts32: error while loading shared libraries: libjava.so: cannot open shared object file: No such file or directory
    - XYZ30

    I know that when I ran util SP4, I got a message about adding lines in aleph_start, but I lost that message and I can't retrieve what line I have to add in aleph_start.

    Resolution:
    Thanks for installing the SP on our TEST server.

    I installed SP 1280 on our PROD server yesterday, using the new util SP procedure. The message that I was looking is is the following :

    Please select [0]: 1
    Are you sure you want to install Service Pack 1280 Y/[N] Y

    Attention: Java support is required for SP installation.
    Please add the lines below to the end of $alephe_root/aleph_start,
    before the final "exit" command.
    Then, run "source $alephe_root/aleph_start" and re-run Service Pack installation:

    if ($unix_name == "LINUX") then
    setenv JAVA_MACHINE i386
    else
    setenv JAVA_MACHINE `uname -p`
    endif

    setenv JAVA_ENABLED TRUE
    setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$JAVA_HOME/jre/lib/$JAVA_MACHINE"
    setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$JAVA_HOME/jre/lib/$JAVA_MACHINE/server"

    press <Enter> to continue

    So I added the relevant lines in aleph_start, installed the Service Pack and got no error messages when I restarted Aleph Services with aleph_startup.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • aleph_startup fails to start batch queues and daemons for certain libraries
      • aleph_startup stops with "aleph_que.c: Permission denied" message for que_batch.old
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 18.01
      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