[Koha] Reoccurring DBMS auto increment issue

[Katrin Fischer]

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 <mik at adminkuhn.ch> 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 mik at 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 mik at adminkuhn.ch · W www.adminkuhn.ch
>>>> _______________________________________________
>>>>
>>>> Koha mailing list  http://koha-community.org
>>>> Koha at lists.katipo.co.nz
>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>> _______________________________________________
>>
>> Koha mailing list  http://koha-community.org
>> Koha at lists.katipo.co.nz
>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> _______________________________________________
>
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha