Creating a Z39.50 Target - No connection
Hi Everyone, I was interested in making my catalogue searchable by turning its <biblios> database into a z39.50 target. I've followed the instructions in my koha-conf.xml file (etc/koha/sites/library/koha-conf.xml), un-commenting the necessary areas. However, going through the Troubleshooting page on the Koha Wiki: http://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server has led to a dead-end. I have my port set to 210 (this is different from the 9999 default for biblios), yet I cannot connect to yaz-client after running yaz-client -c /etc/koha/zebradb/ccl.properties localhost:210/biblios It shows the following error: Connecting...error = System (lower-layer) error: Connection refused Now, I'm wondering if this is a simple case of not opening port 210 on my firewall. I've run the following command, attempting to do this: sudo iptables -A INPUT -p udp --dport 210 -j ACCEPT Yet, this port isn't listed on my server connections (sudo netstat -pn --udp -listen) Can anyone advise, please? (Happy to send the necessary areas of my koha-conf.xml file off-list for diagnosis). Many thanks in advance! Best to all, 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<http://www.rcmusic.ca/> 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.
Hi this is a very silly advice :(, but have you restarted Zebra? changes in koha-conf.xml are not effective until you restart the server, if you have started have you tried telnet localhost 210? Hugo 2015-04-07 19:46 GMT+02:00 Craig Butosi <craig.butosi@rcmusic.ca>:
Hi Everyone,
I was interested in making my catalogue searchable by turning its <biblios> database into a z39.50 target. I've followed the instructions in my koha-conf.xml file (etc/koha/sites/library/koha-conf.xml), un-commenting the necessary areas. However, going through the Troubleshooting page on the Koha Wiki: http://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server has led to a dead-end.
I have my port set to 210 (this is different from the 9999 default for biblios), yet I cannot connect to yaz-client after running
yaz-client -c /etc/koha/zebradb/ccl.properties localhost:210/biblios
It shows the following error:
Connecting...error = System (lower-layer) error: Connection refused
Now, I'm wondering if this is a simple case of not opening port 210 on my firewall. I've run the following command, attempting to do this:
sudo iptables -A INPUT -p udp --dport 210 -j ACCEPT
Yet, this port isn't listed on my server connections (sudo netstat -pn --udp -listen)
Can anyone advise, please? (Happy to send the necessary areas of my koha-conf.xml file off-list for diagnosis).
Many thanks in advance!
Best to all,
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<http://www.rcmusic.ca/>
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. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- *Hugo Agud - Orex Digital * *www.orex.es <http://www.orex.es>* Director Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70 hagud@orex.es · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.
Hi all, Hugo, thank you for the advice ☺ To a novice, no advice is silly! I will look into restarting zebra and try to telnet to 210 later this evening. Thanks very much! 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<http://www.rcmusic.ca/> From: Hugo Agud [mailto:hagud@orex.es] Sent: April-07-15 1:51 PM To: Craig Butosi Cc: koha-user Subject: Re: [Koha] Creating a Z39.50 Target - No connection Hi this is a very silly advice :(, but have you restarted Zebra? changes in koha-conf.xml are not effective until you restart the server, if you have started have you tried telnet localhost 210? Hugo 2015-04-07 19:46 GMT+02:00 Craig Butosi <craig.butosi@rcmusic.ca<mailto:craig.butosi@rcmusic.ca>>: Hi Everyone, I was interested in making my catalogue searchable by turning its <biblios> database into a z39.50 target. I've followed the instructions in my koha-conf.xml file (etc/koha/sites/library/koha-conf.xml), un-commenting the necessary areas. However, going through the Troubleshooting page on the Koha Wiki: http://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server has led to a dead-end. I have my port set to 210 (this is different from the 9999 default for biblios), yet I cannot connect to yaz-client after running yaz-client -c /etc/koha/zebradb/ccl.properties localhost:210/biblios It shows the following error: Connecting...error = System (lower-layer) error: Connection refused Now, I'm wondering if this is a simple case of not opening port 210 on my firewall. I've run the following command, attempting to do this: sudo iptables -A INPUT -p udp --dport 210 -j ACCEPT Yet, this port isn't listed on my server connections (sudo netstat -pn --udp -listen) Can anyone advise, please? (Happy to send the necessary areas of my koha-conf.xml file off-list for diagnosis). Many thanks in advance! Best to all, 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<http://www.rcmusic.ca><http://www.rcmusic.ca/> 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. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha -- Hugo Agud - Orex Digital www.orex.es<http://www.orex.es> Director Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70 hagud@orex.es<mailto:hagud@orex.es> · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema. 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.
Hi all, Update: Restarted zebra with sudo koha-zebra-restart <instancename> 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 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. 2. Here is my koha-conf.xml file (edited out sensitive information): https://www.dropbox.com/s/qk5scpwuv6pibvy/koha-conf.xml?dl=0 . Does anyone see anything out of place? By the way, my instance name is <library>, and I would like to use Port 210 for Z39.50. 3. Log Files: a) On zebra-error.log: 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] b) On zebra-output.log: 20:53:41-24/03 zebrasrv(103) [warn] dfa_parse fail=1 20:53:41-24/03 zebrasrv(103) [warn] dict_lookup_grep fail -1 Not sure if #3 is a clue to what's happening. Any thoughts? Best to all and thanks, 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 ________________________________________ From: Koha [koha-bounces@lists.katipo.co.nz] on behalf of Craig Butosi [craig.butosi@rcmusic.ca] Sent: Tuesday, April 07, 2015 2:21 PM To: Hugo Agud Cc: koha-user Subject: Re: [Koha] Creating a Z39.50 Target - No connection Hi all, Hugo, thank you for the advice ☺ To a novice, no advice is silly! I will look into restarting zebra and try to telnet to 210 later this evening. Thanks very much! 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<http://www.rcmusic.ca/> From: Hugo Agud [mailto:hagud@orex.es] Sent: April-07-15 1:51 PM To: Craig Butosi Cc: koha-user Subject: Re: [Koha] Creating a Z39.50 Target - No connection Hi this is a very silly advice :(, but have you restarted Zebra? changes in koha-conf.xml are not effective until you restart the server, if you have started have you tried telnet localhost 210? Hugo 2015-04-07 19:46 GMT+02:00 Craig Butosi <craig.butosi@rcmusic.ca<mailto:craig.butosi@rcmusic.ca>>: Hi Everyone, I was interested in making my catalogue searchable by turning its <biblios> database into a z39.50 target. I've followed the instructions in my koha-conf.xml file (etc/koha/sites/library/koha-conf.xml), un-commenting the necessary areas. However, going through the Troubleshooting page on the Koha Wiki: http://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server has led to a dead-end. I have my port set to 210 (this is different from the 9999 default for biblios), yet I cannot connect to yaz-client after running yaz-client -c /etc/koha/zebradb/ccl.properties localhost:210/biblios It shows the following error: Connecting...error = System (lower-layer) error: Connection refused Now, I'm wondering if this is a simple case of not opening port 210 on my firewall. I've run the following command, attempting to do this: sudo iptables -A INPUT -p udp --dport 210 -j ACCEPT Yet, this port isn't listed on my server connections (sudo netstat -pn --udp -listen) Can anyone advise, please? (Happy to send the necessary areas of my koha-conf.xml file off-list for diagnosis). Many thanks in advance! Best to all, 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<http://www.rcmusic.ca><http://www.rcmusic.ca/> 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. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha -- Hugo Agud - Orex Digital www.orex.es<http://www.orex.es> Director Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70 hagud@orex.es<mailto:hagud@orex.es> · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema. 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. _______________________________________________ Koha mailing list http://koha-community.org Koha@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.
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
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@lists.katipo.co.nz] On Behalf Of Robin Sheat Sent: April-07-15 9:46 PM To: koha@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@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.
Hi Craig and Robin, I'm very new to Koha and I'm implementing a library on Ubuntu 14.04 and I faced the same problem as you did. Would you be able to help me - how did you actually get them to work please? I can't telnet to the port I've set. I tried changing the iptables, and I have also tried different ports on the koha-conf.xml, but with no success. Does it make a difference if I set it on the UDP or TCP port? As I couldn't add it using iptable rules, I've added it in apache2's port. Am I doing something wrong here? Cheers, Viv -- View this message in context: http://koha.1045719.n5.nabble.com/Creating-a-Z39-50-Target-No-connection-tp5... Sent from the Koha-general mailing list archive at Nabble.com.
Hi Viv, In my experience, whenever you cannot telnet to the port that you set in koha-conf.xml, it doesn't necessarily mean that the port is closed (say by a firewall or some such setting), but rather that no service is running on it yet. In other words, your system does not recognize the Z39.50 as "activated". On the two separate occasions where I activated the Z39.50 settings in /etc/koha/sites/<instance>/koha-conf.xml (not koha-conf.xml.in), I had to completely reboot my server. I know the instructions say to restart Zebra by running sudo koha-restart-zebra <instance>, but the reboot was what did it for me. Be sure to save your koha-conf settings as root though! <-- I didn’t do this the first time. So, what I did was this: 1. As root user, navigate to /etc/koha/sites/<instance>/koha-conf.xml [Open with nano (or some other editor)] 2. Uncomment the necessary sections of koha-conf.xml 3. Set the <listen id> tag content to the port of your choice (I chose 9999, thus " <listen id="publicserver">tcp:@:9999</listen>" 4. Save your file and exit (Ctrl+O, then Ctrl+X) 5. Restart Zebra: koha-restart-zebra <instance> 6. Check if you can telnet to the port you set: telnet localhost <port #> (without '<>' of course) 7. If it gives you a "connection refused" error, check koha-conf.xml again. 8. If all is well, then restart Zebra again. 9. If connection refused after telnetting to port for the second time, reboot server. 10. In my case, this is what did it. Everything was up and running. I tested the connection using MarcEdit's ILS integration module. It's also handy to take a look at your Zebra logs, which should be here: /var/log/koha/library ; it is here that you will find clues as to what might be preventing you from connecting. You know Z39.50 is working when you visit, <url:port/biblios> in my case, library.craigbutosi.ca:9999/biblios <--you should see an xml file. The above is what worked for me. I've learned everything on the advice of Robin and others on this list (thank you all by the way! Love this list!). I've also been told to steer clear of changing iptables. There shouldn't be (generally speaking) any reason to have to modify them for the task here. I hope this little bit helps! Thoughts anyone? Best to all, 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@lists.katipo.co.nz] On Behalf Of cartoonmagic Sent: May-01-15 6:30 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Creating a Z39.50 Target - No connection Hi Craig and Robin, I'm very new to Koha and I'm implementing a library on Ubuntu 14.04 and I faced the same problem as you did. Would you be able to help me - how did you actually get them to work please? I can't telnet to the port I've set. I tried changing the iptables, and I have also tried different ports on the koha-conf.xml, but with no success. Does it make a difference if I set it on the UDP or TCP port? As I couldn't add it using iptable rules, I've added it in apache2's port. Am I doing something wrong here? Cheers, Viv -- View this message in context: http://koha.1045719.n5.nabble.com/Creating-a-Z39-50-Target-No-connection-tp5... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://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.
Hi Craig, Thank you so much for your detailed instructions. When I do telnet, it doesn't give me a 'connection refused'. It simply doesn't respond after connecting. I have rebooted my server and restarted zebra as instructed. URL:port/biblios also doesn't give me anything even after I have rebuilt zebra. What do you think is wrong? I'm hoping to use MarcEdit's ILS integration module as I have lots of files to tweak later. On Fri, May 1, 2015 at 1:38 PM, Craig Butosi <craig.butosi@rcmusic.ca> wrote:
Hi Viv,
In my experience, whenever you cannot telnet to the port that you set in koha-conf.xml, it doesn't necessarily mean that the port is closed (say by a firewall or some such setting), but rather that no service is running on it yet. In other words, your system does not recognize the Z39.50 as "activated". On the two separate occasions where I activated the Z39.50 settings in /etc/koha/sites/<instance>/koha-conf.xml (not koha-conf.xml.in), I had to completely reboot my server. I know the instructions say to restart Zebra by running sudo koha-restart-zebra <instance>, but the reboot was what did it for me. Be sure to save your koha-conf settings as root though! <-- I didn’t do this the first time.
So, what I did was this:
1. As root user, navigate to /etc/koha/sites/<instance>/koha-conf.xml [Open with nano (or some other editor)] 2. Uncomment the necessary sections of koha-conf.xml 3. Set the <listen id> tag content to the port of your choice (I chose 9999, thus " <listen id="publicserver">tcp:@:9999</listen>" 4. Save your file and exit (Ctrl+O, then Ctrl+X) 5. Restart Zebra: koha-restart-zebra <instance> 6. Check if you can telnet to the port you set: telnet localhost <port #> (without '<>' of course) 7. If it gives you a "connection refused" error, check koha-conf.xml again. 8. If all is well, then restart Zebra again. 9. If connection refused after telnetting to port for the second time, reboot server. 10. In my case, this is what did it. Everything was up and running. I tested the connection using MarcEdit's ILS integration module.
It's also handy to take a look at your Zebra logs, which should be here: /var/log/koha/library ; it is here that you will find clues as to what might be preventing you from connecting.
You know Z39.50 is working when you visit, <url:port/biblios> in my case, library.craigbutosi.ca:9999/biblios <--you should see an xml file.
The above is what worked for me. I've learned everything on the advice of Robin and others on this list (thank you all by the way! Love this list!). I've also been told to steer clear of changing iptables. There shouldn't be (generally speaking) any reason to have to modify them for the task here.
I hope this little bit helps!
Thoughts anyone?
Best to all,
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@lists.katipo.co.nz] On Behalf Of cartoonmagic Sent: May-01-15 6:30 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Creating a Z39.50 Target - No connection
Hi Craig and Robin,
I'm very new to Koha and I'm implementing a library on Ubuntu 14.04 and I faced the same problem as you did. Would you be able to help me - how did you actually get them to work please?
I can't telnet to the port I've set. I tried changing the iptables, and I have also tried different ports on the koha-conf.xml, but with no success. Does it make a difference if I set it on the UDP or TCP port? As I couldn't add it using iptable rules, I've added it in apache2's port. Am I doing something wrong here?
Cheers, Viv
-- View this message in context: http://koha.1045719.n5.nabble.com/Creating-a-Z39-50-Target-No-connection-tp5... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://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.
Craig Butosi schreef op vr 01-05-2015 om 12:38 [+0000]:
I know the instructions say to restart Zebra by running sudo koha-restart-zebra <instance>, but the reboot was what did it for me.
If you notice this being an ongoing problem, can you please file a bug with steps to reproduce? koha-restart-zebra should work (but there was always the chance it somehow got into a bit of an incorrect state that fixed itself eventually.) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (5)
-
cartoonmagic -
Craig Butosi -
Hugo Agud -
Robin Sheat -
Vee San Cheong