- Koha - lists.katipo.co.nz

There was an error updating the user
by Victor Barroso Oliveira 23 Jun '21

23 Jun '21

In version 18 ubuntu and koha 21.5. When trying to save a user is showing the following error "There was an error updating the user. Check the logs." How can I solve this problem? Thanks, Victor

2 1

Error 500 when calling "import_borrowers.pl"
by Michael Kuhn 23 Jun '21

23 Jun '21

Hi Himanshu > image.png > This is the error i am getting when I click on import Patrons module. > Koha version is 21.05. this is the reason I asked. Error 500 is a very unspecific HTTP message that can have many different reasons. You will have to search for the reason in the log files. However, this error has nothing to do with the (meanwhile solved) problem described in my posting "[Koha] Reoccurring DBMS auto increment issue". Just for your information: I just checked in my own demo installation ( http://koha.adminkuhn.ch:8080 ) which uses Koha 21.05 - it also gives me Error 500 when clicking Koha menu "Tools > Import patrons". In my case log file "plack-error.log" shows the following: Could not compile /usr/share/koha/intranet/cgi-bin/tools/import_borrowers.pl: Can't locate Data/Printer.pm in @INC (you may need to install the Data::Printer module) (@INC contains: /usr/share/koha/lib /usr/share/koha/installer /usr/share/koha/lib/installer /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base /var/lib/koha/sandkasten/plugins) at /usr/share/koha/lib/Koha/Patrons/Import.pm line 352. BEGIN failed--compilation aborted at /usr/share/koha/lib/Koha/Patrons/Import.pm line 352. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/tools/import_borrowers.pl line 50. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/tools/import_borrowers.pl line 50. Maybe this is just a new bug you found. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch -------- Weitergeleitete Nachricht -------- Betreff: Re: [Koha] Reoccurring DBMS auto increment issue Datum: Tue, 22 Jun 2021 17:25:33 +0200 Von: Michael Kuhn <mik(a)adminkuhn.ch> Antwort an: Michael Kuhn <mik(a)adminkuhn.ch> Organisation: Admin Kuhn GmbH An: Himanshu Aggarwal <rtr.himanshu(a)gmail.com> Hi > image.png > This is what I see OK, but these are not error messages - this is just a directory listing with the names of some files on the right side. What are you asking exactly? To look into one of these log files you could use for example: # more intranet-error.log or # tail intranet-error.log or any other bash command that makes sense. But you should definitely have basic Linux knowledge if you are ranging the file system. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch -------- Weitergeleitete Nachricht -------- Betreff: Re: [Koha] Reoccurring DBMS auto increment issue Datum: Tue, 22 Jun 2021 17:02:29 +0200 Von: Michael Kuhn <mik(a)adminkuhn.ch> Antwort an: Michael Kuhn <mik(a)adminkuhn.ch> Organisation: Admin Kuhn GmbH An: Himanshu Aggarwal <rtr.himanshu(a)gmail.com> Hi Himanshu > Yes it helped me to understand the errors I am getting but how to > resolve it? I don't know of any errors that you are getting. Best wishes: Michael Kuhn -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

2 3

Error 500 in Koha OPAC but NOT Staff Catalog After Running Linux System Update
by Charles Kelley 22 Jun '21

22 Jun '21

Hello, all! Yesterday, I updated my library's entire catalog. What we did was to exchange the CCODE and LOC. It worked fine. It took all day and part of today, but it worked. Then I ran Linux system updates. It too worked fine -- in staff mode. In the patron mode, it's another story. It shows the search screen but instead of the bib. record with the holdings, we see this response for every record search: Sorry, the requested page is not available > Error 500 > This message can have the following reason(s): > > An error occurred while processing your request. > What's next? > You can use the menu and links at the top of the page > You can search our catalog using the search form at the top of this page. > Return to the catalog home page. > Report issues and broken links > To report this error, please contact the Koha Administrator. Send email. > First, what does this mean? Second, how do I fix this? If the staff can see the records, ought not the patrons, also? Since the patrons cannot see the results -- results that the staff can see, mind you -- why can't the patrons? Did something break in the last system update? If so, what so? Thanks for you help. Koha v. 20.05 Linux Debian v. 9.13 "Stretch" -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

3 2

Re: [Koha] Error 500 when calling "import_borrowers.pl"
by Michael Kuhn 22 Jun '21

22 Jun '21

Hi > I see so I guess the administrators need to look into this matter. > Should we report about this in the Bugzilla? I suggest first to find out yourself what's the problem, but if it persists - yes, I guess you should report this in Bugzilla. BTW please always answer to the list so other people can read the discussion too and maybe add more information. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch Am 22.06.21 um 18:23 schrieb Himanshu Aggarwal: > I see so I guess the administrators need to look into this matter. > Should we report about this in the Bugzilla? > > On Tue, Jun 22, 2021 at 9:44 PM Michael Kuhn <mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch>> wrote: > > Hi Himanshu > > > image.png > > This is the error i am getting when I click on import Patrons > module. > > Koha version is 21.05. this is the reason I asked. > > Error 500 is a very unspecific HTTP message that can have many > different > reasons. You will have to search for the reason in the log files. > > However, this error has nothing to do with the (meanwhile solved) > problem described in my posting "[Koha] Reoccurring DBMS auto increment > issue". > > Just for your information: I just checked in my own demo installation ( > http://koha.adminkuhn.ch:8080 <http://koha.adminkuhn.ch:8080> ) > which uses Koha 21.05 - it also gives me > Error 500 when clicking Koha menu "Tools > Import patrons". In my case > log file "plack-error.log" shows the following: > > Could not compile > /usr/share/koha/intranet/cgi-bin/tools/import_borrowers.pl > <http://import_borrowers.pl>: Can't locate > Data/Printer.pm in @INC (you may need to install the Data::Printer > module) (@INC contains: /usr/share/koha/lib /usr/share/koha/installer > /usr/share/koha/lib/installer /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 > /usr/local/share/perl/5.24.1 > /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 > /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base > /var/lib/koha/sandkasten/plugins) at > /usr/share/koha/lib/Koha/Patrons/Import.pm line 352. > BEGIN failed--compilation aborted at > /usr/share/koha/lib/Koha/Patrons/Import.pm line 352. > Compilation failed in require at > /usr/share/koha/intranet/cgi-bin/tools/import_borrowers.pl > <http://import_borrowers.pl> line 50. > BEGIN failed--compilation aborted at > /usr/share/koha/intranet/cgi-bin/tools/import_borrowers.pl > <http://import_borrowers.pl> line 50. > > Maybe this is just a new bug you found. > > Best wishes: Michael > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz > T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> > > > > -------- Weitergeleitete Nachricht -------- > Betreff: Re: [Koha] Reoccurring DBMS auto increment issue > Datum: Tue, 22 Jun 2021 17:25:33 +0200 > Von: Michael Kuhn <mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch>> > Antwort an: Michael Kuhn <mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch>> > Organisation: Admin Kuhn GmbH > An: Himanshu Aggarwal <rtr.himanshu(a)gmail.com > <mailto:rtr.himanshu@gmail.com>> > > Hi > > > image.png > > This is what I see > > OK, but these are not error messages - this is just a directory listing > with the names of some files on the right side. > > What are you asking exactly? > > To look into one of these log files you could use for example: > > # more intranet-error.log > > or > > # tail intranet-error.log > > or any other bash command that makes sense. But you should definitely > have basic Linux knowledge if you are ranging the file system. > > Best wishes: Michael > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz > T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> > > > > -------- Weitergeleitete Nachricht -------- > Betreff: Re: [Koha] Reoccurring DBMS auto increment issue > Datum: Tue, 22 Jun 2021 17:02:29 +0200 > Von: Michael Kuhn <mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch>> > Antwort an: Michael Kuhn <mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch>> > Organisation: Admin Kuhn GmbH > An: Himanshu Aggarwal <rtr.himanshu(a)gmail.com > <mailto:rtr.himanshu@gmail.com>> > > Hi Himanshu > > > Yes it helped me to understand the errors I am getting but how to > > resolve it? > > I don't know of any errors that you are getting. > > Best wishes: Michael Kuhn > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz > T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch > <mailto:mik@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> > > > > > > -- > Assistant Librarian, > Confucius Institute Scholar 13-14, > R.D. National College, > Bandra (W.)

1 0

Title search works, but Library catalog search fails in OPAC
by Bales (US), Tasha R 22 Jun '21

22 Jun '21

Good afternoon, I’m having trouble with Title vs. Library catalog keyword searching with several example titles. Searching the same phrase with either method yields different results. This problem occurs only in the OPAC. I hope to confirm whether the behavior I’m seeing is intended (i.e., the problem is me) or not. Thanks in advance. For example, given the ebook title, Electroactive polymer (EAP) actuators as artificial muscles, a Title keyword search in the OPAC is successful, but a plain, Library catalog (i.e., no index specified), keyword search fails. For reference, the title is recorded in the MARC record as: 245 00 - TITLE STATEMENT a Title Electroactive polymer (EAP) actuators as artificial muscles : Below I’ve copied in my search history as well as the tail of the search URL that shows the search parameters. · Library catalog keyword search with 0 results o 2021-06-21 02:34 PM  Electroactive polymer (EAP) actuators, suppress:false 0 o …opac-search.pl?idx=&q=Electroactive%20polymer%20%28EAP%29%20actuators&weight_search=1 · Title keyword search with 2 results o 2021-06-21 02:34 PM  Electroactive polymer (EAP) actuators, suppress:false 2 o …opac-search.pl?idx=ti&q=Electroactive+polymer+%28EAP%29+actuators&weight_search=1 As a test, I decided to enclose my Library catalog search terms in quotes, which yielded the desired results. However, I did not at all anticipate that quotes would be required to get hits: · Library catalog quoted keyword search with 2 results o 2021-06-21 02:46 PM  "Electroactive polymer (EAP) actuators", suppress:false 2 o … opac-search.pl?idx=&q=%22Electroactive+polymer+%28EAP%29+actuators%22&weight_search=1 On comparing the above URL query strings, it appears that the unquoted terms in the Library catalog keyword search aren’t “anded” together with a “+” the way other searches are, but I’m not sure what the implications are, if any. Also, the Koha manual indicates the following, which suggests to me that I ought to get hits on the unquoted string: When you have more than one word in the search box, Koha will still do a keyword search, but a bit differently. Each word will be searched on its own, then the Boolean connector ‘and’ will narrow your search to those items with all words contained in matching records. I understand and can predict pretty well the way our old ILS (Millennium, if context helps) will perform a keyword search, but I’m a little confused here. My expectation for this particular case is that all of the above methods would yield results. If there are any pointers to be had, I thank you if might point me to them so that I may be better poised to help users. I’m using Elasticsearch with Koha 20.11.06. I reindexed both authorities and biblios today, but that didn’t impact my experience. The records are not newly added. Thanks! Tasha Bales Business Support Team | Information Services Enterprise Services | Enterprise Operations, Finance and Sustainability

2 2

Need help with Koha instance that refuses to do checkouts
by Chris Brown 22 Jun '21

22 Jun '21

Dear Koha Community Following up my post on 12 June I am repeating my call for help as Koha is effectively unusable right now at one of our libraries. We are running Koha 19.11 on Debian 9.11 (stretch). This supports 5 Koha instances for some of the volunteer-run libraries in Sheffield. It has been stable and working fine for many months. Currently we have a serious problem with one of these instances. Any attempt to check out a book hangs (never completes) and we see /usr/share/koha/intranet/cgi-bin/circ/circulation.pl consuming most of the CPU cycles (stuck in a loop perhaps?). On one occasion I noticed it was renew.pl consuming all the CPU. I have tried disabling plack for this instance, and have rebuilt the zebra index, but the problem persists. There is nothing obvious reported in the log files, though I may not be looking in the right places. I cannot see any obvious problems with the configuration, though again I might be looking at the wrong things. The other 4 instances are working OK. *Any advice on how to debug or fix this would be greatly appreciated.* Does anyone know how to turn on tracing of MySQL transactions? I was wondering if looking at the activity at the database end might help. Thanks and Best Regards, Chris Brown (Voluntary Libraries in Sheffield)

6 7

Collection code
by Carlo Dumontet 22 Jun '21

22 Jun '21

Could anyone please tell me how to create a new Collection Code? Many thanks Carlo

2 1

re-arrange facet order in Koha 20.11
by Thomas Vealehse 21 Jun '21

21 Jun '21

Hi I'd like to re-arrange the facet order on the results page in the left hand side bar. For example 'Author' would be pushed down the list, and 'item type' moved up. Also is it possible to rename the facets? Thanks Thomas

3 3

many cig:error on opac-error.log and intranet-error.log
by C P Hong 21 Jun '21

21 Jun '21

Hello, I am seeing many error entries on opac-error.log. Sat Jun 19 18:15:47.054074 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in hash element at /usr/share/koha/lib/C4/XSLT.pm line 359.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl [Sat Jun 19 18:15:47.054370 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in scalar assignment at /usr/share/koha/lib/C4/Koha.pm line 550.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl [Sat Jun 19 18:15:47.076539 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in hash element at /usr/share/koha/lib/C4/XSLT.pm line 359.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl [Sat Jun 19 18:15:47.076831 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in scalar assignment at /usr/share/koha/lib/C4/Koha.pm line 550.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl [Sat Jun 19 18:15:47.099125 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in hash element at /usr/share/koha/lib/C4/XSLT.pm line 359.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl [Sat Jun 19 18:15:47.099419 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in scalar assignment at /usr/share/koha/lib/C4/Koha.pm line 550.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl [Sat Jun 19 18:15:47.121645 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in hash element at /usr/share/koha/lib/C4/XSLT.pm line 359.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl [Sat Jun 19 18:15:47.121938 2021] [cgi:error] [pid 14502] [client 185.191.171.33:63720] AH01215: [Sat Jun 19 18:15:47 2021] opac-search.pl: Use of uninitialized value in scalar assignment at /usr/share/koha/lib/C4/Koha.pm line 550.: /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl I checked client ip address. Non-authoritative answer: 33.171.191.185.in-addr.arpa name = crawl27.bl.semrush.com. Any ideas what the errors mean. Do you know what this client is trying to do with my koha system? How do I fix the errors? On another log - intranet-error.log. I saw the error entry below. What does that mean? How do I fix the issue? FYI. I am running Koha version 20.11.03 and Elasticsearch version 6.8.9. Sat Jun 19 18:14:39.867657 2021] [cgi:error] [pid 14436] [client xxx.xxx.xxx.xxx:59533] AH01215: [Sat Jun 19 18:14:39 2021] addbiblio.pl: [Request] ** [http://localhost:9200]-[400] [illegal_argument_exception] Fielddata is disabled on text fields by default. Set fielddata=true on [local-number__sort] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead., called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 96. With vars: {'body' => {'status' => 400,'error' => {'grouped' => bless( do{\\(my $o = 1)}, 'JSON::PP::Boolean' ),'caused_by' => {'reason' => 'Fielddata is disabled on text fields by default. Set fielddata=true on [local-number__sort] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.','caused_by' => {'type' => 'illegal_argument_exception','reason' => 'Fielddata is disabled on text fields by default. Set fielddata=true on [local-number__sort] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.'},'type' => 'illegal_argument_exception'},'reason' => 'all shards failed','root_cause' => [{'reason' => 'Fielddata is disabled on text fields by default. Set fielddata=true on [local-number__sort] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.','type' => 'illegal_argument_exception'}],'phase' => 'query','failed_shards' => [{'node' => 'XixKhqGwRtinFdkt7uwTWw','index' => 'koha_lib_authorities','shard' => 0,'reason' => {'type' => 'illegal_argument_exception','reason' => 'Fielddata is disabled on text fields by default. Set fielddata=true on [local-number__sort] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.'}}],'type' => 'search_phase_execution_exception'}},'request' => {'ignore' => [],'body' => {'size' => 20,'sort' => [{'local-number__sort' => 'asc'}],'query' => {'bool' => {'filter' => {'term' => {'authtype.raw' => 'PERSO_NAME'}},'must' => [{'term' => {'match-heading.ci_raw' => 'Schmidt Thomas E'}}]}},'from' => 0},'path' => '/koha_lib_authorities/_search','mime_type' => 'application/json','qs' => {},'serialize' => 'std','method' => 'GET'},'status_code' => 400}: /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl, referer: http://xxx.xxx.org:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=… Best Regards, Chee

2 1

renewal period setting
by Nalisha Tamang 21 Jun '21

21 Jun '21

Dear all, please help me to set the renewal period in circulation and fine setting . as our library users can renew the book 3 times and the renewal period is 10 days. But when I try to renew a book it only renews 1 day at a time. If the due date is 22June 2021 then if i renew it gives 23 June 2021. According to our rule it should be 01 July 2021. Please help me out Thank you in advance Nalisha Tamang Rai

2 2