- Koha - lists.katipo.co.nz

Koha Community Newsletter: February 2021
by Koha Newsletter 28 Feb '21

28 Feb '21

The Koha Community Newsletter for February 2021 is here: https://koha-community.org/koha-community-newsletter-february-2021/ Many thanks to everyone who submitted articles and news to last month's newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

2 1

Re: [Koha] HELP - 502 Proxy error on version 19.11.14
by gveranis＠dataly.gr 26 Feb '21

26 Feb '21

Hi Jose, Do you check the logs from your koha ? under the following path ? /var/log/koha/ Best Regards, George Παραθέτοντας από Jose Ricardo Quaglio <jose.quaglio(a)saobernardo.sp.gov.br>: > Hi, > > > > We used koha in version 19.11.09.000, when upgrading to version 19.11.14.000 > we see a performance difference when running resources. > > > > The screen with the message often appears: Proxy Error. The proxy server > received an invalid response from an upstream server. The proxy server could > not handle the request. Reason: Error reading from remote server. > > > > Has anyone been through this situation? Do you know how to guide me? > > > > Server information: > > > > OS version ('uname -a'): Linux koha 3.16.0-9-amd64 #1 SMP Debian 3.16.68-2 > (2019-06-17) x86_64 > > Perl version: 5.020002 > > Versão do MYSQL: mysql Ver 15.1 Distrib 10.1.32-MariaDB, for > debian-linux-gnu (x86_64) using readline 5.2 > > Versão do apache: Server version: Apache/2.4.10 (Debian) > > PSGI: Plack (deployment) > > Memcached Servidores: 127.0.0.1:11211 | Namespace: koha_biblio | Situação: > em execução. | Configuração lida de: koha-conf.xml > > Versão do Zebra: Zebra 2.0.59 (C) 1994-2014 > > > > Tks, > > > > José Ricardo Quaglio > > > > Informatização de Bibliotecas - SC.211.3 > > Secretaria de Cultura / Município de São Bernardo do Campo > > Tel.: (11) 2630-9394 > > > > > > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Request to add Dataly Tech on Paid support in Greece and Cyprus
by gveranis＠dataly.gr 26 Feb '21

26 Feb '21

Hi All / Koha Community I would like to ask to add company 'Dataly Tech' to Koha directory for paid support in Greece and Cyprus. We have already submit some patches, sign-off , testing and we prepare to add more as we develop more and more.. Also as company we support Koha for National Library of Greece and National Library of Cyprus, among other 80 Libraries on both countries. Company Name: Dataly Tech Contact Person: George Veranis Contact email: info(a)dataly.gr Website: https://dataly.gr Telephone: +30 231231 4264 Best Regards, George Veranis CTO Dataly Tech

2 2

HELP - 502 Proxy error on version 19.11.14
by Jose Ricardo Quaglio 26 Feb '21

26 Feb '21

Hi, We used koha in version 19.11.09.000, when upgrading to version 19.11.14.000 we see a performance difference when running resources. The screen with the message often appears: Proxy Error. The proxy server received an invalid response from an upstream server. The proxy server could not handle the request. Reason: Error reading from remote server. Has anyone been through this situation? Do you know how to guide me? Server information: OS version ('uname -a'): Linux koha 3.16.0-9-amd64 #1 SMP Debian 3.16.68-2 (2019-06-17) x86_64 Perl version: 5.020002 Versão do MYSQL: mysql Ver 15.1 Distrib 10.1.32-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 Versão do apache: Server version: Apache/2.4.10 (Debian) PSGI: Plack (deployment) Memcached Servidores: 127.0.0.1:11211 | Namespace: koha_biblio | Situação: em execução. | Configuração lida de: koha-conf.xml Versão do Zebra: Zebra 2.0.59 (C) 1994-2014 Tks, José Ricardo Quaglio Informatização de Bibliotecas - SC.211.3 Secretaria de Cultura / Município de São Bernardo do Campo Tel.: (11) 2630-9394

1 0

Search Produces No Results
by Gopalakrishna-BMSIT 26 Feb '21

26 Feb '21

Installation type: Package OS: Ubuntu Server 18.04.5 Koha: Upgraded from 19.11 to 20.11 Problem: Search produces no result Action Taken: Rebuilt full zebra index several times System Information: XML configuration file WarningYou are missing the <lockdir> entry in your koha-conf.xml file. Please add it, pointing to your Koha instance's lock dir. How to fix this? *With Regards,* *Gopalakrishna* *Librarian, B.M.S Institute of Technology,Avalahalli, Doddaballapur Main Road,Yelahanka, Bangalore-64Mob.: 861 853 1385* * 974 189 8674*

2 1

Need help with a couple of errors
by Doug Dearden 25 Feb '21

25 Feb '21

