- Koha - lists.katipo.co.nz

Call for News: October 2017 Newsletter
by kohanews 14 Oct '17

14 Oct '17

I'm collecting news for the October newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Re: [Koha] Major, multiple problems with our Koha 17.05 system.
by Benjamin Rokseth 13 Oct '17

13 Oct '17

Hi, just want to share our experience with 17.05 to give you some hints where to go. We have been using it in production since it was released and for us it has been stable enough. We are a large public library, 400k users, 19branches, some 70+ self checkout machines using SIP, and a quite high item turnover. For sure, mysql _needs_ quite a lot of ram, we specifically allocated 16G to the innondb buffer pool (innodb-buffer-pool-size=16G). This is needed since Koha rarely has been optimized for DB queries. Second, plack, apache and sip should have a fair amount of workers. In our example: SIP_WORKERS: 125 APACHE_MINSERVERS: 20 APACHE_TIMEOUT: 1000 PLACK_WORKERS: "30" PLACK_MAX_REQUESTS: "200" Now, on the few troubles we had so far: - when employees ran some troublesome SQL reports which consumed high amounts of memory it could overload, by starting to swap memory to disk and stall the system since there is no limits on what to run from the Reports. We resolved this by limiting the swap space (tmp) on the mysql server (tmpfs: /tmp:rw,size=655360k) Troublesome queries that exceed swap size would now die. Not the perfect solution, but a simple hack. - patron lookups in intra was sometimes overloading system if using mysql specific identifiers, e.g. percentage, '%a'. We resolved this by filtering with javascript. Again not perfect, but a simple hack. We also, even prior to 17.05, had complaints on slow performance and started investigating. The amount of unneccessary DB calls turned out to be absurd, so a perl expert helped us in resolving this my a memoized cached we named purefunctions. It's been discussed in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17941 which is a bug fixing some performance issues in CanbookBeRenewed. In short PureFunctions is a cache map to be used on the "immutable" functions called often, usually Getting info on items, patrons, etc. It is a short-lived cache, that is, it is function scope, so it will not live after function is returned. As an example, we ran a call on /svc/checkouts on a patron with 5 checkouts with some items that had many reserves and saw that about 15k db calls were saved and about 20sec. We have been running this stable for more than 6 months in production, so we are sure it is stable. Perhaps this should be added to the community? Our patch is here: https://gitlab.deichman.no/digibib/Koha/commit/919c65f1b521d051bc0dc137efae… As you can se, we have added it to any Get function that can be deemed safe, and it has improved our Koha performance immensely. To be sure, this is not fixing poorly optimized code, only bypassing it. Regards Benjamin Rokseth Oslo Public Library ________________________________________ Fra: Koha <koha-bounces(a)lists.katipo.co.nz> på vegne av koha-request(a)lists.katipo.co.nz <koha-request(a)lists.katipo.co.nz> Sendt: 12. oktober 2017 16:34 Til: koha(a)lists.katipo.co.nz Emne: Koha Digest, Vol 144, Issue 18 Send Koha mailing list submissions to koha(a)lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit https://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Re: Major, multiple problems with our Koha 17.05 system. (Tajoli Zeno) 2. Elasticsearch on BWS Sandboxes (BOUIS Sonia) 3. Re: Major, multiple problems with our Koha 17.05 system. (Tomas Cohen Arazi) 4. Re: Major, multiple problems with our Koha 17.05 system. (Jonathan Druart) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Oct 2017 14:29:53 +0200 From: Tajoli Zeno <z.tajoli(a)cineca.it> To: Raymund Delahunty <r.delahunty(a)arts.ac.uk>, "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Major, multiple problems with our Koha 17.05 system. Message-ID: <4498a2a9-1f3d-4899-caa0-daf803c2490d(a)cineca.it> Content-Type: text/plain; charset=utf-8; format=flowed Hi Raymund, Il 12/10/2017 13:29, Raymund Delahunty ha scritto: > VERY long sorry, but our Koha system is virtually unusable and we need help! generaly speaking, you can try to tune your MySQL setup, I find useful this tool: https://github.com/major/MySQLTuner-perl Attention that could you need more RAM on your server !! About SIP, do a search on bugzilla: https://bugs.koha-community.org/bugzilla3/ and see the open problems Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ------------------------------ Message: 2 Date: Thu, 12 Oct 2017 12:29:56 +0000 From: BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Elasticsearch on BWS Sandboxes Message-ID: <7dcf9a8b89154929861031405cc8dba7(a)exch2013-mb1.ad.univ-lyon3.fr> Content-Type: text/plain; charset="utf-8" What a good news ! Thank you Nick ! Sonia ------------------------------ Message: 6 Date: Thu, 12 Oct 2017 11:26:29 +0000 From: Nick Clemens <nick(a)bywatersolutions.com> To: Koha Devel <koha-devel(a)lists.koha-community.org>, Koha <koha(a)lists.katipo.co.nz>, ByWater Partners <partners(a)bywatersolutions.com> Subject: [Koha] Elasticsearch on BWS Sandboxes Message-ID: <CAA_eX3NAO1ktbRn4w00nxKausLBgn4sEGQVAywPuq75NarRhLA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi All, Just an update to ES testing, we have now made Elasticsearch available on the BWS sandboxes: http://sandbox.bywatersolutions.com/cgi-bin/sandbox-dashboard.pl You will need to set the 'SearchEngine' system preference once the sandbox is setup, but records should be indexed and ready to go. If you have any questions or problems please let me know via email or in IRC. -Nick (kidclamp) ------------------------------ Message: 7 Date: Thu, 12 Oct 2017 11:29:17 +0000 From: Raymund Delahunty <r.delahunty(a)arts.ac.uk> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Major, multiple problems with our Koha 17.05 system. Message-ID: <HE1PR0601MB2156A4DCC397D0A6FEB95796DC4B0(a)HE1PR0601MB2156.eurprd06.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" VERY long sorry, but our Koha system is virtually unusable and we need help! We are experiencing dozens of outages daily (both OPAC and intranet, more often only OPAC) with our Koha 17.05.01.000 (Debian 3.2.89-2, perl 5.020002, mysql 14.14, apache 2.4.10). Searches can take 15+ seconds. While university staff provide first tier support, we don't have server access, and the second tier and hosting is via an external company. Of course we are working with that company to have them identify the cause, but I have decided to ask the community of any user on 17.05 has the problems we have. Our system is quite extensively customised, with major work done to the OPAC at https://libsearch.arts.ac.uk<https://libsearch.arts.ac.uk/>. We have some auto-renewal functionality we funded working, while we work on more improvements (we are NOT using the template toolkit, relying on workarounds to offer reasonably useful auto-renewal features). Our problems started in the summer vacation soon after the upgrade, where Koha returns functionality became unstable. It was taking 8 seconds to return one item. Our support company advised that it was the AddReturn (and, in particular, MarkIssueReturned) which was the pinch point. Seems some code to resolve the auto_increment bug works slower in 17.05 and our support company was correcting that with a view (I understand) to adding it to Master. Things improved a little, but with the start of term almost 2 weeks ago we are encountering so many problems... "We were alerted to issues at 4.22pm. and found that the plack server was no longer responding. We restarted plack and then apache and the service restored. We are trying to get to the bottom of what caused this issue. It appears to be completely separate from the high CPU problem that we are also seeing." I understand more resources have been allocated to mySQL and additional plack helpers have been allocated (whatever that means). We are heavy users of SIP (80% of transactions are via self issue). But there are so many problems with the returns unit that they are almost unusable. Front line staff are fed up! The sorters and the kiosks configured for returns (as well as issue) fail repeatedly dozens of times daily (ERR_SIP_COM_RECV). Reconnection does happen- takes about 40seconds or so, leading to queues. And the items have NOT come off the account and flow into the exceptions bin. At the same time the intranet report 500 server errors. I am pretty sure most of our problems are related to returns code, but could well be wrong/ oversimplifying things. Our support company advised: "We have added extra logging and can see that some checkin requests via the SIP2 protocol are causing the sipserver process to abort. The book is returned within Koha but as the process returns no information to the SIP2 client therefore the unit responds with an error. After waiting for the timeout period it then will reconnect to the server. We are adding further debug to the logs to work out why the sipserver process is aborting. It does seem to be a special subset of the checkin requests. I'll update you when we have more news." And more problems relating to total outages (with proxy errors 502 relating to invalid responses from an upstream server): "There appears to be a number of issues you are experiencing. Friday you had high CPU usage which is different to today's issues which we think are down to the apache webserver not restarting correctly. I will double check first thing tomorrow that the overnight apache restart has occurred properly. We are hoping the database connections change may address the high CPU issue. We will monitor closely for the errors we have seen in the apache error logs tomorrow." We are a university with 20,000 students across 6 colleges, and right now inductions and training in OPAC use is going on with new students. These continual problems are deeply embarrassing, and faith in the Koha system is dropping rapidly. Has any other Koha 17.05 user (especially one heavily reliant on SIP) experienced anything like this? Has anyone out there any suggestions? Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY ------------------------------ Message: 8 Date: Thu, 12 Oct 2017 12:25:13 +0000 From: Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Major, multiple problems with our Koha 17.05 system. Message-ID: <VI1PR05MB3487F8E520F21EA675CA2957CE4B0(a)VI1PR05MB3487.eurprd05.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Very sorry to hear about your problems, Raymond. Cant say very much about it, since we do not yet use 17.05. But you should be searching on Bugzilla for the reports that got recently backported to 17.05.x. Might just include some that you need. Upgrading to the latest 17.05 would then perhaps address some issues. Just a side note: Very long delays in the past have been the result of date calculations with very far future dates like 9999 in expiry dates etc. Setting them back temporarily has been helpful in the past. (No guarantees; may be other factors involved.) Since your system is extensively customized, it could be helpful (for you) to know if your system without custom changes in a test environment would still experience the same problems.. And what about: Does your server have enough CPU and memory, etc ? Just a few remarks. Marcel -----Oorspronkelijk bericht----- Van: Koha [mailto:koha-bounces@lists.katipo.co.nz] Namens Raymund Delahunty Verzonden: donderdag 12 oktober 2017 13:29 Aan: koha(a)lists.katipo.co.nz Onderwerp: [Koha] Major, multiple problems with our Koha 17.05 system. VERY long sorry, but our Koha system is virtually unusable and we need help! We are experiencing dozens of outages daily (both OPAC and intranet, more often only OPAC) with our Koha 17.05.01.000 (Debian 3.2.89-2, perl 5.020002, mysql 14.14, apache 2.4.10). Searches can take 15+ seconds. While university staff provide first tier support, we don't have server access, and the second tier and hosting is via an external company. Of course we are working with that company to have them identify the cause, but I have decided to ask the community of any user on 17.05 has the problems we have. Our system is quite extensively customised, with major work done to the OPAC at https://libsearch.arts.ac.uk<https://libsearch.arts.ac.uk/>. We have some auto-renewal functionality we funded working, while we work on more improvements (we are NOT using the template toolkit, relying on workarounds to offer reasonably useful auto-renewal features). Our problems started in the summer vacation soon after the upgrade, where Koha returns functionality became unstable. It was taking 8 seconds to return one item. Our support company advised that it was the AddReturn (and, in particular, MarkIssueReturned) which was the pinch point. Seems some code to resolve the auto_increment bug works slower in 17.05 and our support company was correcting that with a view (I understand) to adding it to Master. Things improved a little, but with the start of term almost 2 weeks ago we are encountering so many problems... "We were alerted to issues at 4.22pm. and found that the plack server was no longer responding. We restarted plack and then apache and the service restored. We are trying to get to the bottom of what caused this issue. It appears to be completely separate from the high CPU problem that we are also seeing." I understand more resources have been allocated to mySQL and additional plack helpers have been allocated (whatever that means). We are heavy users of SIP (80% of transactions are via self issue). But there are so many problems with the returns unit that they are almost unusable. Front line staff are fed up! The sorters and the kiosks configured for returns (as well as issue) fail repeatedly dozens of times daily (ERR_SIP_COM_RECV). Reconnection does happen- takes about 40seconds or so, leading to queues. And the items have NOT come off the account and flow into the exceptions bin. At the same time the intranet report 500 server errors. I am pretty sure most of our problems are related to returns code, but could well be wrong/ oversimplifying things. Our support company advised: "We have added extra logging and can see that some checkin requests via the SIP2 protocol are causing the sipserver process to abort. The book is returned within Koha but as the process returns no information to the SIP2 client therefore the unit responds with an error. After waiting for the timeout period it then will reconnect to the server. We are adding further debug to the logs to work out why the sipserver process is aborting. It does seem to be a special subset of the checkin requests. I'll update you when we have more news." And more problems relating to total outages (with proxy errors 502 relating to invalid responses from an upstream server): "There appears to be a number of issues you are experiencing. Friday you had high CPU usage which is different to today's issues which we think are down to the apache webserver not restarting correctly. I will double check first thing tomorrow that the overnight apache restart has occurred properly. We are hoping the database connections change may address the high CPU issue. We will monitor closely for the errors we have seen in the apache error logs tomorrow." We are a university with 20,000 students across 6 colleges, and right now inductions and training in OPAC use is going on with new students. These continual problems are deeply embarrassing, and faith in the Koha system is dropping rapidly. Has any other Koha 17.05 user (especially one heavily reliant on SIP) experienced anything like this? Has anyone out there any suggestions? Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 144, Issue 17 ************************************* ------------------------------ Message: 3 Date: Thu, 12 Oct 2017 14:16:22 +0000 From: Tomas Cohen Arazi <tomascohen(a)gmail.com> To: koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Major, multiple problems with our Koha 17.05 system. Message-ID: <CABZfb=XgDSBVrifwYJv5767R+TyrWsd7J-TGa989jXO9BOV6ew(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" El jue., 12 oct. 2017 a las 8:29, Raymund Delahunty (<r.delahunty(a)arts.ac.uk>) escribió: > VERY long sorry, but our Koha system is virtually unusable and we need > help! > > We are experiencing dozens of outages daily (both OPAC and intranet, more > often only OPAC) with our Koha 17.05.01.000 (Debian 3.2.89-2, perl > 5.020002, mysql 14.14, apache 2.4.10). Searches can take 15+ seconds. While > university staff provide first tier support, we don't have server access, > and the second tier and hosting is via an external company. Of course we > are working with that company to have them identify the cause, but I have > decided to ask the community of any user on 17.05 has the problems we have. It seems you haven't enabled Plack on your setup. Those numbers are really wrong. -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F ------------------------------ Message: 4 Date: Thu, 12 Oct 2017 14:34:13 +0000 From: Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> To: Raymund Delahunty <r.delahunty(a)arts.ac.uk>, "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Major, multiple problems with our Koha 17.05 system. Message-ID: <CAJzKNY4-1u6LfY_=n+H0DOs-4LN=2Q+EwAUiOdS++cgBYkVKWw(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" I am a bit desperate because I already told several times on this list that some versions of Koha must not be used. See https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix and you will see that 17.05.01 is a buggy version My recommendation is to upgrade ASAP to the latest 17.05.x Maybe it will not change anything, but you should not use this version anyway. Regards, Jonathan On Thu, 12 Oct 2017 at 08:29 Raymund Delahunty <r.delahunty(a)arts.ac.uk> wrote: > VERY long sorry, but our Koha system is virtually unusable and we need > help! > > We are experiencing dozens of outages daily (both OPAC and intranet, more > often only OPAC) with our Koha 17.05.01.000 (Debian 3.2.89-2, perl > 5.020002, mysql 14.14, apache 2.4.10). Searches can take 15+ seconds. While > university staff provide first tier support, we don't have server access, > and the second tier and hosting is via an external company. Of course we > are working with that company to have them identify the cause, but I have > decided to ask the community of any user on 17.05 has the problems we have. > > Our system is quite extensively customised, with major work done to the > OPAC at https://libsearch.arts.ac.uk<https://libsearch.arts.ac.uk/>. We > have some auto-renewal functionality we funded working, while we work on > more improvements (we are NOT using the template toolkit, relying on > workarounds to offer reasonably useful auto-renewal features). > > Our problems started in the summer vacation soon after the upgrade, where > Koha returns functionality became unstable. It was taking 8 seconds to > return one item. Our support company advised that it was the AddReturn > (and, in particular, MarkIssueReturned) which was the pinch point. Seems > some code to resolve the auto_increment bug works slower in 17.05 and our > support company was correcting that with a view (I understand) to adding it > to Master. > > Things improved a little, but with the start of term almost 2 weeks ago we > are encountering so many problems... > > "We were alerted to issues at 4.22pm. and found that the plack server was > no longer responding. We restarted plack and then apache and the service > restored. We are trying to get to the bottom of what caused this issue. It > appears to be completely separate from the high CPU problem that we are > also seeing." > > I understand more resources have been allocated to mySQL and additional > plack helpers have been allocated (whatever that means). > > We are heavy users of SIP (80% of transactions are via self issue). But > there are so many problems with the returns unit that they are almost > unusable. Front line staff are fed up! The sorters and the kiosks > configured for returns (as well as issue) fail repeatedly dozens of times > daily (ERR_SIP_COM_RECV). Reconnection does happen- takes about 40seconds > or so, leading to queues. And the items have NOT come off the account and > flow into the exceptions bin. At the same time the intranet report 500 > server errors. I am pretty sure most of our problems are related to returns > code, but could well be wrong/ oversimplifying things. > > Our support company advised: > "We have added extra logging and can see that some checkin requests via > the SIP2 protocol are causing the sipserver process to abort. The book is > returned within Koha but as the process returns no information to the SIP2 > client therefore the unit responds with an error. After waiting for the > timeout period it then will reconnect to the server. We are adding further > debug to the logs to work out why the sipserver process is aborting. It > does seem to be a special subset of the checkin requests. I'll update you > when we have more news." > > And more problems relating to total outages (with proxy errors 502 > relating to invalid responses from an upstream server): > > "There appears to be a number of issues you are experiencing. Friday you > had high CPU usage which is different to today's issues which we think are > down to the apache webserver not restarting correctly. I will double check > first thing tomorrow that the overnight apache restart has occurred > properly. We are hoping the database connections change may address the > high CPU issue. We will monitor closely for the errors we have seen in the > apache error logs tomorrow." > > We are a university with 20,000 students across 6 colleges, and right now > inductions and training in OPAC use is going on with new students. These > continual problems are deeply embarrassing, and faith in the Koha system is > dropping rapidly. Has any other Koha 17.05 user (especially one heavily > reliant on SIP) experienced anything like this? Has anyone out there any > suggestions? > > > Ray Delahunty > University of the Arts London > > > This email and any attachments are intended solely for the addressee and > may contain confidential information. If you are not the intended recipient > of this email and/or its attachments you must not take any action based > upon them and you must not copy or show them to anyone. Please send the > email back to us and immediately and permanently delete it and its > attachments. Where this email is unrelated to the business of University of > the Arts London or of any of its group companies the opinions expressed in > it are the opinions of the sender and do not necessarily constitute those > of University of the Arts London (or the relevant group company). Where the > sender's signature indicates that the email is sent on behalf of UAL Short > Courses Limited the following also applies: UAL Short Courses Limited is a > company registered in England and Wales under company number 02361261. > Registered Office: University of the Arts London, 272 High Holborn, > London WC1V 7EY > <https://maps.google.com/?q=272+High+Holborn,+London+WC1V+7EY&entry=gmail&so…> > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 144, Issue 18 *************************************

