[Koha] DBMS auto increment fix not working

2022-08-25 Thread Michael Kuhn

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://wiki.koha-community.org/wiki/DBMS_auto_increment_fix 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 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] DBMS auto increment fix not working

2022-08-25 Thread Katrin Fischer

Hi Michael,

the fix did prevent the problem from occurring on older versions, but it
doesn't fix the data.

Could it be the bad data was there before, maybe from using an older
DBMS version?

The simplest fix is to delete the entries in the old_ and deleted_
tables with the doubled up IDs and then restart your DBMS.

Hope this helps,

Katrin

On 25.08.22 11:03, Michael Kuhn wrote:

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://wiki.koha-community.org/wiki/DBMS_auto_increment_fix 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 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] DBMS auto increment fix not working

2022-08-25 Thread Michael Kuhn

Hi Katrin

You wrote:

> the fix did prevent the problem from occurring on older versions, but
> it doesn't fix the data.
>
> Could it be the bad data was there before, maybe from using an older
> DBMS version?
>
> The simplest fix is to delete the entries in the old_ and deleted_
> tables with the doubled up IDs and then restart your DBMS.

Yes, I know the fix won't fix the data. So I usually do what you suggested.

But I had expected the fix to prevent the problem from occurring - only 
the "auto_increment fix" does NOT prevent the problem in MariaDB 
10.5.51. Instead from time to time new deletions (not all) produce the 
same error again.


That's why I wrote I'm not sure if the underlying problem is the same as 
the one that was fixed by the "auto_increment fix".


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



Am 25.08.22 um 11:03 schrieb Michael Kuhn:
> 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://wiki.koha-community.org/wiki/DBMS_auto_increment_fix 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 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] DBMS auto increment fix not working

2022-08-25 Thread Katrin Fischer

Hi Michael,

not sure then :(

Maybe someone else has an idea?

Katrin


On 25.08.22 18:39, Michael Kuhn wrote:

Hi Katrin

You wrote:

> the fix did prevent the problem from occurring on older versions, but
> it doesn't fix the data.
>
> Could it be the bad data was there before, maybe from using an older
> DBMS version?
>
> The simplest fix is to delete the entries in the old_ and deleted_
> tables with the doubled up IDs and then restart your DBMS.

Yes, I know the fix won't fix the data. So I usually do what you
suggested.

But I had expected the fix to prevent the problem from occurring -
only the "auto_increment fix" does NOT prevent the problem in MariaDB
10.5.51. Instead from time to time new deletions (not all) produce the
same error again.

That's why I wrote I'm not sure if the underlying problem is the same
as the one that was fixed by the "auto_increment fix".

Best wishes: Michael

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Koha as SRU Server authentication problem

2022-08-25 Thread DHIM IT
Dear Colleagues,

I use Koha as SRU Server (Version 22.05.03).

I can connect to the server without credentials (user and password is blank) 
and with credentials from koha-conf.xml

How can I disable connection without credentials?

Example from koha-conf.xml:




/etc/koha/zebradb/ccl.properties

kohauser

password






Best regards
Eugen Bastron

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Edited authorities not updating in recently edited biblio records

2022-08-25 Thread Elaine Bradtke
I'm in the process of adding some 610 fields to catalogue records. These
are linked to existing authority records.  If I then edit the existing
authority record (usually to add (Musical group) to the 110) it doesn't
update 610 in the biblio record in which I just added the 610.  However, it
updates other records linked to that authority.
I think this is a timing issue; it will eventually update - possibly
related to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25324

Elaine Bradtke
VWML 
English Folk Dance and Song Society 
Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
Song Society in London, England. If you wish to phone me personally, send
an e-mail first. I work off site)
--
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Record display turns completely blank

2022-08-25 Thread 吳宣億
Hi,


Occasionally when we view/create/edit a record, the record page will not 
display properly, all the field will turn blank, any update to the record just 
pauses and we need to wait from minutes to hours before it fixes itself and the 
record to be displayed normally again. It happens from time to time and really 
impacts our workflow.

This is the screenshot of what it looks when it happens:

https://www.lib.ntu.edu.tw/AR/images/example.jpg


Anyone else experienced this? What could be the cause and what are potential 
solutions?




Mickey Wu
National Taiwan University Library IT Services Department
No.1 Sec.4, Roosevelt Rd., Taipei, Taiwan
Tel. 02-33664573
hsuan...@ntu.edu.tw
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Edited authorities not updating in recently edited biblio records

2022-08-25 Thread Marcel de Rooy
Hi Elaine,
Please check bug 30883.
This fix is in: 22.11.00, 22.05.01, 21.11.10, 21.05.17
Questions here are: Are you using ElasticSearch? And does the number of touched 
biblio records exceed the merge limit ?

Regards,
Marcel


Van: Koha  namens Elaine Bradtke 

Verzonden: donderdag 25 augustus 2022 19:56
Aan: koha 
Onderwerp: [Koha] Edited authorities not updating in recently edited biblio 
records

I'm in the process of adding some 610 fields to catalogue records. These
are linked to existing authority records.  If I then edit the existing
authority record (usually to add (Musical group) to the 110) it doesn't
update 610 in the biblio record in which I just added the 610.  However, it
updates other records linked to that authority.
I think this is a timing issue; it will eventually update - possibly
related to 
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2Fbugzilla3%2Fshow_bug.cgi%3Fid%3D25324&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C45649f4e6aba4229fa8a08da86c35519%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970470763177952%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BLbZvRu6iJhzhwIrhXuJPxHGujSEYrOYr5JzvG4Pqz8%3D&reserved=0

Elaine Bradtke
VWML 

English Folk Dance and Song Society 

Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
Song Society in London, England. If you wish to phone me personally, send
an e-mail first. I work off site)
--
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
___

Koha mailing list  
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C45649f4e6aba4229fa8a08da86c35519%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970470763177952%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BP2Fyb8jAAtCNsYzMJTGi%2Fcf8nZuCA2P5RrgC4t3Upc%3D&reserved=0
Koha@lists.katipo.co.nz
Unsubscribe: 
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C45649f4e6aba4229fa8a08da86c35519%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970470763177952%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nvSiB2PnG%2Fm2U0LViJvOn%2BmPf03qiOJ5Vd1Jd%2BPs6rY%3D&reserved=0
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha