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. New version 21 GUI: "Library ABC01 is not defined on the server."

    New version 21 GUI: "Library ABC01 is not defined on the server."

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Description
    2. Resolution

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description

    Description:
    After installing the GUI as part of the upgrade to version 21, we get a message "Library ABC01 is not defined on the server."

    UTIL W/1/1 shows no server activity. There is no activity in the PC_server log but some of the other logs show errors--most of them show binding stream socket--address already in use.
     

    Resolution


    ls -lrt in $LOGDIR shows:

    aleph@library(a21_1) ABC01> ls -lrt pc*
    -rw-rw-r-- 1 aleph exlibris 0 Aug 7 10:31 pc_server_6991.log.0708.122752
    -rw-rw-r-- 1 aleph exlibris 0 Aug 7 12:27 pc_server_6991.log.0708.1227
    -rw-rw-r-- 1 aleph exlibris 0 Aug 7 12:27 pc_server_6991.log.0708.1235
    -rw-rw-r-- 1 aleph exlibris 0 Aug 7 12:35 pc_server_6991.log.0708.1321
    -rw-rw-r-- 1 aleph exlibris 0 Aug 7 13:21 pc_server_6991.log.0708.1441
    -rw-rw-r-- 1 aleph exlibris 0 Aug 7 14:41 pc_server_6991.log



    and util w/3/4 (PC Server) shows:

    | Port | Pid | Server Type | Started At | Status
    |---------|---------|-----------------|-----------------|--------------------

    Enter CR to continue...



    This, in combination with "binding stream socket--address already in use" led me to this:

    aleph@library(a21_1):~>ps -ef | grep 6991
    aleph 3732 1 0 Apr04 ? 00:00:00 csh -f /exlibris/aleph/a21_1/aleph/proc/pc_server 6991
    aleph 3809 3732 0 Apr04 ? 00:00:05 /exlibris/aleph/a21_1/aleph/exe/pc_server_main 0 6991
    aleph 3957 3809 0 Apr04 ? 00:00:00 /exlibris/aleph/a21_1/aleph/exe/pc_server_main 0 6991
    aleph 3960 3809 0 Apr04 ? 00:00:00 /exlibris/aleph/a21_1/aleph/exe/pc_server_main 0 6991
    aleph 3962 3809 0 Apr04 ? 00:00:00 /exlibris/aleph/a21_1/aleph/exe/pc_server_main 0 6991
    aleph 3964 3809 0 Apr04 ? 00:00:00 /exlibris/aleph/a21_1/aleph/exe/pc_server_main 0 6991
    aleph 3965 3809 0 Apr04 ? 00:00:00 /exlibris/aleph/a21_1/aleph/exe/pc_server_main 0 6991


    > ps -ef | grep server

    shows other processes still running from April 04.

    This is like KB's 16384-26706 and 4549.

    You can do one of two things: 

    1. kill all of these Apr04 processes individually and start the servers, or

    2. reboot the server

    The latter is probably better, since that may clean up other problem processes as well.

    [From site: The reboot cleared up these problems.]

     


    • Article last edited: 28-Feb-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • New vendor record error: "co1043 - duplicate nn - Vendor does not exist".
      • New VerUtil.exe (backward-)compatible with Aleph 20.1.2 (SP 2539)
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      This page has no tags.
    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