1 0

Major, multiple problems with our Koha 17.05 system.
by Raymund Delahunty 12 Oct '17

12 Oct '17

VERY long sorry, but our Koha system is virtually unusable and we need help! We are experiencing dozens of outages daily (both OPAC and intranet, more often only OPAC) with our Koha 17.05.01.000 (Debian 3.2.89-2, perl 5.020002, mysql 14.14, apache 2.4.10). Searches can take 15+ seconds. While university staff provide first tier support, we don't have server access, and the second tier and hosting is via an external company. Of course we are working with that company to have them identify the cause, but I have decided to ask the community of any user on 17.05 has the problems we have. Our system is quite extensively customised, with major work done to the OPAC at https://libsearch.arts.ac.uk<https://libsearch.arts.ac.uk/>. We have some auto-renewal functionality we funded working, while we work on more improvements (we are NOT using the template toolkit, relying on workarounds to offer reasonably useful auto-renewal features). Our problems started in the summer vacation soon after the upgrade, where Koha returns functionality became unstable. It was taking 8 seconds to return one item. Our support company advised that it was the AddReturn (and, in particular, MarkIssueReturned) which was the pinch point. Seems some code to resolve the auto_increment bug works slower in 17.05 and our support company was correcting that with a view (I understand) to adding it to Master. Things improved a little, but with the start of term almost 2 weeks ago we are encountering so many problems... "We were alerted to issues at 4.22pm. and found that the plack server was no longer responding. We restarted plack and then apache and the service restored. We are trying to get to the bottom of what caused this issue. It appears to be completely separate from the high CPU problem that we are also seeing." I understand more resources have been allocated to mySQL and additional plack helpers have been allocated (whatever that means). We are heavy users of SIP (80% of transactions are via self issue). But there are so many problems with the returns unit that they are almost unusable. Front line staff are fed up! The sorters and the kiosks configured for returns (as well as issue) fail repeatedly dozens of times daily (ERR_SIP_COM_RECV). Reconnection does happen- takes about 40seconds or so, leading to queues. And the items have NOT come off the account and flow into the exceptions bin. At the same time the intranet report 500 server errors. I am pretty sure most of our problems are related to returns code, but could well be wrong/ oversimplifying things. Our support company advised: "We have added extra logging and can see that some checkin requests via the SIP2 protocol are causing the sipserver process to abort. The book is returned within Koha but as the process returns no information to the SIP2 client therefore the unit responds with an error. After waiting for the timeout period it then will reconnect to the server. We are adding further debug to the logs to work out why the sipserver process is aborting. It does seem to be a special subset of the checkin requests. I'll update you when we have more news." And more problems relating to total outages (with proxy errors 502 relating to invalid responses from an upstream server): "There appears to be a number of issues you are experiencing. Friday you had high CPU usage which is different to today's issues which we think are down to the apache webserver not restarting correctly. I will double check first thing tomorrow that the overnight apache restart has occurred properly. We are hoping the database connections change may address the high CPU issue. We will monitor closely for the errors we have seen in the apache error logs tomorrow." We are a university with 20,000 students across 6 colleges, and right now inductions and training in OPAC use is going on with new students. These continual problems are deeply embarrassing, and faith in the Koha system is dropping rapidly. Has any other Koha 17.05 user (especially one heavily reliant on SIP) experienced anything like this? Has anyone out there any suggestions? Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

