Re: [greenstone-devel] z39.50

From John R. McPherson
DateTue, 2 Sep 2003 13:43:06 +1200
Subject Re: [greenstone-devel] z39.50
In-Reply-To (OF70AA0179-9A469CE3-ON69256D95-000557ED-69256D95-00055831-ntu-edu-au)
On Tue, Sep 02, 2003 at 10:28:22AM +0930, wrote:
> Hi,
> We are trying to get z39.50 going.
> Our system is Greenstone 2.40 running under Redhat Linux with Apache 1.3.27
> I believe we have compiled it correctly and as far as I can tell fast-cgi
> is off. (I have checked the config.log - it is at the end of this email)
> I have tried using tcptrace (
> to monitor requests from greenstone by changing the address in the
> z3950.cfg file to refer to my pc and using tcptrace to redirect it to the
> server (I tried for both LOC and our site) and in the process have
> discovered that not a peep is coming from greenstone.
> Any idea what we are doing wrong?

Check that the compiled library binary has z3950 support: if you do
$ strings library | grep z39
you will get "z3950proto" as the only string in a stock standard library,
and a couple of other different symbols if the server includes z3950 support.
Eg if I do this, I get:
z39.50: couldn't find collection
z3950 filter query: error connecting to server
z39.50 server (ie target). Most likely this was a
Malloc failed while initialising z39.50 server

If that's not in it, did you do a make clean or make distclean before
doing the ./configure --enable-z3950, if you had previously compiled a
standard library? Check that the gsdl/src/recpt/Makefile has
"USE_Z3950 = 1" at the top of it (meaning that the configure got it

If those strings in the library, did you remember to install or otherwise
copy the library executable into the right place for your webserver?

> -tail of my z3950.cfg file--
> dynix
> "Charles Darwin University z39.50 Server"
> About "This is the z39.50 interface to the CDU Library catalogue"

This setting works for me - I get "server online", and I can search
the catalog.

You could check that there aren't any errors in the config file - these
get logged to the etc/z3950log.txt file, assuming the web server can
write to/create that file. Parse errors get written here, for example.

Lastly, I notice that the z3950 support in recent releases of greenstone
is slightly broken - the navigation bar doesn't include a link to the
Search button, which makes the z3950 support a bit useless. I'll look
into this and see what the reason for this is!

(You can get to the search page manually by pointing a web browser at