<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 17274 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 187, Issue 23<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. pull latest koha-testing-docker-images (Add new lib<br> directory) (Jonathan Druart)<br> 2. Release of Koha 21.05.01 (Nick Clemens)<br> 3. Re: Z39.50 daemon with ElasticSearch (Jason Boyer)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 24 Jun 2021 15:57:17 +0200<br>From: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] pull latest koha-testing-docker-images (Add new<br> lib directory)<br>Message-ID:<br> <CAJzKNY5yA5V=FUpcvgEqhz0=JwHOFbF9gVxJjQH6tPnOHRY_Sw@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>(This is a message from last week that didn't reach the list)<br><br>Hi,<br><br>I've just pushed bug 28489 that is adding a new "lib" directory. It<br>needs to be added to the apache config, and new koha-testing-docker<br>images have been published.<br><br>The error:<br>couldn't load CGI::Session::Serialize::yamlxs: Can't locate<br>CGI/Session/Serialize/yamlxs.pm in @INC (you may need to install the<br>CGI::Session::Serialize::yamlxs module)<br><br>The KTD solution: `docker-compose pull`<br><br>A workaround (if you are not using ktd):<br>In your apache config, add the lib directory:<br>SetEnv PERL5LIB "/kohadevbox/koha:/kohadevbox/koha/lib"<br><br>That's not enough, for the CLI scripts (and tests), you will need to<br>adjust PERL5LIB as well<br>In koha-testing-docker, edit .env and replace the PERL5LIB line with:<br> PERL5LIB=/kohadevbox/koha:/kohadevbox/koha/lib:/kohadevbox/qa-test-tools<br><br>Cheers,<br>Jonathan<br><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 24 Jun 2021 13:27:40 -0400<br>From: Nick Clemens <nick@bywatersolutions.com><br>To: Koha <koha@lists.katipo.co.nz>, Koha Devel<br> <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Release of Koha 21.05.01<br>Message-ID:<br> <CAA_eX3PFb5U1RoQAb1O3MuUKX4XTBzCFXF3unGrGwpov80CENw@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all!<br><br>The Koha community is pleased to announce the release of Koha 21.05.01!<br>The full release notes can be found here:<br>https://koha-community.org/koha-21-05-01-released/<br><br>Thanks!<br>Kyle + Nick<br><br><br>-- <br>Nick Clemens<br>ByWater Solutions<br>bywatersolutions.com<br>Phone: (888) 900-8944<br>Pronouns: (he/him/his)<br>Timezone: Eastern<br>Follow us:<br><https://www.facebook.com/ByWaterSolutions/><br><https://www.instagram.com/bywatersolutions/><br><https://www.youtube.com/user/bywatersolutions><br><https://twitter.com/ByWaterSolution><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210624/d63db876/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Thu, 24 Jun 2021 14:30:48 -0400<br>From: Jason Boyer <JBoyer@equinoxOLI.org><br>To: Zeno Tajoli <ztajoli@gmail.com><br>Cc: Fridolin SOMERS <fridolin.somers@biblibre.com>,<br> koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Z39.50 daemon with ElasticSearch<br>Message-ID: <35868655-B963-4CCB-8967-BC29642D7B82@equinoxOLI.org><br>Content-Type: text/plain; charset="utf-8"<br><br>I was glad that I remembered this exchange, I was setting up ES and the z3950 responder today and having some trouble. I poked at the script a bit to see what might be the problem but didn’t have time to figure out the issue. I am fairly comfortable with systemd units though, so I put together the attached instanced service so you can create as many z3950 instances as needed on a Debian-packages based system like so:<br><br>systmectl start koha-z3950-responder@instance-name.service<br>systmectl enable koha-z3950-responder@instance-name.service<br><br>And it should work as intended with koha-z3950-responder --start ...<br><br>Since systemd keeps track of things there’s no need to worry about the -u or -p options<br><br>Jason<br><br>-- <br>Jason Boyer<br>Senior System Administrator<br>Equinox Open Library Initiative<br>JBoyer@equinoxOLI.org<br>+1 (877) Open-ILS (673-6457)<br>https://equinoxOLI.org/<br><br>> On Dec 15, 2020, at 6:02 PM, Zeno Tajoli <ztajoli@gmail.com> wrote:<br>> <br>> Hi,<br>> <br>> I use the suggestion of Fridolin and now I'm a working z39.50 with ElasticSearch on Koha 20.11<br>> <br>> My SystemD unit (etc/systemd/system/koha-z39-el.service):<br>> [Unit]<br>> Description=Koha Z39.50 Service<br>> <br>> [Service]<br>> Type=simple<br>> User=lib-koha<br>> Environment="KOHA_CONF=/etc/koha/sites/lib/koha-conf.xml" "PERL5LIB=/usr/share/koha/lib"<br>> ExecStart=/usr/share/koha/bin/z3950_responder.pl --config-dir=/etc/koha/sites/lib/z3950-ES -l /var/log/koha/lib/z3950.log -u lib-koha -p /var/run/koha/lib/z3950-responder.pid --debug<br>> <br>> [Install]<br>> WantedBy=multi-user.target<br>> <br>> I add/change those values:<br>> User=<the Unix user related with instance><br>> <br>> ExecStart=/usr/share/koha/bin/z3950_responder.pl<br>> <br>> --config-dir=/etc/koha/sites/lib/z3950-ES<br>> #It can't use '-c'; I create a new specific dir for configurations<br>> <br>> -l /var/log/koha/lib/z3950.log<br>> #The log file<br>> <br>> -u lib-koha<br>> #The user to use<br>> <br>> -p /var/run/koha/lib/z3950-responder.pid<br>> #File for save pid<br>> <br>> --debug<br>> <br>> What do you think of the changes and adds ?<br>> <br>> Cheers<br>> Zeno Tajoli<br>> <br>> <br>> <br>> <br>> Il 15/12/2020 08:51, Fridolin SOMERS ha scritto:<br>>> Hi,<br>>> We at Biblibre use one Koha per machine so whe created a SystemD unit :<br>>> [Unit]<br>>> Description=Koha Z39.50 Service<br>>> [Service]<br>>> Type=simple<br>>> User=koha<br>>> Environment="KOHA_CONF=/home/koha/etc/koha-conf.xml" "PERL5LIB=/home/koha/src"<br>>> ExecStart=/home/koha/src/misc/z3950_responder.pl --debug<br>>> [Install]<br>>> WantedBy=multi-user.target<br>>> Easy peazy<br>>> Le 15/12/2020 à 00:57, Zeno Tajoli a écrit :<br>>>> Hi to,<br>>>> I'm trying to use ElasticSearch everywhere with Koha 20.11<br>>>> I'm working on Debian 10, EleasticSearch 6.8.13, Java openjdk 11 (Debian package)<br>>>> <br>>>> The search on Opac and Intranet is OK.<br>>>> <br>>>> Problems are on z39.50 server.<br>>>> With bug 13937 a z39.50/SRU server is ready also with ES as search back-end.<br>>>> <br>>>> But now the demonization of the script doesn't work.<br>>>> If i do:<br>>>> sudo koha-z3950-responder --start lib<br>>>> and I do a check with:<br>>>> yaz-client<br>>>> Z> open 127.0.0.1:2100/biblios<br>>>> Connecting...OK.<br>>>> Sent initrequest.<br>>>> Target closed connection<br>>>> Z><br>>>> <br>>>> The result is 'closed connection', ZOOM error: 1004<br>>>> <br>>>> But if do:<br>>>> sudo koha-z3950-responder --stop lib<br>>>> sudo koha-shell lib<br>>>> /usr/bin/perl /usr/share/koha/bin/z3950_responder.pl -c /etc/koha/sites/lib/z3950 -l /var/log/koha/lib/z3950.log<br>>>> koha@deb:~$ yaz-client<br>>>> Z> open 127.0.0.1:2100/biblios<br>>>> Connecting...OK.<br>>>> Sent initrequest.<br>>>> Connection accepted by v3 target.<br>>>> ID : 81<br>>>> Name : Koha/GFS/YAZ<br>>>> Version: 20.11.00.000/5.30.3 2af59bc45cf4508d5c84f350ee99804c4354b3b3<br>>>> Options: search present triggerResourceCtrl namedResultSets<br>>>> Elapsed: 0.012131<br>>>> Z> f css3<br>>>> Sent searchRequest.<br>>>> Received SearchResponse.<br>>>> Search was a success.<br>>>> Number of hits: 1, setno 1<br>>>> records returned: 0<br>>>> Elapsed: 0.915224<br>>>> Z> show 1<br>>>> Sent presentRequest (1+1).<br>>>> Records: 1<br>>>> []Record type: USmarc<br>>>> 00357nam a22001217a 4500<br>>>> 005 20201208204443.0<br>>>> 008 201208b ||||| |||| 00| 0 eng d<br>>>> 040 $c IFLA<br>>>> 100 $a Tajoli, Zeno<br>>>> 245 $a Node.js e CSS3<br>>>> ...<br>>>> <br>>>> So the script 'z3950_responder.pl' is working, the transformation into daemon not.<br>>>> Do you have any suggestion/check to fix this situation ?<br>>>> <br>>>> Cheers<br>>>> Zeno Tajoli<br>>>> <br>>>> <br>> <br>> -- <br>> Zeno Tajoli<br>> System Librarian<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org><br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel><br>> website : http://www.koha-community.org/ <http://www.koha-community.org/><br>> git : http://git.koha-community.org/ <http://git.koha-community.org/><br>> bugs : http://bugs.koha-community.org/ <http://bugs.koha-community.org/><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210624/379863ca/attachment.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 187, Issue 23<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>