Hey Everyone, I posted earlier about trying to upgrade from 19.05 to 20.11 but was unable to solve all the issues after making the move. I decided to just go back to 19.05. I had updated to Debian Buster from Stretch. I installed 19.05 on Buster but ran into a problem with mojolicious not being the right version. A little investigation made me conclude that Buster/19.05 and the version of mojolicious weren't going to work together, but Buster/19.11 might. I installed 19.11 and passed the required prerequisites to do the upgrade. There was one error listed at the bottom of the install info when I hit the staff client during the upgrade: "Update errors : [Tue Feb 23 11:43:34 2021] updatedatabase.pl: Use of uninitialized value $INC[-1] in string eq at /usr/share/koha/lib/Koha/Plugins.pm line 37." I am also getting this error when I rebuild zebra on two of the three instances I am running: "Use of uninitialized value in subroutine entry at /usr/share/perl5/Module/Find.pm line 190." Find.pm line 190 includes the value @INC which makes me wonder if these are related, and perhaps I am missing something in a config file. I had some other strange things with Plack but was able to track them down, all instances do seem to be working. Any insights to the above error messages are appreciated. Thanks, Doug Dearden Director / Information Technology School for Advanced Research (SAR) PO Box 2188 / Santa Fe / NM / 87504-2188 505-954-7220 (work) / 505-690-1535 (cell) www.sarweb.org<http://www.sarweb.org/> EXPLORING HUMANITY. UNDERSTANDING OUR WORLD. Receive the SAR monthly E-News: SIGN UP HERE <https://sarweb.org/about/e-news-signup/>

3 3

Release of Koha 20.11.03
by Fridolin SOMERS 24 Feb '21

24 Feb '21

Hello everyone 🤗 The Koha community is proud to announce the release of Koha 20.11.03. It is a maintenance release including 2 new features, 22 enhancements, 74 bugfixes, 1 security fix. So consider upgrading quickly 🤖 The full release notes are available here: https://koha-community.org/koha-20-11-03-released/ Debian packages should be available in a few days. Best regards 🤓 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

2 2

Koha 19.11.15 released, security release ⚠
by Victor Grousset/tuxayo 24 Feb '21

24 Feb '21

Hello! The Koha Community is happy to announce the release of Koha 19.11.15 The full release notes can be found at: https://koha-community.org/koha-19-11-15-released/ Debian packages will be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo

1 0

Re: [Koha] Status of ElasticSearch - 2021 version
by dcook＠prosentient.com.au 23 Feb '21

23 Feb '21

Hi Tom, I can't really speak to Elasticsearch with Koha, as I still just use Zebra. I imagine Ere in Finland or someone from Bywater in the USA might be the best to comment on Elasticsearch. However, I'm curious what OS you are using. Debian/Ubuntu is typically the best option in terms of community support, but I also run Koha on OpenSUSE, and have run it on all kinds of other Linux-based OSes. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- Date: Mon, 22 Feb 2021 14:47:38 -0500 From: Tom Hanstra <hanstra(a)nd.edu> To: Koha Community <koha(a)lists.katipo.co.nz> Subject: [Koha] Status of ElasticSearch - 2021 version Message-ID: <CAA60kZMf7=KkeojMVDA8M-DWBN8VG3OJpa9b6U3u+c74C7qVBA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Last year I checked in on the status of ElasticSearch with Koha and got the distinct impression that it was still quite a work in progress. Almost a year has passed and I'm not sure if much has changed. As late as October, 2020, I see messages suggesting "Stay with Zebra for now". But I also see some messages about sites who claim to have successfully moved to ElasticSearch. It is just unclear if they are using it for everything or if there is some hybrid of using both in place. The Wiki is of little help. Along with being completely Debian-centric (I'm not using Debian), it is a couple of versions behind. So, again, signs that ElasticSearch is still not mainstream. So, who actually uses ElasticSearch in production at this point? I'm interested in doing so if it can speed things up as well as work fully with both Authorities and Bibs. But if it is still not there, I can continue with Zebra. Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra(a)nd.edu

2 1

Re: [Koha] Help debugging Internal Server Error
by Doug Dearden 22 Feb '21

22 Feb '21

Hey Everyone, Thank you Alvaro and Jonathan for your help, I wanted to report back that I got this fixed and what the problem was in case someone else runs into this. An error in the plack-opac-error.log appears, and the same warning appears when I did koha-rebuild-zebra with the –v option: DBD::mysql::st execute failed: Unknown column 'me.exclude_from_local_holds_priority' I created a new instance, and found that column in the items table on the new instance but not on the old instance. I added the column with the SQL command: ALTER TABLE items ADD exclude_from_local_holds_priority tinyint(1) and that fixed it. I’m not sure why koha-upgrade-schema didn’t fix this. I have another instance that we stopped using and combined with an existing one. I tried doing koha-remove, then koha-restore, the koha-upgrade-schema on that instance and it didn’t work. I am concerned that there may be other database alterations between version 19.05 and 20.11.02.000 that also didn’t make it into the database. I found a reference to database changes on the wiki but it ends in the 3.x series. How do I find out what other database schema changes have been implemented between 19.05 and 20.11.02.000? Thanks, Doug Dearden Director / Information Technology School for Advanced Research (SAR) PO Box 2188 / Santa Fe / NM / 87504-2188 505.954.7220 / www.sarweb.org<http://www.sarweb.org/> EXPLORING HUMANITY. UNDERSTANDING OUR WORLD. Receive the SAR monthly E-News: SIGN UP HERE <https://sarweb.org/about/e-news-signup/>

2 4