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

    Client gets message "z39.50 gate not running"

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

    We are testing the 18 to 19 upgrade and I find that I can't search a z39.50 target from the within the v.19 client. After selecting a z39.50 target in the "Base" selection list of the Search tab in the Cataloging client and trying to perform a search the error message "z39.50 gate is not running" displays. I verified with Util W that the z39_gate was running and also stopped and restarted it to see if that would make a difference (also stopped and restarted the pc_server to be sure). So far nothing has fixed the problem. In the pc_server log I see the following:

    SERVICE : C1011
    MODULE : OPAC Services
    DESCRIPTION: Send Find Request
    ACTION :
    PROGRAM : pc_sear_c1011

    connect: No route to host

    The "connect: No route to host" is particularly interesting. What does that error mean in the pc_server log? I have tried several institutions and so far they all are having the same problem.

    Also, looking at the log for the z39_gate there seems to be no indication at all that it was communicated with by the client after I try to perform a z39.50 search.

    I found this in aleph_start:

    setenv Z39_HOST aserv33

    However, when I echo $HOST, I get this:

    >>echo $HOST

    Your Z39_HOST definition in aleph_start is defined incorrectly. aserv33 is a different server hosing your Oracle application. I found this in your aleph_start:

    setenv ORA_HOST aserv33

    You need to change the Z39_HOST definition to:

    setenv Z39_HOST aserv32

    In other cases the entry in aleph_start for Z39_HOST must be changed to the internal server address (don't use the the external address). 

    • Article last edited: 10/8/2013
    • Was this article helpful?