5 4

Elasticsearch on BWS Sandboxes
by Nick Clemens 12 Oct '17

12 Oct '17

Hi All, Just an update to ES testing, we have now made Elasticsearch available on the BWS sandboxes: http://sandbox.bywatersolutions.com/cgi-bin/sandbox-dashboard.pl You will need to set the 'SearchEngine' system preference once the sandbox is setup, but records should be indexed and ready to go. If you have any questions or problems please let me know via email or in IRC. -Nick (kidclamp)

2 1

Elasticsearch on BWS Sandboxes
by BOUIS Sonia 12 Oct '17

12 Oct '17

What a good news ! Thank you Nick ! Sonia ------------------------------ Message: 6 Date: Thu, 12 Oct 2017 11:26:29 +0000 From: Nick Clemens <nick(a)bywatersolutions.com> To: Koha Devel <koha-devel(a)lists.koha-community.org>, Koha <koha(a)lists.katipo.co.nz>, ByWater Partners <partners(a)bywatersolutions.com> Subject: [Koha] Elasticsearch on BWS Sandboxes Message-ID: <CAA_eX3NAO1ktbRn4w00nxKausLBgn4sEGQVAywPuq75NarRhLA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi All, Just an update to ES testing, we have now made Elasticsearch available on the BWS sandboxes: http://sandbox.bywatersolutions.com/cgi-bin/sandbox-dashboard.pl You will need to set the 'SearchEngine' system preference once the sandbox is setup, but records should be indexed and ready to go. If you have any questions or problems please let me know via email or in IRC. -Nick (kidclamp) ------------------------------ Message: 7 Date: Thu, 12 Oct 2017 11:29:17 +0000 From: Raymund Delahunty <r.delahunty(a)arts.ac.uk> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Major, multiple problems with our Koha 17.05 system. Message-ID: <HE1PR0601MB2156A4DCC397D0A6FEB95796DC4B0(a)HE1PR0601MB2156.eurprd06.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" VERY long sorry, but our Koha system is virtually unusable and we need help! We are experiencing dozens of outages daily (both OPAC and intranet, more often only OPAC) with our Koha 17.05.01.000 (Debian 3.2.89-2, perl 5.020002, mysql 14.14, apache 2.4.10). Searches can take 15+ seconds. While university staff provide first tier support, we don't have server access, and the second tier and hosting is via an external company. Of course we are working with that company to have them identify the cause, but I have decided to ask the community of any user on 17.05 has the problems we have. Our system is quite extensively customised, with major work done to the OPAC at https://libsearch.arts.ac.uk<https://libsearch.arts.ac.uk/>. We have some auto-renewal functionality we funded working, while we work on more improvements (we are NOT using the template toolkit, relying on workarounds to offer reasonably useful auto-renewal features). Our problems started in the summer vacation soon after the upgrade, where Koha returns functionality became unstable. It was taking 8 seconds to return one item. Our support company advised that it was the AddReturn (and, in particular, MarkIssueReturned) which was the pinch point. Seems some code to resolve the auto_increment bug works slower in 17.05 and our support company was correcting that with a view (I understand) to adding it to Master. Things improved a little, but with the start of term almost 2 weeks ago we are encountering so many problems... "We were alerted to issues at 4.22pm. and found that the plack server was no longer responding. We restarted plack and then apache and the service restored. We are trying to get to the bottom of what caused this issue. It appears to be completely separate from the high CPU problem that we are also seeing." I understand more resources have been allocated to mySQL and additional plack helpers have been allocated (whatever that means). We are heavy users of SIP (80% of transactions are via self issue). But there are so many problems with the returns unit that they are almost unusable. Front line staff are fed up! The sorters and the kiosks configured for returns (as well as issue) fail repeatedly dozens of times daily (ERR_SIP_COM_RECV). Reconnection does happen- takes about 40seconds or so, leading to queues. And the items have NOT come off the account and flow into the exceptions bin. At the same time the intranet report 500 server errors. I am pretty sure most of our problems are related to returns code, but could well be wrong/ oversimplifying things. Our support company advised: "We have added extra logging and can see that some checkin requests via the SIP2 protocol are causing the sipserver process to abort. The book is returned within Koha but as the process returns no information to the SIP2 client therefore the unit responds with an error. After waiting for the timeout period it then will reconnect to the server. We are adding further debug to the logs to work out why the sipserver process is aborting. It does seem to be a special subset of the checkin requests. I'll update you when we have more news." And more problems relating to total outages (with proxy errors 502 relating to invalid responses from an upstream server): "There appears to be a number of issues you are experiencing. Friday you had high CPU usage which is different to today's issues which we think are down to the apache webserver not restarting correctly. I will double check first thing tomorrow that the overnight apache restart has occurred properly. We are hoping the database connections change may address the high CPU issue. We will monitor closely for the errors we have seen in the apache error logs tomorrow." We are a university with 20,000 students across 6 colleges, and right now inductions and training in OPAC use is going on with new students. These continual problems are deeply embarrassing, and faith in the Koha system is dropping rapidly. Has any other Koha 17.05 user (especially one heavily reliant on SIP) experienced anything like this? Has anyone out there any suggestions? Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY ------------------------------ Message: 8 Date: Thu, 12 Oct 2017 12:25:13 +0000 From: Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Major, multiple problems with our Koha 17.05 system. Message-ID: <VI1PR05MB3487F8E520F21EA675CA2957CE4B0(a)VI1PR05MB3487.eurprd05.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Very sorry to hear about your problems, Raymond. Cant say very much about it, since we do not yet use 17.05. But you should be searching on Bugzilla for the reports that got recently backported to 17.05.x. Might just include some that you need. Upgrading to the latest 17.05 would then perhaps address some issues. Just a side note: Very long delays in the past have been the result of date calculations with very far future dates like 9999 in expiry dates etc. Setting them back temporarily has been helpful in the past. (No guarantees; may be other factors involved.) Since your system is extensively customized, it could be helpful (for you) to know if your system without custom changes in a test environment would still experience the same problems.. And what about: Does your server have enough CPU and memory, etc ? Just a few remarks. Marcel -----Oorspronkelijk bericht----- Van: Koha [mailto:koha-bounces@lists.katipo.co.nz] Namens Raymund Delahunty Verzonden: donderdag 12 oktober 2017 13:29 Aan: koha(a)lists.katipo.co.nz Onderwerp: [Koha] Major, multiple problems with our Koha 17.05 system. VERY long sorry, but our Koha system is virtually unusable and we need help! We are experiencing dozens of outages daily (both OPAC and intranet, more often only OPAC) with our Koha 17.05.01.000 (Debian 3.2.89-2, perl 5.020002, mysql 14.14, apache 2.4.10). Searches can take 15+ seconds. While university staff provide first tier support, we don't have server access, and the second tier and hosting is via an external company. Of course we are working with that company to have them identify the cause, but I have decided to ask the community of any user on 17.05 has the problems we have. Our system is quite extensively customised, with major work done to the OPAC at https://libsearch.arts.ac.uk<https://libsearch.arts.ac.uk/>. We have some auto-renewal functionality we funded working, while we work on more improvements (we are NOT using the template toolkit, relying on workarounds to offer reasonably useful auto-renewal features). Our problems started in the summer vacation soon after the upgrade, where Koha returns functionality became unstable. It was taking 8 seconds to return one item. Our support company advised that it was the AddReturn (and, in particular, MarkIssueReturned) which was the pinch point. Seems some code to resolve the auto_increment bug works slower in 17.05 and our support company was correcting that with a view (I understand) to adding it to Master. Things improved a little, but with the start of term almost 2 weeks ago we are encountering so many problems... "We were alerted to issues at 4.22pm. and found that the plack server was no longer responding. We restarted plack and then apache and the service restored. We are trying to get to the bottom of what caused this issue. It appears to be completely separate from the high CPU problem that we are also seeing." I understand more resources have been allocated to mySQL and additional plack helpers have been allocated (whatever that means). We are heavy users of SIP (80% of transactions are via self issue). But there are so many problems with the returns unit that they are almost unusable. Front line staff are fed up! The sorters and the kiosks configured for returns (as well as issue) fail repeatedly dozens of times daily (ERR_SIP_COM_RECV). Reconnection does happen- takes about 40seconds or so, leading to queues. And the items have NOT come off the account and flow into the exceptions bin. At the same time the intranet report 500 server errors. I am pretty sure most of our problems are related to returns code, but could well be wrong/ oversimplifying things. Our support company advised: "We have added extra logging and can see that some checkin requests via the SIP2 protocol are causing the sipserver process to abort. The book is returned within Koha but as the process returns no information to the SIP2 client therefore the unit responds with an error. After waiting for the timeout period it then will reconnect to the server. We are adding further debug to the logs to work out why the sipserver process is aborting. It does seem to be a special subset of the checkin requests. I'll update you when we have more news." And more problems relating to total outages (with proxy errors 502 relating to invalid responses from an upstream server): "There appears to be a number of issues you are experiencing. Friday you had high CPU usage which is different to today's issues which we think are down to the apache webserver not restarting correctly. I will double check first thing tomorrow that the overnight apache restart has occurred properly. We are hoping the database connections change may address the high CPU issue. We will monitor closely for the errors we have seen in the apache error logs tomorrow." We are a university with 20,000 students across 6 colleges, and right now inductions and training in OPAC use is going on with new students. These continual problems are deeply embarrassing, and faith in the Koha system is dropping rapidly. Has any other Koha 17.05 user (especially one heavily reliant on SIP) experienced anything like this? Has anyone out there any suggestions? Ray Delahunty University of the Arts London This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 144, Issue 17 *************************************

