September 2022 - Koha-devel - lists.koha-community.org

Libraries using MARC 880 will need a fix...
by dcook＠prosentient.com.au 09 Sep '22

09 Sep '22

Hi all, A couple months ago I wrote a fix for "Bug 15187 - Adding 880 Fields to index-list in order to Increase Search for ALL non-latin Scripts" for Zebra. While it worked in terms of adding 880 to the indexing, it created an unexpected problem with the search result display, since the MARC records in the search results are fetched from Zebra and not MySQL. Yesterday, I raised "Bug 31532 - Zebra search results incorrect because of Bug 15187". This uses pure Zebra configuration to use the same mechanism as Bug 15187 but only at the indexing stage. Records retrieved from Zebra will still be the original sent from Koha to Zebra. It's actually the original solution I wrote for Bug 15187 before thinking there was an easier way. Fwiw, Elasticsearch indexes the 880 in its own way in the Koha code. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Regular Koha Mailing list down ?
by Marcel de Rooy 07 Sep '22

07 Sep '22

Hi CHris, It seems that the mails to the regular Koha ML (katipo one) are not coming thru since September 1. The archive also shows August entries. Do you know how to resolve? Thanks, Marcel

2 1

Re: [Koha-devel] [Koha] DBMS auto increment fix not working
by Michael Kuhn 06 Sep '22

06 Sep '22

Hi Marcel Unfortunately it seems like the mailing list is not accepting my original answer to your e-mail (I tried twice). Instead after some days I received an e-mail with the subject "Undelivered Mail Returned to Sender", telling me The mail system <koha(a)lists.katipo.co.nz>: connect to lists.katipo.co.nz[202.70.130.220]:25: Connection refused I don't even know if this e-mail is getting through. There's probably something wrong with the mailing list when not accepting answers. 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 30.08.22 um 13:17 schrieb Marcel de Rooy: > Hi, > > The fact that it will no longer happen under MariaDB 10.5.15 does not guarantee that you still suffer the consequences of older occurrences. > The wiki promises a script but it never made it probably. But the easiest 'solution' is deleting the records in the deleted_* tables that have a corresponding id in the normal tables. > After that verify that your autoincrement pointers on the normal tables are higher than the maximum id values in the deleted tables. If they would not be, you may bump into the issue again one day. > > Marcel > > ________________________________ > Van: Koha <koha-bounces(a)lists.katipo.co.nz> namens Michael Kuhn <mik(a)adminkuhn.ch> > Verzonden: donderdag 25 augustus 2022 11:03 > Aan: Koha <koha(a)lists.katipo.co.nz> > Onderwerp: [Koha] DBMS auto increment fix not working > > Hi > > In our library we are using Debian 11 with MariaDB 10.5.15 and Koha > 21.05.14. > > When deleting bibliographic records in the staff client, some deletions > produce the message: "An error has occurred! Error 500 / This message > may have been caused by any of the following reasons: etc." In such > cases Koha menu "About Koha > System information" shows the message > aubout data problems, saying > > Some of your tables have problems with their auto_increment values > which may lead to data loss. > > You should not ignore this warning. > > The problem is that InnoDB does not keep auto_increment across SQL > server restarts (it is only set in memory). So on server startup the > auto_increment values are set to max(table.id)+1. > > To know how to avoid this problem see the related wiki page: DBMS auto > increment fix > > > According to > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.koha… the problem > shouldn't appear with MariaDB 10.5.15 but as a trial we have implemented > the solution described there and have restarted everything - still the > problem persists. > > In such cases file "plack-error.log" shows the following: > > {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry > '6187-marcxml-MARC21' for key 'deletedbiblio_metadata_uniq_key' [for > Statement " > INSERT INTO deletedbiblio_metadata (biblionumber, > format, `schema`, metadata) > SELECT biblionumber, format, `schema`, metadata FROM > biblio_metadata WHERE biblionumber=? > "] at /usr/share/koha/lib/C4/Biblio.pm line 2907 > > I suspect this behavior indeed looks like the original auto_increment > problem described in bugs 18242, 18651, 18966, 19106 and 20271 but the > reason may in fact not be the same since the described problem shouldn't > appear at all in MariaDB 10.5.15. > > Does anyone have an idea what is happening and how we can solve it? > > 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 https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.admink… > _______________________________________________ > > Koha mailing list https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-commu… > Koha(a)lists.katipo.co.nz > Unsubscribe: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.kat… > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

1 0