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

Re: [Koha-devel] {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' for key 'PRIMARY'
by Michael Kuhn 24 Jul '24

24 Jul '24

Hi Tomas I was able to solve the problem which apparently appeared because of a corrupt database dump. See my e-mail to mailinglist "koha-devel" from 22 Jul 17:38 (see below). Best wishes and many thanks: 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 24.07.24 um 14:25 schrieb Tomas Cohen Arazi: > > Hi, Michael. > > What DB engine and version are you using? > > Is it possible for you to share a dump for that DB to some of us for review? > > El mié, 10 jul 2024 a la(s) 7:46 a.m., Michael Kuhn via Koha-devel > (koha-devel(a)lists.koha-community.org > <mailto:koha-devel@lists.koha-community.org>) escribió: > > Hi > > We have loaded our Koha 19.11 database into a new Koha 24.05 instance. > When running "koha-upgrade-schema" the following error appears: > > ... > Upgrade to 19.12.00.017 [12:00:41]: Bug 21674 - Add unique key > (parent_id, branchcode) to library_group > {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' > for key 'PRIMARY' at /usr/share/perl5/DBIx/Class/Schema.pm line 1118. > > DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x55a4b4a0dba8), > "DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' "...) > called at /usr/share/perl5/DBIx/Class/Storage.pm line 113 > > DBIx::Class::Storage::throw_exception(DBIx::Class::Storage::DBI::mysql=HASH(0x55a4b9ff1b70), "DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' "...) called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1623 > DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::db do failed: > Duplicate entry '0' for key 'PRIMARY'", DBI::db=HASH(0x55a4ba7d2b38), > undef) called at > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl <http://updatedatabase.pl> > line 20736 > > > Does anyone know how to solve this problem? At the moment I'm not even > able to find out in which table the duplicate entry can be 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> > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> > website : https://www.koha-community.org/ > <https://www.koha-community.org/> > git : https://git.koha-community.org/ <https://git.koha-community.org/> > bugs : https://bugs.koha-community.org/ > <https://bugs.koha-community.org/> > -------- Weitergeleitete Nachricht -------- Betreff: Re: [Koha-devel] [Koha] {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' for key 'PRIMARY' Datum: Mon, 22 Jul 2024 17:38:04 +0200 Von: Michael Kuhn via Koha-devel <koha-devel(a)lists.koha-community.org> Antwort an: Michael Kuhn <mik(a)adminkuhn.ch> Organisation: Admin Kuhn GmbH An: Philippe Blouin <philippe.blouin(a)inlibro.com>, koha-devel(a)lists.koha-community.org Hi Philippe You wrote: > If you went with an existing 23.11 and tried to overwrite the database > with you 19.05 one, it's possible it got conflicts since it drop-and- > add in the order in the file and dependencies might break. Always > easier to just drop the old database and load the "new" one in an > empty space. Thanks for this hint! > Then you went from 19 to 23.06.00.013, which is much further, but then > failed on something unrelated to any previous error. (beside being a > constraint, like the primary key earlier). Cannot dropping something > that doesn't exist is NOT a deal breaker, so try > > comment installer/data/mysql/db_revs/230600014.pl line 11, and try > again. After all we found out the database dump I was provided with was corrupt or unusual in at least two ways: 1) it didn't contain the final line "Dump completed" and so really was incomplete, but 2) it did include lines like the following (and the corresponding SQL commands) that are usually not included in the database dump: -- Constraints der exportierten Tabellen -- Constraints der Tabelle `accountlines` -- Constraints der Tabelle `account_credit_types_branches` etc. etc. Provided with an incorrupt dump I was able to load it into the MariaDB server and the update from Koha 19.11 to 24.05 worked like a charm. No errors at all. Best wishes and many thanks for your help: 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 > On 2024-07-10 12:30, Michael Kuhn wrote: >> Hi Philippe >> >> You wrote: >> >> > If you're a bit adventurous (and have some time, which you're probably >> > thinking you've burnt enough already): try to update to 20.05, for >> > example, using 20.05 code. >> > >> > So you reset your installation (you have saved your DB, right?), then >> > instead of installing a 24.05, you install an older version, like >> > 20.05 and do the update. >> > >> > The specific lines in updatedatabase.pl probably are the same, but a >> > lot of underlying plumbing could be different and work badly with your >> > system. I'd start by ruling that out. >> >> 1. On an different host with Koha 23.11 I loaded the database which >> then showed the following error: >> >> ERROR 1452 (23000) at line 8292833: Cannot add or update a child row: >> a foreign key constraint fails (`koha_test`.`#sql-alter-368-2a`, >> CONSTRAINT `borrower_message_transport_preferences_ibfk_1` FOREIGN KEY >> (`borrower_message_preference_id`) REFERENCES >> `borrower_message_preferences` (`borrower_) >> >> 2. I didn't care for it and then tried to update the database. This >> time the update process went far far further but it still aborted here: >> >> Upgrade to 23.06.00.013 [17:56:51]: Bug 28966 - Holds queue view too >> slow to load for large numbers of holds >> ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't DROP >> CONSTRAINT `tmp_holdsqueue_ibfk_1`; check that it exists at >> /usr/share/koha/lib/C4/Installer.pm line 741 >> >> This seems to be a different problem and I'm hoping the solution could >> lead to the road of success... Do you happen to know how to solve this? >> >> 3. Furthermore I saw the database dump file I received for the update >> ends like this: >> >> -- >> -- Constraints der Tabelle `virtualshelves` >> -- >> ALTER TABLE `virtualshelves` >> ADD CONSTRAINT `virtualshelves_ibfk_1` FOREIGN KEY (`owner`) >> REFERENCES `borrowers` (`borrowernumber`) ON DELETE SET NULL ON UPDATE >> SET NULL; >> COMMIT; >> >> /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; >> /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; >> /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; >> >> while the database dump files I usually create myself do not contain >> constraints at all and end like this: >> >> -- Dump completed on 2024-07-10 6:25:22 >> >> Does this make sense to you? >> >> Best wishes: Michael _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/

1 0

{UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' for key 'PRIMARY'
by Michael Kuhn 22 Jul '24

22 Jul '24

Hi We have loaded our Koha 19.11 database into a new Koha 24.05 instance. When running "koha-upgrade-schema" the following error appears: ... Upgrade to 19.12.00.017 [12:00:41]: Bug 21674 - Add unique key (parent_id, branchcode) to library_group {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' for key 'PRIMARY' at /usr/share/perl5/DBIx/Class/Schema.pm line 1118. DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x55a4b4a0dba8), "DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' "...) called at /usr/share/perl5/DBIx/Class/Storage.pm line 113 DBIx::Class::Storage::throw_exception(DBIx::Class::Storage::DBI::mysql=HASH(0x55a4b9ff1b70), "DBI Exception: DBD::mysql::db do failed: Duplicate entry '0' "...) called at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1623 DBIx::Class::Storage::DBI::__ANON__("DBD::mysql::db do failed: Duplicate entry '0' for key 'PRIMARY'", DBI::db=HASH(0x55a4ba7d2b38), undef) called at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 20736 Does anyone know how to solve this problem? At the moment I'm not even able to find out in which table the duplicate entry can be 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

2 10

REMINDER: Development Jitsi meeting 17 July 2024
by Paul Derscheid 16 Jul '24

16 Jul '24

Hi all, We have a Development Jitsi meeting scheduled for tomorrow: https://wiki.koha-community.org/wiki/Development_IRC_meeting_17_July_2024 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. If you are lead or supporter of a roadmap project, we will be happy to get an update on progress. See you there! Paul

1 0

Call for news - Newsletter July 2024
by Koha Newsletter 13 Jul '24

13 Jul '24

Hi I'm collecting news for the July 2024 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

REMINDER: Development Jitsi meeting 3 July 2024
by Paul Derscheid 02 Jul '24

02 Jul '24

Hi all, We have a Development Jitsi meeting scheduled for tomorrow: https://wiki.koha-community.org/wiki/Development_IRC_meeting_3_July_2024 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+J… Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. If you are lead or supporter of a roadmap project, we will be happy to get an update on progress. See you there! Paul

1 0

Koha Community Newsletter: June 2024
by Koha Newsletter 27 Jun '24

27 Jun '24

The Koha Community Newsletter for June 2024 is here: https://koha-community.org/koha-community-newsletter-june-2024/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me (kohanews(a)gmail.com) with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Roadmap 24.11
by Fischer, Katrin 20 Jun '24

20 Jun '24

Hi all, it's high time to work on the roadmap for 24.11: https://wiki.koha-community.org/wiki/Roadmap_24.11 The roadmap is a list of small and big projects that we want to pursue during this release cycle, either as a community or individually. Please take the time to list your projects for this cycle and add your name to the projects that you can help with. We'll take time to discuss, review and advertise the roadmap projects during the next development meeting: https://wiki.koha-community.org/wiki/Development_IRC_meeting_3_July_2024 Deadline for the project proposals is July 2nd. There will be some additional time for adjustments after our discussion at the meeting. Happy editing! Katrin

1 0

Koha May release with security fixes
by Fridolin SOMERS 19 Jun '24

19 Jun '24

Hello everyone 🤗 The Koha community is proud to announce the release of May versions: 24.05.01 23.11.06 23.05.12 22.11.18 22.05.22 It is a bugfix/maintenance release including some security fixes. It is highly recommended to upgrade. The full release notes will soon be available here: https://koha-community.org/koha-24-05-01-released/ https://koha-community.org/koha-23-11-06-released/ https://koha-community.org/koha-23-05-12-released/ https://koha-community.org/koha-22-11-18-released/ https://koha-community.org/koha-22-05-22-released/ Debian packages are available. We now start 24.11 cycle, lets go. Best regards 🤓 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 1

Issues with persistent TCP connections in Microsoft Azure cloud
by David Cook 18 Jun '24

18 Jun '24

Hi all, We recently migrated a busy Koha instance from an on-premises server to an Azure cloud server. During that move, we also took the opportunity to switch to using Elasticsearch (not located on the same virtual machine). Over time, we noticed that we were getting issues with SIP2 connections and with Koha's Elasticsearch indexer worker timing out. Especially during the least busy parts of the day. After some investigation, we learned that Azure allows TCP connections to only be idle for a maximum of 4 minutes (https://learn.microsoft.com/en-us/azure/firewall/long-running-sessions) One solution is to implement application-level keepalives, but that wasn't practical with Koha's Elasticsearch client library or the SIP2 server. Instead, I opted to utilize Linux's TCP keepalive implementation, which operates at a lower level of the technology stack. Fortunately, Koha's Elasticsearch client library is already compatible with TCP keepalives, so I just needed to tweak the "net.ipv4.tcp_keepalive_time" kernel parameter via "sysctl". I dropped the keepalive to under the 4 minute threshold (from the default of 2 hours), and now no more timeouts with Koha's Elasticsearch indexer worker! Unfortunately, Koha's SIP2 server doesn't support the TCP keepalives out of the box. However, I've written a patch at "Bug 37087 - Add support for TCP keepalive to SIP server" which adds granular TCP keepalive support which can actually be configured via the SIPconfig.xml configuration file (without needing to change any kernel parameters at all). I've written up a bit about it on the wiki: https://wiki.koha-community.org/wiki/Koha_SIP2_server_setup#Microsoft_Azure_ cloud_platform https://wiki.koha-community.org/wiki/Elasticsearch#Microsoft_Azure_cloud_pla tform I hope that this information is useful to other people out in the world implementing Koha. It was a very annoying problem with a surprisingly simple solution in the end. 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

What's your opinion on sorting facets with diacritics? (Bug 36947)
by David Cook 18 Jun '24

18 Jun '24

Hi all, Lari Strand pointed out on Bug 36947 that Koha doesn’t take into account diacritics when it sorts facet names. He talks about Elasticsearch there although it appears Zebra also has the same issue. The first proposed solution was to strip out the diacritics using Unicode::Normalize. This worked pretty well, but on Mattermost paxed pointed out that this doesn’t work well for Finnish where “⟨å⟩, ⟨ä⟩ and ⟨ö⟩ are regarded as distinct letters and collated after ⟨z⟩” (as per Wikipedia’s “Finnish orthography” entry. So I looked at some locale-based Perl core options like “use locale” and “Unicode::Collate::Locale”, and I really really like “Unicode::Collate::Locale”. It leverages the Linux locale files to perfectly sort the text. (The only gotcha is that it’s based off the system locale. There are ways we could use the UI-chosen language instead, but I figure that’s a future development.) Anyway, I just want to get more eyes on this code, because it’s super interesting. The patch is very small and easy to understand. I just want to get more opinions about what we should be doing with it. Cheers! 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