1 0

Thanks for help on GBSD!
by Nick Clemens 12 Oct '17

12 Oct '17

Hi All, Thanks to efforts from you, the community, the NSO queue is under 150 and you have given the QA team a bit more work to catch up on :-) Remember, if you keep GBSD in your heart we can squash bugs all year long. Every bug squashed makes for a better Koha. There's (almost) always someone around in IRC to help and we are happy to answer any questions about testing or getting involved, or just to say hi. Hoping to see you soon. -Nick (kidclamp)

1 0

OPAC open in new window
by Marian May A. Marquez 12 Oct '17

12 Oct '17

Hi! At the backend cataloguing of koha, whenever I click "open in new window" to view the opac of a record, the page won't load. Please help. Thanks! Best regards,May

3 2

Problems with MARC framework test.
by Hector Gonzalez 12 Oct '17

12 Oct '17

Hi, I recently installed a new koha server, with version 17.05.04, and was trying it out, but found this, I have no idea why this would be wrong (I have not edited the framework): MARC bibliographic framework test Test Result itemnum * The field itemnum MUST be mapped * The corresponding subfield MUST be in with -1 (ignore) tab item fields ALL items fields MUST : * be mapped to the same tag, * and they must all be in the 10 (items) tab OK Only 1 MARC tag mapped to items OK biblioitems.itemtype defined homebranch NOT mapped the items.homebranch field MUST : * be mapped to a MARC subfield, * the corresponding subfield MUST have "Authorized value" set to "branches" holdingbranch NOT mapped the items.holdingbranch field MUST : * be mapped to a MARC subfield, * the corresponding subfield MUST have "Authorized value" set to "branches" OK at least 1 item type defined OK at least 1 library defined biblio and biblionumber The biblio.biblionumber and biblioitems.biblioitemnumber fields be mapped to a MARC subfield, OK no NULL value in frameworkcode OK all subfields for each tag are in the same tab (or ignored) OK all authority types used in the frameworks are defined OK items.permanent_location is not mapped on the frameworks TOTAL You have 5 error(s) in your MARC configuration. Please fix them before using Koha I can't find the errors, or where the errors are. do you have any suggestions? Thanks in advance. -- Héctor González cacho(a)genac.org

