[Koha] Creating a Z39.50 Target - No connection

[Craig Butosi]

Hi all,

Robin, thank you for the clarification about iptables.

After setting the port back to 9999 in koha-conf.xml under root (which in hindsight, I was not doing :( ), and restarting Zebra, I've been able to telnet to that port successfully using <telnet localhost 9999> , it shows as being connected.

Yaz-client also shows the following,

        Connecting...OK.
        Sent initrequest.
        Connection accepted by v3 target.
        ID     : 81
        Name   : Zebra Information Server/GFS/YAZ
        Version: 4.2.18 cc3abee6f861d0166bef5333b1fc72fbdc8bd94c
        Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets
        Elapsed: 0.001692

Also, when navigating to library.craigbutosi.ca:9999, it displays the following, which was not there prior to doing the above:

        This XML file does not appear to have any style information associated with it. The document tree is shown below.
        <zs:explainResponse><zs:version>1.1</zs:version><zs:record><zs:recordSchema>http://explain.z3950.org/dtd/2.0/</zs:recordSchema><zs:recordPacking>xml</zs:recordPacking><zs:recordData><explain><serverInfo><host>__ZEBRA_SRU_HOST__</hos        t><port>__ZEBRA_SRU_BIBLIOS_PORT__</port><database>biblios</database></serverInfo></explain></zs:recordData></zs:record></zs:explainResponse>


Looks like I'm closer to being up and running.

Many thanks everyone!

Best,

Craig Butosi, MA, MLIS, B Mus (Hons.)
LIBRARY SERVICES MANAGER
THE ROYAL CONSERVATORY
TELUS Centre for Performance and Learning
273 Bloor Street West
Toronto, ON M5S 1W2
416.408.2824 x338
www.rcmusic.ca


-----Original Message-----
From: Koha [mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of Robin Sheat
Sent: April-07-15 9:46 PM
To: koha at lists.katipo.co.nz
Subject: Re: [Koha] Creating a Z39.50 Target - No connection

Craig Butosi schreef op wo 08-04-2015 om 01:29 [+0000]:
> to no effect. Still unable to connect to 210
>
> Also tried to telnet using sudo telnet localhost:210, to which I get
> the following error
> telnet: could not resolve localhost:210/telnet: Name or service not
> known

Your syntax is wrong:

telnet localhost 210

> Three things of note:
>
> 1. I noticed that when checking the iptables, nothing is listed as listening in on port 210, but port 80 and 8080 are listed (OPAC and Staff Client, respectively). How would I open port 210 with iptables? I'm not sure what I should do.

Ignore iptables, you're likely to make things worse. If the process isn't listening, no amount of messing with firewall rules is going to make it show up. iptables --list will show you what rules actually exist.

Also, iptables doesn't tell you about things that are listening anyway.
For that you want:

sudo netstat -lp --inet

> I/O warning : failed to load external entity "/etc/koha/sites/library/__KOHA_CONF_DIR__/zebradb/explain-biblios.xml"
> 21:04:47-07/04 [fatal] Failed to bind to tcp:@:210 [Permission denied]

This is your key thing that you need to be noticing. You don't have permissions to bind on that port, you need root to bind to ports <1024, so try for a different number and see if that works.

--
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5FA7 4B49 1E4D CAA4 4C38  8505 77F5 B724 F871 3BDF

_______________________________________________
Koha mailing list  http://koha-community.org Koha at lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha


Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.