Re: [Koha] Reoccurring DBMS auto increment issue
Just for the record: The solution was really easy - no update was necessary. Instead just add a missing semicolon after the curly bracket in line 138 of file "deletemem.pl" (see https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114182=diff ) # cd /usr/share/koha/intranet/cgi-bin/members # vi deletemem.pl Line 138 will then look like: }; That's all. 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 m...@adminkuhn.ch · W www.adminkuhn.ch ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Maybe helpful to know, if you add ALL at the beginning of your bugzilla search, the closed and resolved bugs will be included :) Katrin On 22.06.21 11:04, Jonathan Druart wrote: The bug is "resolved fixed", they are excluded from the default search. Le mar. 22 juin 2021 à 10:44, Michael Kuhn a écrit : Hi Joonas You wrote: > if you are really using 20.11.00 and not 20.11.01 or newer then I > think you might be bumping into bug 27144 [1]. Please upgrade your > koha version to fix the issue. > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144 Yes, this sounds exactly like what's going on, thank you very much! Bummer - yesterday I was searching Bugzilla for "delete" and "patron", but bug 27144 didn't raise its ugly head... I don't know what kind of search Bugzilla performs anyway, because it won't show me bug 27144 when I'm searching for * delete patron * delete patrons * delete any patrons Sigh. 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 m...@adminkuhn.ch · W www.adminkuhn.ch On 21/06/2021 22:01, Michael Kuhn wrote: Hi We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha 20.11.00 (using Shibboleth authentication). To avoid auto increment issues we have implemented the solution described in https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup - of course replacing "koha_kohadev" with the name of our own database, then restarted MariaDB. We did this even if the page says only versions prior to MariaDB 10.2.24 are affected. However, if we implement the fix or not, the following problem occurs: When we manually create a new Koha user (e. g. 84) and then try to delete it in the staff client, the message appears "An Error Occurred / 500 Internal Server Error". In Koha menu "About Koha > System information" it says "The following ids exist in both tables borrowers and deletedborrowers: 84". So we delete that number in MariaDB using SQL statement "DELETE FROM deletedborrowers where borrowernumber=84;". After that table "deletedborrowers" is empty and Koha menu "About Koha > System information" says "No warnings.". Again we try to delete the user, the internal server error occurs, etc ad infinitum. Are we doing something wrong? 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 m...@adminkuhn.ch · W www.adminkuhn.ch ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
The bug is "resolved fixed", they are excluded from the default search. Le mar. 22 juin 2021 à 10:44, Michael Kuhn a écrit : > > Hi Joonas > > You wrote: > > > if you are really using 20.11.00 and not 20.11.01 or newer then I > > think you might be bumping into bug 27144 [1]. Please upgrade your > > koha version to fix the issue. > > > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144 > > Yes, this sounds exactly like what's going on, thank you very much! > > Bummer - yesterday I was searching Bugzilla for "delete" and "patron", > but bug 27144 didn't raise its ugly head... I don't know what kind of > search Bugzilla performs anyway, because it won't show me bug 27144 when > I'm searching for > > * delete patron > * delete patrons > * delete any patrons > > Sigh. > > 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 m...@adminkuhn.ch · W www.adminkuhn.ch > > > > > On 21/06/2021 22:01, Michael Kuhn wrote: > >> Hi > >> > >> We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha > >> 20.11.00 (using Shibboleth authentication). > >> > >> To avoid auto increment issues we have implemented the solution > >> described in > >> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup > >> - of course replacing "koha_kohadev" with the name of our own database, > >> then restarted MariaDB. > >> > >> We did this even if the page says only versions prior to MariaDB 10.2.24 > >> are affected. However, if we implement the fix or not, the following > >> problem occurs: > >> > >> When we manually create a new Koha user (e. g. 84) and then try to > >> delete it in the staff client, the message appears "An Error Occurred / > >> 500 Internal Server Error". In Koha menu "About Koha > System > >> information" it says "The following ids exist in both tables borrowers > >> and deletedborrowers: 84". > >> > >> So we delete that number in MariaDB using SQL statement "DELETE FROM > >> deletedborrowers where borrowernumber=84;". After that table > >> "deletedborrowers" is empty and Koha menu "About Koha > System > >> information" says "No warnings.". Again we try to delete the user, the > >> internal server error occurs, etc ad infinitum. > >> > >> Are we doing something wrong? > >> > >> 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 m...@adminkuhn.ch · W www.adminkuhn.ch > >> ___ > >> > >> Koha mailing list http://koha-community.org > >> Koha@lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > ___ > > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Hi Joonas You wrote: > if you are really using 20.11.00 and not 20.11.01 or newer then I > think you might be bumping into bug 27144 [1]. Please upgrade your > koha version to fix the issue. > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144 Yes, this sounds exactly like what's going on, thank you very much! Bummer - yesterday I was searching Bugzilla for "delete" and "patron", but bug 27144 didn't raise its ugly head... I don't know what kind of search Bugzilla performs anyway, because it won't show me bug 27144 when I'm searching for * delete patron * delete patrons * delete any patrons Sigh. 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 m...@adminkuhn.ch · W www.adminkuhn.ch On 21/06/2021 22:01, Michael Kuhn wrote: Hi We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha 20.11.00 (using Shibboleth authentication). To avoid auto increment issues we have implemented the solution described in https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup - of course replacing "koha_kohadev" with the name of our own database, then restarted MariaDB. We did this even if the page says only versions prior to MariaDB 10.2.24 are affected. However, if we implement the fix or not, the following problem occurs: When we manually create a new Koha user (e. g. 84) and then try to delete it in the staff client, the message appears "An Error Occurred / 500 Internal Server Error". In Koha menu "About Koha > System information" it says "The following ids exist in both tables borrowers and deletedborrowers: 84". So we delete that number in MariaDB using SQL statement "DELETE FROM deletedborrowers where borrowernumber=84;". After that table "deletedborrowers" is empty and Koha menu "About Koha > System information" says "No warnings.". Again we try to delete the user, the internal server error occurs, etc ad infinitum. Are we doing something wrong? 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 m...@adminkuhn.ch · W www.adminkuhn.ch ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Hi Jonathan > Nothing in plack-error.log? > If you have a 500 you should see something useful there. No, sorry - absolutely nothing in "plack-error.log". 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 m...@adminkuhn.ch · W www.adminkuhn.ch Le mar. 22 juin 2021 à 09:48, Michael Kuhn a écrit : Hi Jonathan You wrote: > Hi Michael, what do you have in the Koha log files? When trying to delete a user, logfile "/var/log/koha/embl/plack.log" says: 192.168.210.80 - - [21/Jun/2021:17:16:58 +0200] "GET /intranet/members/deletemem.pl?member=83 HTTP/1.1" 200 32438 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" 192.168.210.80 - - [21/Jun/2021:17:17:44 +0200] "GET /intranet/members/deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed HTTP/1.1" 500 136 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" At the same time "/var/log/apache2/other_vhosts_access.log" says: libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:16:58 +0200] "GET /cgi-bin/koha/members/deletemem.pl?member=83 HTTP/1.1" 200 7192 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:17:44 +0200] "GET /cgi-bin/koha/members/deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed HTTP/1.1" 500 532 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" 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 m...@adminkuhn.ch · W www.adminkuhn.ch Le lun. 21 juin 2021 à 21:01, Michael Kuhn a écrit : Hi We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha 20.11.00 (using Shibboleth authentication). To avoid auto increment issues we have implemented the solution described in https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup - of course replacing "koha_kohadev" with the name of our own database, then restarted MariaDB. We did this even if the page says only versions prior to MariaDB 10.2.24 are affected. However, if we implement the fix or not, the following problem occurs: When we manually create a new Koha user (e. g. 84) and then try to delete it in the staff client, the message appears "An Error Occurred / 500 Internal Server Error". In Koha menu "About Koha > System information" it says "The following ids exist in both tables borrowers and deletedborrowers: 84". So we delete that number in MariaDB using SQL statement "DELETE FROM deletedborrowers where borrowernumber=84;". After that table "deletedborrowers" is empty and Koha menu "About Koha > System information" says "No warnings.". Again we try to delete the user, the internal server error occurs, etc ad infinitum. Are we doing something wrong? 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 m...@adminkuhn.ch · W www.adminkuhn.ch ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Nothing in plack-error.log? If you have a 500 you should see something useful there. Le mar. 22 juin 2021 à 09:48, Michael Kuhn a écrit : > > Hi Jonathan > > You wrote: > > > Hi Michael, what do you have in the Koha log files? > > When trying to delete a user, logfile "/var/log/koha/embl/plack.log" says: > > 192.168.210.80 - - [21/Jun/2021:17:16:58 +0200] "GET > /intranet/members/deletemem.pl?member=83 HTTP/1.1" 200 32438 > "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > 192.168.210.80 - - [21/Jun/2021:17:17:44 +0200] "GET > /intranet/members/deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed > HTTP/1.1" 500 136 > "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > > At the same time "/var/log/apache2/other_vhosts_access.log" says: > > libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:16:58 > +0200] "GET /cgi-bin/koha/members/deletemem.pl?member=83 HTTP/1.1" 200 > 7192 > "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:17:44 > +0200] "GET > /cgi-bin/koha/members/deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed > HTTP/1.1" 500 532 > "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > > > 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 m...@adminkuhn.ch · W www.adminkuhn.ch > > > > > Le lun. 21 juin 2021 à 21:01, Michael Kuhn a écrit : > >> > >> Hi > >> > >> We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha > >> 20.11.00 (using Shibboleth authentication). > >> > >> To avoid auto increment issues we have implemented the solution > >> described in > >> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup > >> - of course replacing "koha_kohadev" with the name of our own database, > >> then restarted MariaDB. > >> > >> We did this even if the page says only versions prior to MariaDB 10.2.24 > >> are affected. However, if we implement the fix or not, the following > >> problem occurs: > >> > >> When we manually create a new Koha user (e. g. 84) and then try to > >> delete it in the staff client, the message appears "An Error Occurred / > >> 500 Internal Server Error". In Koha menu "About Koha > System > >> information" it says "The following ids exist in both tables borrowers > >> and deletedborrowers: 84". > >> > >> So we delete that number in MariaDB using SQL statement "DELETE FROM > >> deletedborrowers where borrowernumber=84;". After that table > >> "deletedborrowers" is empty and Koha menu "About Koha > System > >> information" says "No warnings.". Again we try to delete the user, the > >> internal server error occurs, etc ad infinitum. > >> > >> Are we doing something wrong? > >> > >> 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 m...@adminkuhn.ch · W www.adminkuhn.ch > >> ___ > >> > >> Koha mailing list http://koha-community.org > >> Koha@lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Hi Michael, if you are really using 20.11.00 and not 20.11.01 or newer then I think you might be bumping into bug 27144 [1]. Please upgrade your koha version to fix the issue. Joonas [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27144 On 21/06/2021 22:01, Michael Kuhn wrote: > Hi > > We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha > 20.11.00 (using Shibboleth authentication). > > To avoid auto increment issues we have implemented the solution > described in > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup > - of course replacing "koha_kohadev" with the name of our own database, > then restarted MariaDB. > > We did this even if the page says only versions prior to MariaDB 10.2.24 > are affected. However, if we implement the fix or not, the following > problem occurs: > > When we manually create a new Koha user (e. g. 84) and then try to > delete it in the staff client, the message appears "An Error Occurred / > 500 Internal Server Error". In Koha menu "About Koha > System > information" it says "The following ids exist in both tables borrowers > and deletedborrowers: 84". > > So we delete that number in MariaDB using SQL statement "DELETE FROM > deletedborrowers where borrowernumber=84;". After that table > "deletedborrowers" is empty and Koha menu "About Koha > System > information" says "No warnings.". Again we try to delete the user, the > internal server error occurs, etc ad infinitum. > > Are we doing something wrong? > > 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 m...@adminkuhn.ch · W www.adminkuhn.ch > ___ > > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Hi there. Given that web application logs are so laconic maybe you can temporary enable SQL query logging in your database to see which query is producing the error. Cheers. Javier On Tue, 22 Jun 2021 at 09:48, Michael Kuhn wrote: > Hi Jonathan > > You wrote: > > > Hi Michael, what do you have in the Koha log files? > > When trying to delete a user, logfile "/var/log/koha/embl/plack.log" says: > > 192.168.210.80 - - [21/Jun/2021:17:16:58 +0200] "GET > /intranet/members/deletemem.pl?member=83 HTTP/1.1" 200 32438 > " > https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; > > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > 192.168.210.80 - - [21/Jun/2021:17:17:44 +0200] "GET > /intranet/members/ > deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed > HTTP/1.1" 500 136 > " > https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; > > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > > At the same time "/var/log/apache2/other_vhosts_access.log" says: > > libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:16:58 > +0200] "GET /cgi-bin/koha/members/deletemem.pl?member=83 HTTP/1.1" 200 > 7192 > " > https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; > > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:17:44 > +0200] "GET > /cgi-bin/koha/members/ > deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed > HTTP/1.1" 500 532 > " > https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; > > "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" > > > 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 m...@adminkuhn.ch · W www.adminkuhn.ch > > > > > Le lun. 21 juin 2021 à 21:01, Michael Kuhn a écrit : > >> > >> Hi > >> > >> We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha > >> 20.11.00 (using Shibboleth authentication). > >> > >> To avoid auto increment issues we have implemented the solution > >> described in > >> > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup > >> - of course replacing "koha_kohadev" with the name of our own database, > >> then restarted MariaDB. > >> > >> We did this even if the page says only versions prior to MariaDB 10.2.24 > >> are affected. However, if we implement the fix or not, the following > >> problem occurs: > >> > >> When we manually create a new Koha user (e. g. 84) and then try to > >> delete it in the staff client, the message appears "An Error Occurred / > >> 500 Internal Server Error". In Koha menu "About Koha > System > >> information" it says "The following ids exist in both tables borrowers > >> and deletedborrowers: 84". > >> > >> So we delete that number in MariaDB using SQL statement "DELETE FROM > >> deletedborrowers where borrowernumber=84;". After that table > >> "deletedborrowers" is empty and Koha menu "About Koha > System > >> information" says "No warnings.". Again we try to delete the user, the > >> internal server error occurs, etc ad infinitum. > >> > >> Are we doing something wrong? > >> > >> 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 m...@adminkuhn.ch · W www.adminkuhn.ch > >> ___ > >> > >> Koha mailing list http://koha-community.org > >> Koha@lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > ___ > > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Hi Jonathan You wrote: > Hi Michael, what do you have in the Koha log files? When trying to delete a user, logfile "/var/log/koha/embl/plack.log" says: 192.168.210.80 - - [21/Jun/2021:17:16:58 +0200] "GET /intranet/members/deletemem.pl?member=83 HTTP/1.1" 200 32438 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" 192.168.210.80 - - [21/Jun/2021:17:17:44 +0200] "GET /intranet/members/deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed HTTP/1.1" 500 136 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" At the same time "/var/log/apache2/other_vhosts_access.log" says: libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:16:58 +0200] "GET /cgi-bin/koha/members/deletemem.pl?member=83 HTTP/1.1" 200 7192 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/moremember.pl?borrowernumber=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" libcatalog-test.embl.de:443 192.168.210.80 - - [21/Jun/2021:17:17:44 +0200] "GET /cgi-bin/koha/members/deletemem.pl?csrf_token=9aea7e6464047b5c52c5ee3c6af5955bbf1b78a6%2Cbfb8e2961b2275e44a1fa49235060091ccece7fe%2C1624288618=83=delete_confirmed HTTP/1.1" 500 532 "https://libcatalog-testusers.embl.de/cgi-bin/koha/members/deletemem.pl?member=84; "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" 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 m...@adminkuhn.ch · W www.adminkuhn.ch Le lun. 21 juin 2021 à 21:01, Michael Kuhn a écrit : Hi We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha 20.11.00 (using Shibboleth authentication). To avoid auto increment issues we have implemented the solution described in https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup - of course replacing "koha_kohadev" with the name of our own database, then restarted MariaDB. We did this even if the page says only versions prior to MariaDB 10.2.24 are affected. However, if we implement the fix or not, the following problem occurs: When we manually create a new Koha user (e. g. 84) and then try to delete it in the staff client, the message appears "An Error Occurred / 500 Internal Server Error". In Koha menu "About Koha > System information" it says "The following ids exist in both tables borrowers and deletedborrowers: 84". So we delete that number in MariaDB using SQL statement "DELETE FROM deletedborrowers where borrowernumber=84;". After that table "deletedborrowers" is empty and Koha menu "About Koha > System information" says "No warnings.". Again we try to delete the user, the internal server error occurs, etc ad infinitum. Are we doing something wrong? 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 m...@adminkuhn.ch · W www.adminkuhn.ch ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Reoccurring DBMS auto increment issue
Hi Michael, what do you have in the Koha log files? Le lun. 21 juin 2021 à 21:01, Michael Kuhn a écrit : > > Hi > > We are working with Debian GNU/Linux 10, MariaDB 10.3.27 and Koha > 20.11.00 (using Shibboleth authentication). > > To avoid auto increment issues we have implemented the solution > described in > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#Single_instance_setup > - of course replacing "koha_kohadev" with the name of our own database, > then restarted MariaDB. > > We did this even if the page says only versions prior to MariaDB 10.2.24 > are affected. However, if we implement the fix or not, the following > problem occurs: > > When we manually create a new Koha user (e. g. 84) and then try to > delete it in the staff client, the message appears "An Error Occurred / > 500 Internal Server Error". In Koha menu "About Koha > System > information" it says "The following ids exist in both tables borrowers > and deletedborrowers: 84". > > So we delete that number in MariaDB using SQL statement "DELETE FROM > deletedborrowers where borrowernumber=84;". After that table > "deletedborrowers" is empty and Koha menu "About Koha > System > information" says "No warnings.". Again we try to delete the user, the > internal server error occurs, etc ad infinitum. > > Are we doing something wrong? > > 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 m...@adminkuhn.ch · W www.adminkuhn.ch > ___ > > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