2 2

Re: [Koha] opac search
by Erlanda Simonyan 12 Oct '17

12 Oct '17

----- Original Message ----- From: Erlanda Simonyan To: koha(a)lists.katipo.co.nz Sent: Thursday, October 12, 2017 11:22 AM Subject: opac search Dear list, We have some problems in opac search in koha 17.05. When we search for a keyword and from the result page and the column of "refine your search" we clikck on any author's name that contains a hyphen, for example a.. Տեր-Մարտիրոսյան, Ռուբինա , we get no result . See photos attached. b.. Thanks a..

1 0

Re: [Koha] Koha Digest, Vol 144, Issue 13
by Jamil Ahmed 11 Oct '17

11 Oct '17

Hi, Can we generate reports of koha in pdf format Regards On Tue, Oct 10, 2017 at 8:18 PM, <koha-request(a)lists.katipo.co.nz> wrote: > Send Koha mailing list submissions to > koha(a)lists.katipo.co.nz > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.katipo.co.nz/mailman/listinfo/koha > or, via email, send a message with subject or body 'help' to > koha-request(a)lists.katipo.co.nz > > You can reach the person managing the list at > koha-owner(a)lists.katipo.co.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha digest..." > > > Today's Topics: > > 1. OPAC open in new window (Marian May A. Marquez) > 2. Re: OPAC open in new window (schnydszch) > 3. Creating labels with barcodes not already in the system > (Michael Kuhn) > 4. Re: Creating labels with barcodes not already in the system > (Philippe Blouin) > 5. Checkout one item results in multiple items... (Tim Young) > 6. Re: Checkout one item results in multiple items... > (Marcel de Rooy) > 7. Request (Mike Ward) > 8. Koha password recovery doesn't seem to work (VISINI Giacomo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 10 Oct 2017 02:09:05 +0000 (UTC) > From: "Marian May A. Marquez" <mamaymarquez(a)yahoo.com> > To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz>, > "kohaus(a)lists.bywatersolutions.com" > <kohaus(a)lists.bywatersolutions.com> > Subject: [Koha] OPAC open in new window > Message-ID: <1793233770.4712716.1507601345057(a)mail.yahoo.com> > Content-Type: text/plain; charset=UTF-8 > > Hi! > At the backend cataloguing of koha, whenever I click "open in new window" > to view the opac of a record, the page won't load. > Please help. > Thanks! > > > > > > > > > > > > > > > > > Best regards,May > > > ------------------------------ > > Message: 2 > Date: Mon, 9 Oct 2017 23:15:14 -0700 (MST) > From: schnydszch <eugenegf(a)yahoo.com> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] OPAC open in new window > Message-ID: <1507616114424-0.post(a)n5.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Hi! What exactly is happening when you click the Open in new window? Is it > "The site can't be reached"? > There could be a misconfiguration in the OPACBaseURL which you can edit in > System Preferences > OPAC > OPACBaseURL. Please try to edit your base URL > to > the URL of your Koha installation, e.g. http://catalog. > bywatersolutions.com, > just what it is noted in the system preference: This should be a complete > URL, starting with http:// or https://. Do not include a trailing slash in > the URL. (This must be filled in correctly for RSS, unAPI, and search > plugins to work.). If the Koha ILS installation is only available locally > within you network, you can get the assigned IP address for the server > where > Koha ILS is installed, e.g. http://192.168.2.11. HTH! > > > > -- > Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html > > > ------------------------------ > > Message: 3 > Date: Tue, 10 Oct 2017 14:30:02 +0200 > From: Michael Kuhn <mik(a)adminkuhn.ch> > To: "Koha : access" <koha(a)lists.katipo.co.nz> > Subject: [Koha] Creating labels with barcodes not already in the > system > Message-ID: <a264b505-dcd4-b2b9-6ef1-4f03f9d8c718(a)adminkuhn.ch> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi > > Using the label creator we want to generate a number of barcodes but it > seems the label creator can only create a label batch if the barcodes > are already existing in Koha. > > How can we create a sheet with labels of barcodes (simply consecutive > numbers like 74180238 74180239 74180240 etc.) that are not yet existing > in Koha? When cataloging, first creating the record and the item, we > then just want to pick one of the labels on the sheet and read the > barcode number into MARC 952 $p, then sticking the label on the item. > > How can this be achieved? Any hint is appreciated. > > 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 > > > ------------------------------ > > Message: 4 > Date: Tue, 10 Oct 2017 08:46:13 -0400 > From: Philippe Blouin <philippe.blouin(a)inlibro.com> > To: mik(a)adminkuhn.ch, koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Creating labels with barcodes not already in the > system > Message-ID: <47946f33-147d-9dcd-89ab-5e4949828bfe(a)inlibro.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Michael, > > This is not possible in Koha at this moment. You can check Bug 7468 > that offers a patch to fix that. > > Philippe Blouin, > Responsable du développement informatique > > Tél. : (833) 465-4276, poste 230 > philippe.blouin(a)inLibro.com <mailto:philippe.blouin@inLibro.com> > > inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> > On 10/10/2017 08:30 AM, Michael Kuhn wrote: > > Hi > > > > Using the label creator we want to generate a number of barcodes but > > it seems the label creator can only create a label batch if the > > barcodes are already existing in Koha. > > > > How can we create a sheet with labels of barcodes (simply consecutive > > numbers like 74180238 74180239 74180240 etc.) that are not yet > > existing in Koha? When cataloging, first creating the record and the > > item, we then just want to pick one of the labels on the sheet and > > read the barcode number into MARC 952 $p, then sticking the label on > > the item. > > > > How can this be achieved? Any hint is appreciated. > > > > Best wishes: Michael > > > > ------------------------------ > > Message: 5 > Date: Tue, 10 Oct 2017 09:01:12 -0500 > From: Tim Young <Tim.Young(a)LightSys.org> > To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> > Subject: [Koha] Checkout one item results in multiple items... > Message-ID: <091ad026-a0fc-8558-4605-901bed6e88cb(a)LightSys.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > We have started experiencing a recent issue where attempting to check > out one item results in multiple of those items (same barcode, checked > out multiple times) being checked out to the one patron. This does not > happen to every item, nor does it happen to every patron. > > I am not sure if this error has to do with the problem, but I am seeing > errors like: > > [Tue Oct 10 15:49:58.258993 2017] [cgi:error] [pid 20067] [client > 41.89.41.2:23363] AH01215: [Tue Oct 10 15:49:58 2017] additem.pl: > DBIx::Class::Storage::DBI::select_single(): Query returned more than one > row. SQL that returns multiple rows is DEPRECATED for ->find and > ->single at /usr/share/koha/lib/Koha/Objects.pm line 92, referer: > http://opac.scott.ac.ke:8080/cgi-bin/koha/cataloguing/ > additem.pl?op=edititem&biblionumber=15157&itemnumber=25724 > > showing up in the internet-error.log > > Any clue how I should begin tracking this down? > > - Tim > > > > ------------------------------ > > Message: 6 > Date: Tue, 10 Oct 2017 14:19:43 +0000 > From: Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl> > To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Checkout one item results in multiple items... > Message-ID: > <VI1PR05MB3487CC045BE8A2B344BFC823CE750@VI1PR05MB3487. > eurprd05.prod.outlook.com> > > Content-Type: text/plain; charset="iso-8859-1" > > Adding your exact Koha version might be helpful too. > > > Marcel > > ________________________________ > Van: Koha <koha-bounces(a)lists.katipo.co.nz> namens Tim Young > <Tim.Young(a)LightSys.org> > Verzonden: dinsdag 10 oktober 2017 16:01:12 > Aan: koha(a)lists.katipo.co.nz > Onderwerp: [Koha] Checkout one item results in multiple items... > > We have started experiencing a recent issue where attempting to check > out one item results in multiple of those items (same barcode, checked > out multiple times) being checked out to the one patron. This does not > happen to every item, nor does it happen to every patron. > > I am not sure if this error has to do with the problem, but I am seeing > errors like: > > [Tue Oct 10 15:49:58.258993 2017] [cgi:error] [pid 20067] [client > 41.89.41.2:23363] AH01215: [Tue Oct 10 15:49:58 2017] additem.pl: > DBIx::Class::Storage::DBI::select_single(): Query returned more than one > row. SQL that returns multiple rows is DEPRECATED for ->find and > ->single at /usr/share/koha/lib/Koha/Objects.pm line 92, referer: > http://opac.scott.ac.ke:8080/cgi-bin/koha/cataloguing/ > additem.pl?op=edititem&biblionumber=15157&itemnumber=25724 > > showing up in the internet-error.log > > Any clue how I should begin tracking this down? > > - Tim > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > Message: 7 > Date: Tue, 10 Oct 2017 10:43:35 -0400 > From: Mike Ward <wardm(a)clintondaleschools.net> > To: Koha(a)lists.katipo.co.nz > Subject: [Koha] Request > Message-ID: > <CAFKgftiLmAQp=UazhOmYuUWJJqv1+GLONOZQPtOmf56Muzz-Sw@mail. > gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Please remove me from this list. > > Thanks, > > Mike Ward > > > ------------------------------ > > Message: 8 > Date: Tue, 10 Oct 2017 14:47:56 +0000 > From: VISINI Giacomo <Giacomo.VISINI(a)divaantwerp.be> > To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> > Subject: [Koha] Koha password recovery doesn't seem to work > Message-ID: > <AM3PR08MB05968C80C179153B3A10A0BEEF750@AM3PR08MB0596. > eurprd08.prod.outlook.com> > > Content-Type: text/plain; charset="us-ascii" > > Hello, > > I've been having issues setting up a password recovery in Koha (version > 16.11.12.000). I've did all the necessary steps, as explained in the manual. > > In short this: > > 1. Go to Administration > 2. System Preferences > 3. OPAC Preferences > 4. Opacresetpassword<http://translate.koha-community.org/ > manual/16.05/en/html-desktop/#OpacResetPassword> : Library users are > "allowed" to recover their password via email in the OPAC. > 5. A notice must be set up in the Notices and Slips section > * Go to Tools > * Notices and Slips > * Verify there is a notice set up called Password_Reset > Everything seems to be working fine. I can choose 'Forgot password' in > OPAC, then I can enter a login name and/or email address. I receive a link > in my mailbox saying: > > This email has been sent in response to your password recovery request for > the account XXX.XXX. > You can now create your new password using the following link: > /cgi-bin/koha/opac-password-recovery.pl?uniqueKey=$2a$08$ > DDiNbAFWtNLz80gWHQxUbe<http://cgi-bin/koha/opac-password- > recovery.pl?uniqueKey=$2a$08$DDiNbAFWtNLz80gWHQxUbe> > This link will be valid for 2 days from this email's reception, then you > must reapply if you do not change your password. > Thank you. > > Unfortunately the link doesn't seem to work. I've tried several times > under several accounts. The link is always faulty. > > The same thing happens when I want to set up a verify-by-email for the > self-registering patron (PatronSelfRegistrationVerifyByEmail). All goes > well like above, until I click the link sent to me: > > Hello! Your library account has been created. Please verify your email > address by clicking this link to complete the signup process: /cgi-bin/koha/ > opac-registration-verify.pl?token=1b9cbb3ba7da22d9751aa4b9f15973b1< > http://opac-registration-verify.pl/?token=1b9cbb3ba7da22d9751aa4b9f15973b1> > If you did not initiate this request, you may safely ignore this one-time > message. The request will expire shortly. > > Has anybody experienced this problem? Can anybody give an explanation or a > solution? I didn't see any reportings of this exact issue. > > Many thanks in advance! > > With kind regards, > > > Giacomo Visini > +32(0)3 360 52 41 > giacomo.visini(a)divaantwerp.be > > Gildekamersstraat 9, B-2000 Antwerpen > > Disclaimer: Op deze e-mail is de wet van 13 juni 2005 over het > vertrouwelijke karakter van elektronische communicatie van toepassing. De > tekst van het relevante artikel 124 kun je op onze website consulteren. > http://www.provincieantwerpen.be/over-deze-website.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 144, Issue 13 > ************************************* > -- Jamil Ahmed. Assistant Librarian Bennett University

2 1