Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    /etc/init.d/exlibris script doesn't start (or stop) Aleph processes

    • Article Type: General
    • Product: Aleph
    • Product Version: 22

    Problem Symptoms:
    After changing the owner of the Aleph 22 software from the unix user aleph to UNIX user aleph22, the script /etc/init.d/exlibris does not start (or stop) the Aleph 22 processes.

    The third parameter in the file /exlibris/startup/init.dat, which is the owner of the Aleph nn software on this server, has "aleph" when it should have "alephnn", that is:


    when it should have:


    See Additional Information (below) for detailed information.

    Change the third parameter (the owner) in the aleph line in /exlibris/startup/start_stop from "aleph" to "alephnn".

    Additional Information

    1. The script /etc/init.d/exlibris calls the script /exlibris/startup/start_stop. The script /exlibris/startup/start_stop determines the owner of the Aleph software from the file /exlibris/startup/init.dat in the following way:

    while read line
    if 1st field = "Y" and 2nd field = "aleph"
    then Aleph owner = 3rd field


    --------> UNIX user aleph is the owner of the Aleph 22 software.

    2. On the customer's server the file /exlibris/startup/init.dat may include the following line:


    Hence the script /exlibris/startup/start_stop would try to start the Aleph 22 processes as UNIX user aleph.
    However, this attempt would fail because the owner of the Aleph 22 software on the customer's server is UNIX user aleph22.

    3. Usually AIK Step 5.6 "Update auto startup/shutdown script" determines the owner of the Aleph 22 software by evaluating the variable $MAIN_USER which is set in the file /exlibris/ftp_from_exlibris/AIK22/param_bash.ini.

    Then AIK Step 5.6 adds the owner of the Aleph 22 software to the relevant line in the file /exlibris/startup/init.dat.

    Category: System Management (500)

    • Article last edited: 7/30/2014