Re: [Koha] Error 500 when searching in Koha 23.11.0
Hi Just for the record: I updated from Koha 21.11.10 to 23.11.04. When searching the catalogue I got a result list, but when clicking a single hit I got an error 500. In file "plack-error.log" I found this: DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'issue.renewals_count' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 317 In Koha 21.11 this column was called "issues.renewals" and in Koha 23.11 it should be called "issues.renewals_count" - but for whatever reason the upgrade did not rename it properly. I have done that myself: ALTER TABLE issues RENAME COLUMN renewals TO renewals_count; Now single hits show up. PS1: The error message says the column is "issue.renewals_count" but actually it is "issues.renewals_count". PS2: https://schema.koha-community.org/23_11/tables/issues.html says the type of this column is tinyint(3) while it actually is tinyint(4). 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] Error 500 when searching in Koha 23.11.0
Hi I have updated our database from koha 21.11.10 to the current Koha 23.11.04. When searching the catalogue I get a result list, but when clicking a single hit I get an error 500. In file "plack-error.log" I have found the following line which could be the reason: DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'issue.renewals_count' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 317 In fact there is no table "issue" in Koha 23.11, the correct name of this table is "issues" (see https://schema.koha-community.org/23_11/tables/issues.html). I have searched in Bugzilla but couldn't find a respective bug. But I found the sequence "issue.renewals_count" in https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=137152 so there may be some relation to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275 Does anyone know how I can solve this problem with the 500 error? Best wishes: Michael Kuhn -- 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] Update to Koha 23.11.04 fails
Hi Aleisha
You wrote:
> The sneaky thing about the installer is that when it fails on a
> database update, it's often referring to the NEXT one, not the printed
> one you can see.
>
> So I think that error is actually about Bug 34869:
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34869 you'll
> see that database update is trying to select a column id from the
> additional_contents table.
>
> Did a previous update adding the additional_contents table fail?
>
> Hope that gives you somewhere to start.
Thanks for the hint! As I saw in table "additional_contents" there was a
column "idnew" in Koha 21.11 and Koha 23.05 - but this was renamed to
"id" in Koha 23.11. So, no earlier update failed, seemingly just the
update from Koha 23.05 to 23.11.
However, in my Koha 21.11 dump I just changed to name of the column
"idnew" to "id" (also for the primary key), then loaded the dump into
MariaDB und retried the upgrade to Koha 23.11 again. This time it worked
and showed the following output:
Upgrade to 23.06.00.068 [09:42:00]: Bug 23798 - Convert
OpacMaintenanceNotice system preference to additional contents
Added 'OpacMaintenanceNotice' HTML customization
Removed system preference 'OpacMaintenanceNotice'
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 12/04/24 09:12, Michael Kuhn wrote:
Hi
Today I tried to update a Koha 21.11.10 database to Koha 23.11.04 but
the update process failed at the following point:
Upgrade to 23.06.00.068 [22:55:59]: Bug 23798 - Convert
OpacMaintenanceNotice system preference to additional contents
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db selectrow_array
failed: Unknown column 'id' in 'field list' at
/usr/share/koha/lib/C4/Installer.pm line 741
I couldn't find anything regarding this error in Bugzilla, but maybe
it is related to
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23798#c12
which shows a similar error regarding an "Unknown column 'title'".
How should I proceed?
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] Update to Koha 23.11.04 fails
Hi
Today I tried to update a Koha 21.11.10 database to Koha 23.11.04 but
the update process failed at the following point:
Upgrade to 23.06.00.068 [22:55:59]: Bug 23798 - Convert
OpacMaintenanceNotice system preference to additional contents
ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db selectrow_array failed:
Unknown column 'id' in 'field list' at
/usr/share/koha/lib/C4/Installer.pm line 741
I couldn't find anything regarding this error in Bugzilla, but maybe it
is related to
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23798#c12
which shows a similar error regarding an "Unknown column 'title'".
How should I proceed?
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] Not possible to create Koha instance with Let's Encrypt
Hi I'm sorry for bothering you - the problem is solved (an unwanted character in file "koha-sites.conf"). 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 11.04.24 um 18:34 schrieb Michael Kuhn: Hi I was just installing the most recent Koha 23.11.04-4. But when trying to create my Koha instance with Let's Encrypt I executed the following command: sudo koha-create --create-db mdc --letsencrypt But instead of obtaining a certificate the output ends with the following: (for full output see below): sed: -e Ausdruck #5, Zeichen 53: Unbekannte Option für »s« (in English maybe: sed: -e Expression #5, character 53: Unknown option for »s«) How can I circumvent this problem? Is this maybe the error that Tomas Cohen Arazi mentioned in his mail to the mailinglist on 16:06? 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] Not possible to create Koha instance with Let's Encrypt
Hi I was just installing the most recent Koha 23.11.04-4. But when trying to create my Koha instance with Let's Encrypt I executed the following command: sudo koha-create --create-db mdc --letsencrypt But instead of obtaining a certificate the output ends with the following: (for full output see below): sed: -e Ausdruck #5, Zeichen 53: Unbekannte Option für »s« (in English maybe: sed: -e Expression #5, character 53: Unknown option for »s«) How can I circumvent this problem? Is this maybe the error that Tomas Cohen Arazi mentioned in his mail to the mailinglist on 16:06? 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@mdckoha1:~$ sudo koha-create --create-db mdc --letsencrypt The letsencrypt package is not installed. Do it now? [y/N] y Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Hinweis: »certbot« wird an Stelle von »letsencrypt« gewählt. Die folgenden zusätzlichen Pakete werden installiert: python3-acme python3-certbot python3-configargparse python3-distro python3-icu python3-josepy python3-openssl python3-parsedatetime python3-rfc3339 Vorgeschlagene Pakete: python-certbot-doc python3-certbot-apache python3-certbot-nginx python-acme-doc python-openssl-doc python3-openssl-dbg Die folgenden NEUEN Pakete werden installiert: certbot python3-acme python3-certbot python3-configargparse python3-distro python3-icu python3-josepy python3-openssl python3-parsedatetime python3-rfc3339 0 aktualisiert, 10 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen 1.013 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 4.739 kB Plattenplatz zusätzlich benutzt. Holen:1 http://deb.debian.org/debian bookworm/main amd64 python3-openssl all 23.0.0-1 [50,8 kB] Holen:2 http://deb.debian.org/debian bookworm/main amd64 python3-josepy all 1.13.0-1 [23,1 kB] Holen:3 http://deb.debian.org/debian bookworm/main amd64 python3-rfc3339 all 1.1-4 [7.088 B] Holen:4 http://deb.debian.org/debian bookworm/main amd64 python3-acme all 2.1.0-1 [32,0 kB] Holen:5 http://deb.debian.org/debian bookworm/main amd64 python3-configargparse all 1.5.3-1 [26,1 kB] Holen:6 http://deb.debian.org/debian bookworm/main amd64 python3-distro all 1.8.0-1 [20,5 kB] Holen:7 http://deb.debian.org/debian bookworm/main amd64 python3-parsedatetime all 2.6-3 [41,2 kB] Holen:8 http://deb.debian.org/debian bookworm/main amd64 python3-certbot all 2.1.0-4 [209 kB] Holen:9 http://deb.debian.org/debian bookworm/main amd64 certbot all 2.1.0-4 [122 kB] Holen:10 http://deb.debian.org/debian bookworm/main amd64 python3-icu amd64 2.10.2-1+b3 [482 kB] Es wurden 1.013 kB in 0 s geholt (20,1 MB/s). Vorkonfiguration der Pakete ... Vormals nicht ausgewähltes Paket python3-openssl wird gewählt. (Lese Datenbank ... 101801 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../0-python3-openssl_23.0.0-1_all.deb ... Entpacken von python3-openssl (23.0.0-1) ... Vormals nicht ausgewähltes Paket python3-josepy wird gewählt. Vorbereitung zum Entpacken von .../1-python3-josepy_1.13.0-1_all.deb ... Entpacken von python3-josepy (1.13.0-1) ... Vormals nicht ausgewähltes Paket python3-rfc3339 wird gewählt. Vorbereitung zum Entpacken von .../2-python3-rfc3339_1.1-4_all.deb ... Entpacken von python3-rfc3339 (1.1-4) ... Vormals nicht ausgewähltes Paket python3-acme wird gewählt. Vorbereitung zum Entpacken von .../3-python3-acme_2.1.0-1_all.deb ... Entpacken von python3-acme (2.1.0-1) ... Vormals nicht ausgewähltes Paket python3-configargparse wird gewählt. Vorbereitung zum Entpacken von .../4-python3-configargparse_1.5.3-1_all.deb ... Entpacken von python3-configargparse (1.5.3-1) ... Vormals nicht ausgewähltes Paket python3-distro wird gewählt. Vorbereitung zum Entpacken von .../5-python3-distro_1.8.0-1_all.deb ... Entpacken von python3-distro (1.8.0-1) ... Vormals nicht ausgewähltes Paket python3-parsedatetime wird gewählt. Vorbereitung zum Entpacken von .../6-python3-parsedatetime_2.6-3_all.deb ... Entpacken von python3-parsedatetime (2.6-3) ... Vormals nicht ausgewähltes Paket python3-certbot wird gewählt. Vorbereitung zum Entpacken von .../7-python3-certbot_2.1.0-4_all.deb ... Entpacken von python3-certbot (2.1.0-4) ... Vormals nicht ausgewähltes Paket certbot wird gewählt. Vorbereitung zum Entpacken von .../8-certbot_2.1.0-4_all.deb ... Entpacken von certbot (2.1.0-4) ... Vormals nicht ausgewähltes Paket python3-icu wird gewählt. Vorbereitung zum Entpacken von .../9-python3-icu_2.10.2-1+b3_amd64.deb ... Entpacken von python3-icu (2.10.2-1+b3) ... python3-configargparse (1.5.3-1) wird eingerichtet ... python3-parsedatetime (2.6-3) wird eingerichtet ... python3-distro (1.8.0-1) wird eingerichtet ... python3-icu (2.10.2-1+b3)
[Koha] Content of tags and in OAI-PMH
Hi In our library we are using Koha 21.11.10 We are trying to use OAI-PMH but when calling https://bibliothek.iunworld.com/cgi-bin/koha/oai.pl?verb=Identify the output is as follows: xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns='http://www.openarchives.org/OAI/2.0/'> 2024-04-03T16:39:53Z verb='Identify'>https://bibliothek.iunworld.com/opac/oai.pl IUN World https://bibliothek.iunworld.com/opac/oai.pl 2.0 root@localhost 2020-01-21T13:25:14Z persistent -MM-DDThh:mm:ssZ gzip As you see in both the tags and there is an incorrect URL ( https://bibliothek.iunworld.com/opac/oai.pl ) which only leads to a 404 error page. The correct URL would be https://bibliothek.iunworld.com/cgi-bin/koha/oai.pl I have changed the following line in file "/usr/share/koha/lib/Koha/OAI/Server/Identify.pm" to get the correct URL at least in tag : #baseURL => $baseURL, baseURL => 'https://bibliothek.iunworld.com/cgi-bin/koha/oai.pl', But I couldn't find out how to get the correct URL also in tag . In fact I doubt what I'm doing is the correct way but I couldn't find any information in the manual on how to configure OAI-PMH except via the system preferences. Why is Koha showing the incorrect URL https://bibliothek.iunworld.com/opac/oai.pl at all and how can I change this? 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] Koha January release with security fixes
Hi Fridolin You wrote: > The full release notes are available here: > https://koha-community.org/koha-23-11-02-released/ This link works. > https://koha-community.org/koha-23-05-08-released/ > https://koha-community.org/koha-22-11-14-released/ > https://koha-community.org/koha-22-05-18-released/ These three links do not work. 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] Fwd: [Koha-devel] Call for news - Newsletter January 2024
Hi Chris Thanks for your answer! However, it seems this e-mail was actually never delivered to the recipients of mailing list "Koha". And for sure it never reached my mailbox, not even marked as junk mail. The same is true for the mailbox of e-mail address "kohan...@gmail.com" from which I was sending this e-mail. 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 16.01.24 um 12:50 schrieb Chris Cormack: Hi Michael It was accepted as far as I can tell, it's certainly in the archive. https://lists.katipo.co.nz/pipermail/koha/2024-January/060444.html <https://lists.katipo.co.nz/pipermail/koha/2024-January/060444.html> Chris On 16 January 2024 11:07:35 pm NZDT, Michael Kuhn wrote: Hi From "kohan...@gmail.com" I have sent the following e-mail as usual to the following two addresses: * koha@lists.katipo.co.nz * koha-de...@lists.koha-community.org But it only appeared via mailing list "koha-devel" - can the responsible person for mailing list "koha" please have a look into the problem and enable this e-mail to be accepted? Best wishes: Michael -- Kaihuawaere Matihiko (he/him) Kāi Tahu, Kāti Māmoe, Waitaha Catalyst.Net Limited - Expert Open Source Solutions 027 4500789 chr...@catalyst.net.nz ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Fwd: [Koha-devel] Call for news - Newsletter January 2024
Hi From "kohan...@gmail.com" I have sent the following e-mail as usual to the following two addresses: * koha@lists.katipo.co.nz * koha-de...@lists.koha-community.org But it only appeared via mailing list "koha-devel" - can the responsible person for mailing list "koha" please have a look into the problem and enable this e-mail to be accepted? 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 Weitergeleitete Nachricht Betreff:[Koha-devel] Call for news - Newsletter January 2024 Datum: Sat, 13 Jan 2024 01:17:15 +0100 Von:Koha Newsletter via Koha-devel Antwort an: Koha Newsletter An: koha , koha-devel Hi I'm collecting news for the January 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 athttps://koha-community.org/calendar/ <https://koha-community.org/calendar/> Thank you! Michael Kuhn Editor, Koha Community Newsletter ___ Koha-devel mailing list koha-de...@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/ ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Argument "0, 00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292.
Hi Katrin and Magnus After the mentioned changes everything works as expected. Thanks again for your help! (And as suggested by Katrin I have set system preference "CurrencyFormat" to a format with decimal dot). 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 08.01.24 um 10:53 schrieb Michael Kuhn: Hi Katrin and Magnus Many thanks for your answers! It is not possible to change the value to "0.00" via Koha menu "Administration > Defining circulation and fine rules for all libraries" - even wehn savin "0.00" it will still show "0,00". We have eight rules there - all of them show value "0,00" in column "Overdue fines cap (amount)". But in table "circulation_rules" I found the following: MariaDB [koha_bibliothek]> SELECT * FROM circulation_rules WHERE rule_name="overduefinescap"; +-++--+--+-++ | id | branchcode | categorycode | itemtype | rule_name | rule_value +-++--+--+-++ | 4 | NULL | NULL | NULL | overduefinescap | | | 34 | NULL | NULL | BUCH | overduefinescap | 0.00 | | 67 | NULL | NULL | CD | overduefinescap | 0.00 | | 94 | NULL | NULL | ZSS | overduefinescap | 0.00 | | 136 | NULL | PT | BUCH | overduefinescap | | | 170 | NULL | HB | BUCH | overduefinescap | 0.00 | | 182 | NULL | NULL | KONV | overduefinescap | | | 214 | NULL | NULL | DVD | overduefinescap | | +-++--+--+-++ 8 rows in set (0,000 sec) So I changed just the values actually containing "0,00" as follows: MariaDB [koha_bibliothek]> UPDATE circulation_rules SET rule_value = '0.00' WHERE rule_value = '0,00'; Thus table "circulation_rules" now shows: MariaDB [koha_bibliothek]> SELECT * FROM circulation_rules WHERE rule_name="overduefinescap"; +-++--+--+-++ | id | branchcode | categorycode | itemtype | rule_name | rule_value | +-++--+--+-++ | 4 | NULL | NULL | NULL | overduefinescap | | | 34 | NULL | NULL | BUCH | overduefinescap | 0.00 | | 67 | NULL | NULL | CD | overduefinescap | 0.00 | | 94 | NULL | NULL | ZSS | overduefinescap | 0.00 | | 136 | NULL | PT | BUCH | overduefinescap | | | 170 | NULL | HB | BUCH | overduefinescap | 0.00 | | 182 | NULL | NULL | KONV | overduefinescap | | | 214 | NULL | NULL | DVD | overduefinescap | | +-++--+--+-++ 8 rows in set (0,000 sec) However, even after restarting Koha ( memcached apache2 koha-common ) Koha menu "Administration > Defining circulation and fine rules for all libraries" still shows the value "0,00" in column "Overdue fines cap (amount)" for all eight rules as before. I will now wait and see what happens after the next run of "/etc/cron.daily/koha-common". Best wishes: Michael ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Argument "0, 00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292.
Hi Katrin and Magnus Many thanks for your answers! It is not possible to change the value to "0.00" via Koha menu "Administration > Defining circulation and fine rules for all libraries" - even wehn savin "0.00" it will still show "0,00". We have eight rules there - all of them show value "0,00" in column "Overdue fines cap (amount)". But in table "circulation_rules" I found the following: MariaDB [koha_bibliothek]> SELECT * FROM circulation_rules WHERE rule_name="overduefinescap"; +-++--+--+-++ | id | branchcode | categorycode | itemtype | rule_name| rule_value +-++--+--+-++ | 4 | NULL | NULL | NULL | overduefinescap | | | 34 | NULL | NULL | BUCH | overduefinescap | 0.00 | | 67 | NULL | NULL | CD | overduefinescap | 0.00 | | 94 | NULL | NULL | ZSS | overduefinescap | 0.00 | | 136 | NULL | PT | BUCH | overduefinescap | | | 170 | NULL | HB | BUCH | overduefinescap | 0.00 | | 182 | NULL | NULL | KONV | overduefinescap | | | 214 | NULL | NULL | DVD | overduefinescap | | +-++--+--+-++ 8 rows in set (0,000 sec) So I changed just the values actually containing "0,00" as follows: MariaDB [koha_bibliothek]> UPDATE circulation_rules SET rule_value = '0.00' WHERE rule_value = '0,00'; Thus table "circulation_rules" now shows: MariaDB [koha_bibliothek]> SELECT * FROM circulation_rules WHERE rule_name="overduefinescap"; +-++--+--+-++ | id | branchcode | categorycode | itemtype | rule_name| rule_value | +-++--+--+-++ | 4 | NULL | NULL | NULL | overduefinescap | | | 34 | NULL | NULL | BUCH | overduefinescap | 0.00 | | 67 | NULL | NULL | CD | overduefinescap | 0.00 | | 94 | NULL | NULL | ZSS | overduefinescap | 0.00 | | 136 | NULL | PT | BUCH | overduefinescap | | | 170 | NULL | HB | BUCH | overduefinescap | 0.00 | | 182 | NULL | NULL | KONV | overduefinescap | | | 214 | NULL | NULL | DVD | overduefinescap | | +-++--+--+-++ 8 rows in set (0,000 sec) However, even after restarting Koha ( memcached apache2 koha-common ) Koha menu "Administration > Defining circulation and fine rules for all libraries" still shows the value "0,00" in column "Overdue fines cap (amount)" for all eight rules as before. I will now wait and see what happens after the next run of "/etc/cron.daily/koha-common". 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 08.01.24 um 08:14 schrieb Magnus Enger: > Hi! > > I have run into a similar problem when upgrading to 23.05, and solved > it by running queries like this directly in the database: > > mysql> update circulation_rules set rule_value = '0.00' where > rule_value = '0,00'; > > If you have this problem with other numbers, repeat the query but > replace 0,00/0.00 with the other relevant numbers. > > Best regards, > Magnus > Libriotech Am 06.01.24 um 11:44 schrieb Katrin Fischer: > Hi Michael, > > this was fixed with: > > *Bug 33028* > <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33028> - > Wrongly formatted monetary amounts in circulation rules break scripts > and calculation > > But the fix still requires you to fix the values stored in the database. > > You could try to edit the rule and save 0.00 (with the .). It might > work.Or you could use SQL to make sure all the monetary values in > circulation_rules are correctly formatted. > > Hope this helps, > > Katrin On 06.01.24 11:33, Michael Kuhn wrote: Hi Our library is working with Koha 22.05.17. Since some days the anacron job "cron.daily" sends us an e-mail with hundreds of lines like the following every day: Argument "0,00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292. I see in the circulation and fine rules the "Overdue fines cap (amount)" shows as "0,00" instead of "0.00" as usual. However, this can't be
[Koha] Argument "0, 00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292.
Hi Our library is working with Koha 22.05.17. Since some days the anacron job "cron.daily" sends us an e-mail with hundreds of lines like the following every day: Argument "0,00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292. I see in the circulation and fine rules the "Overdue fines cap (amount)" shows as "0,00" instead of "0.00" as usual. However, this can't be changed at this place. Changing lines in script "Overdues.pm" according to https://gomezcardozo.com/error-en-fines-koha/ didn't help. How can this output be prevented? 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] Automatic display of punctuation in Title view of record
Hi Jithin N You wrote: > I want display the punctuation ':' before the remaining of title > (245$b) and '/' before the statement of responsibility (245$c) in > display of records in detail view and search result view automatically > without adding it in marc fields. I did some changes in XSLT file but > it is not showing as mentioned. Can you any one give any suggestions > or correct code changes/adding needed to do in XSLT file? Add the following in your files for detail and result view in staff client and OPAC (...Detail.xsl resp. ...Results.xsl): ... : / ... Hope this helps. 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] Koha 23.05.05 advanced editor interface hanging on editing existing catalogue record
Hi Iming Chan You wrote > I am running Koha 23.05.05 and using Google Chrome as the browser. > > Does anyone else have trouble editing an existing catalogue record > using the advanced editor? > > After we switched to the Advanced Editor from the basic editor, the > screen just showed "Loading, please wait ...". Pressed F12 and I > noticed there are two page errors of "Incorrect use of > . In May 2022 I reported a similar problem which is (to my knowledge) still unsolved (the library meanwhile uses Koha 21.11.09): https://lists.katipo.co.nz/public/koha/2022-May/057752.html There were no answers to this post. 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] RabbitMQ
Hi Andrew You wrote: > I'm sorry, the 23.10 is referring to the ubuntu release, not koha. > I'm sorry, the 23.10 is the > Hi Andrew, > can you give us your exact version? There is no released 23.10 and the > developer version should be 23.06. As Fridolin said, I believe > RabbitMQ is not mandatory right now and there is a SQL fallback. > Hope that helps, > Katrin According to https://wiki.koha-community.org/wiki/System_requirements_and_recommendations Ubuntu 23.10 is currently not officially supported by any Koha version. However, Katrin asked for the exact version of Koha you're using. 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] how to make my library as z39 source
Hi Zen You wrote: > I want to make my library as z39 sources, is it possible? Yes it is. Have a look at: * https://wiki.koha-community.org/wiki/Setting_up_the_Z39.50_and_SRU_Server * https://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server * https://www.youtube.com/watch?v=j_XOKvq8_TI Hope this helps. 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] support newer Linux version
Hi ReindeR You wrote: > New to the list and not yet a user of Koha. The IT-person who will > install it says that it runs on old Linux-versions he does not have > anymore. > > Indeed, when I check the specs and compare that with Wikipedia I see > that both the mentioned Debian and Ubuntu-versions are not new. According to https://wiki.koha-community.org/wiki/System_requirements_and_recommendations#Koha_23.05 the most current version Koha 23.05 supports operating systems Debian GNU/Linux 12 and Ubuntu 22.04, among others. Debian GNU/Linux 12 ist the most current Debian version (presumably supported until June 2028). Ubuntu 22.04 ist the most current Ubuntu LTS version (supported untiel April 2027). Use one of these instead of any older operating system version. Hope this helps. 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] Connection timed out whenever I try a Z39.50 search
Hi Δημήτρης You wrote: > Which ports should I check? No Z39.50 service is working, not even the > Library of Congress. In Koha menu "Administration > Z39.50/SRU servers administration you'll find the hostname/port for the Library of Congress are lx2.loc.gov:210 - thus you could test if this host is accessible from your own host: $ telnet lx2.loc.gov 210 Trying 140.147.239.58... Connected to lx2.loc.gov. Escape character is '^]'. $ nc -vz lx2.loc.gov 210 Connection to lx2.loc.gov (140.147.239.58) 210 port [tcp/z3950] succeeded! If your output looks else you'll probably have to talk to your network/firewall administrator. Hope this helps. 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 Στις Παρ 13 Οκτ 2023 στις 10:24 π.μ., ο/η David Nind έγραψε: One thing to look for is to see if the ports used for the Z39.50 services you are trying to access are blocked by your organisation's firewall. Or maybe the Z39.50 sources are no longer available... I'm sure there is a way to check if they are, but not sure how to myself. David Nind New Zealand On Fri, 13 Oct 2023 at 20:17, Δημήτρης Δαλαγιώργος < dimitrios.dalagior...@gmail.com> wrote: Dear all, I have added several Z39.50 interfaces to my library but for some reason searching through Z39.50 no longer works; I get a connection timeout error message. Where should I start looking to remedy this? Kind regards, Dimitrios Dalagiorgos 3rd high school of Kozani Greece ___ 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] search_for_data_inconsistencies.pl: Bibliographic records have invalid MARCXML
Hi Jonathan
In file "search_for_data_inconsistencies.pl" I found the line
push @decoding_errors, $@ if $@;
which I changed to
push @decoding_errors, sprintf("ID=%s - %s", $biblio->biblionumber, $@);
After running "search_for_data_inconsistencies.pl" again, I found three
ID numbers saying:
DBIC result _type isn't of the _type BiblioMetadata at
/usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 124.
I searched for these numbers in the staff client and I found them - but
when trying to show the detail view Koha said:
The record you requested does not exist (10).
Also I found the content of these records in table "biblio" but not in
table "biblio_metadata".
Do you think it's safe to just delete these records in table "biblio"
and then to reindex the database?
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 02.10.23 um 11:08 schrieb Jonathan Druart:
Hi,
This is a bug, there is a lack of information. Please report on bugzilla
and if possible provide a patch.
You should be able to get more info (biblionumber) with the following
change:
diff --git a/misc/maintenance/search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl>
b/misc/maintenance/search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl>
index ddc6b457dd1..92de2bd91b8 100755
--- a/misc/maintenance/search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl>
+++ b/misc/maintenance/search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl>
@@ -126,7 +126,7 @@ use C4::Biblio qw( GetMarcFromKohaField );
while ( my $biblio = $biblios->next ) {
my $record = eval{$biblio->metadata->record;};
if ($@) {
- push @decoding_errors, $@;
+ push @decoding_errors, sprintf("ID=%s - %s",
$biblio->biblionumber, $@);
next;
}
my ( $biblionumber, $biblioitemnumber );
Regards,
Jonathan
Le dim. 1 oct. 2023 à 18:13, Michael Kuhn <mailto:m...@adminkuhn.ch>> a écrit :
Hi
We are using Koha 21.11.09 with MariaDB 10.3.38, running on Debian
GNU/Linux 10.
When running script "search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl>" we are getting
the following output:
== Bibliographic records have invalid MARCXML ==
* DBIC result _type isn't of the _type BiblioMetadata at
/usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl> line 124.
* DBIC result _type isn't of the _type BiblioMetadata at
/usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl> line 124.
* DBIC result _type isn't of the _type BiblioMetadata at
/usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl
<http://search_for_data_inconsistencies.pl> line 124.
=> The bibliographic records must have a valid MARCXML or you will face
encoding issues or wrong displays
Does anyone know how to obtain further information (biblionumbers?) for
these cases?
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
<mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch>
___
Koha mailing list http://koha-community.org <http://koha-community.org>
Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
<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] search_for_data_inconsistencies.pl: Can't call method "get_column"
Hi Jonathan Thanks for your message! You wrote: > Line 157 on this version is about authorised values. My guess is that > you have a value in marc_subfield_structure.authorised_value that does > not have an entry in the authorised_values table (column category). > > It can be considered as a bug for this script, and it seems (looking > at the code) that the bug still exists in master (so please report it > on bugzilla). I have now opened bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34974 (search_for_data_inconsistencies.pl: Can't call method "get_column") > 20.11.02? Did you typo the version? You should at least upgrade to the > latest 20.11.x! No typo, just a fact from an imperfect world... 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 dim. 1 oct. 2023 à 20:02, Michael Kuhn a écrit : Hi We are using Koha 20.11.02 with MariaDB 10.3.39, running on Debian GNU/Linux 10. When calling the script "search_for_data_inconsistencies.pl" the only output is the following: $ sudo koha-shell -c "perl /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl" instancename Can't call method "get_column" on an undefined value at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 157. Does anyone know how to solve this problem? 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] search_for_data_inconsistencies.pl: Can't call method "get_column"
Hi We are using Koha 20.11.02 with MariaDB 10.3.39, running on Debian GNU/Linux 10. When calling the script "search_for_data_inconsistencies.pl" the only output is the following: $ sudo koha-shell -c "perl /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl" instancename Can't call method "get_column" on an undefined value at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 157. Does anyone know how to solve this problem? 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] search_for_data_inconsistencies.pl: Bibliographic records have invalid MARCXML
Hi We are using Koha 21.11.09 with MariaDB 10.3.38, running on Debian GNU/Linux 10. When running script "search_for_data_inconsistencies.pl" we are getting the following output: == Bibliographic records have invalid MARCXML == * DBIC result _type isn't of the _type BiblioMetadata at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 124. * DBIC result _type isn't of the _type BiblioMetadata at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 124. * DBIC result _type isn't of the _type BiblioMetadata at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 124. => The bibliographic records must have a valid MARCXML or you will face encoding issues or wrong displays Does anyone know how to obtain further information (biblionumbers?) for these cases? 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] Koha ver 23.05
Hi Esmael You wrote: > KOHA v23.05 is not working when enable plack I cannot confirm this. Koha 23.05 works flawless with Plack enabled. For an example see http://adminkuhn.ch/wiki/Koha-Demoinstallation 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] Circulation rule for Collection.
Hi Rupinder Maybe the following thread gives you some more ideas concerning itemtypes and collection codes: https://lists.katipo.co.nz/pipermail/koha/2017-May/048124.html https://lists.katipo.co.nz/pipermail/koha/2017-June/048133.html 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 17.07.23 um 22:01 schrieb Rupinder Singh: You are absolutely right mr Delahunty, Circulation rules needs these two parameters, item type, patron catagory. But I was wondering if there is any way to restrict collection codes from circulating. Anyway, I guess I'll have to batch edit my records. Thank you so much Best Rupinder Singh On Tue, Jul 18, 2023, 12:01 AM Raymund Delahunty wrote: Hello Rupinder- I think you will have to rethink how you identify REF items in Koha. The Circulation fine and fee rules are defined by combinations of patron group and item type. The ccode isn't 'consulted' by Koha when deciding how long an item should loan (and all the other loan rules). Koha is only interested in WHO the borrower is (the patron category) and WHAT the item is (and that is the item type). I think you will need to set up a REF item type and use the Koha batch item modification tool to move items with the ccode of 'ref' to the new item type. And then you can set up all the rules. This problem isn't uncommon, I think. Different library management systems use different parameters to set the circulation rules. If my now fading memory serves me right our old Voyager LMS rules were set by the combination of patron category and Voyager 'location'. In Koha it is patron group and the item type. Ray Delahunty University of the Arts London -Original Message- From: Koha On Behalf Of Rupinder Singh Sent: Monday, July 17, 2023 2:36 PM To: koha@lists.katipo.co.nz Subject: [Koha] Circulation rule for Collection. Hi, In our library, all the reference books are catalogued under the item type "Books"; no additional item type is defined for reference books. However, reference books are marked with a CCODE "Ref", So now I want to set up a circulation rule for reference books or all items where CCODE is flagged "ref" that they are restricted from checkout. is there any way to do that? Thanks in advance Rupinder Singh ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY ___ 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] Where are the release notes for Koha 22.05.13
Hi Under https://download.koha-community.org/old_releases/ I see there was a version Koha 22.05.13 released on 25 May 2023. Unfortunately there was no release mail in mailing lists koha-devel or koha, also there is nothing under https://koha-community.org/koha-22-05-13-released/ Can anyone please tell me where I can find the release notes for Koha 22.05.13? 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] export our MARC21 records to other system
Hi You wrote: > Kindly, do you have any idea how to set our Z39 for other libraries > that can import our cataloging records from koha?? These links might help you: * https://wiki.koha-community.org/wiki/Setting_up_the_Z39.50_and_SRU_Server * https://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server 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] Starting rabbitmq-server fails with Koha 22.11.05-2
Hi Costantino You wrote: Hi, try this: sudo service mysql stop sudo service rabbitmq-server stop Create a "backup-temp" folder, move files from /var/lib/rabbitmq/ Then start services again. sudo service mysql start sudo service rabbitmq-server start I did the following but it didn't help: koha@koha:~$ sudo systemctl stop mysql koha@koha:~$ sudo systemctl stop rabbitmq-server koha@koha:~$ sudo mkdir /BACKUPTMP koha@koha:~$ sudo mv /var/lib/rabbitmq /BACKUPTMP koha@koha:~$ sudo systemctl start mysql koha@koha:~$ sudo systemctl start rabbitmq-server Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. As said, the basic problem seems to be that package "koha-common" 22.11.05-2 couldn't properly configure rabbitmq-server... 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 El 11-05-2023 10:27, Michael Kuhn escribió: Hi When trying to install Koha 22.11.05-2 via package installation on a completely new machine with 4 virtual CPUs, 4 GB RAM and Debian GNU/Linux 11 the following error appears: rabbitmq-server (3.8.9-3) wird eingerichtet ... Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript rabbitmq-server, action "start" failed. ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:14:44 CEST; 4ms ago Process: 38141 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 38141 (code=exited, status=1/FAILURE) CPU: 1.071s Mai 11 15:14:44 koha systemd[1]: Failed to start RabbitMQ Messaging Server. Mai 11 15:14:44 koha systemd[1]: rabbitmq-server.service: Consumed 1.071s CPU time. Can someone please tell me how to solve this problem? You can see the output of "systemctl status rabbitmq-server.service" resp. "journalctl -xe" just below. 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 [1] koha@koha:~$ sudo systemctl status rabbitmq-server.service ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:19:57 CEST; 3s ago Process: 41298 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 41298 (code=exited, status=1/FAILURE) CPU: 1.066s koha@koha:~$ sudo journalctl -xe ░░ An ExecStart= process belonging to unit rabbitmq-server.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support [2] ░░ ░░ The unit rabbitmq-server.service has entered the 'failed' state with result 'exit-code'. Mai 11 15:20:47 koha systemd[1]: Failed to start RabbitMQ Messaging Server. ░░ Subject: A start job for unit rabbitmq-server.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support [2] ░░ ░░ A start job for unit rabbitmq-server.service has finished with a failure. ░░ ░░ The job identifier is 3262 and the job result is failed. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Consumed 1.127s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support [2] ░░ ░░ The unit rabbitmq-server.service completed and consumed the indicated resources. Mai 11 15:20:48 koha sudo[41974]: koha : TTY=pts/0 ; PWD=/home/koha ; USER=root ; COMMAND=/usr/bin/journalctl -xe Mai 11 15:20:48 koha sudo[41974]: pam_unix(sudo:session): session opened for user root(uid=0) by koha(uid=1000) ___ Koha mailing list http://koha-community.org [3] Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha [4] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] [Koha-devel] Starting rabbitmq-server fails with Koha 22.11.05-2
Hi Jonathan You wrote: > Well, it's pretty obvious, everything is in the log: > """ > The process' exit code is 'exited' and its exit status is 1. > """ > > Heh :D > > I don't know! Did you try to stop and start it again? > systemctl rabbitmq-server stop > systemctl rabbitmq-server start It's not possible: koha@koha:~$ sudo systemctl rabbitmq-server stop Unknown command verb rabbitmq-server. koha@koha:~$ sudo systemctl rabbitmq-server start Unknown command verb rabbitmq-server. > Looks like it's not started so it won't certainly help. > Rebooted the VM? I did reboot the machine, it didn't change a thing. > Do you have elastic running as well (in such case 4G > of RAM won't be enough) No I'm not running Elasticsearch. At the moment it seems to me like there is a fundamental problem with package "koha-common" 22.11.05-2 when it cannot properly configure rabbitmq-server on a completely new machine. The problem didn't exist with version 22.11.03-1 but I don't know how to obtain this older version via APT. 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 11.05.23 um 16:08 schrieb Jonathan Druart: Well, it's pretty obvious, everything is in the log: """ The process' exit code is 'exited' and its exit status is 1. """ Heh :D I don't know! Did you try to stop and start it again? systemctl rabbitmq-server stop systemctl rabbitmq-server start Looks like it's not started so it won't certainly help. Rebooted the VM? Do you have elastic running as well (in such case 4G of RAM won't be enough) Le jeu. 11 mai 2023 à 15:27, Michael Kuhn a écrit : Hi When trying to install Koha 22.11.05-2 via package installation on a completely new machine with 4 virtual CPUs, 4 GB RAM and Debian GNU/Linux 11 the following error appears: rabbitmq-server (3.8.9-3) wird eingerichtet ... Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript rabbitmq-server, action "start" failed. ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:14:44 CEST; 4ms ago Process: 38141 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 38141 (code=exited, status=1/FAILURE) CPU: 1.071s Mai 11 15:14:44 koha systemd[1]: Failed to start RabbitMQ Messaging Server. Mai 11 15:14:44 koha systemd[1]: rabbitmq-server.service: Consumed 1.071s CPU time. Can someone please tell me how to solve this problem? You can see the output of "systemctl status rabbitmq-server.service" resp. "journalctl -xe" just below. 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@koha:~$ sudo systemctl status rabbitmq-server.service ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:19:57 CEST; 3s ago Process: 41298 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 41298 (code=exited, status=1/FAILURE) CPU: 1.066s koha@koha:~$ sudo journalctl -xe ░░ An ExecStart= process belonging to unit rabbitmq-server.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service has entered the 'failed' state with result 'exit-code'. Mai 11 15:20:47 koha systemd[1]: Failed to start RabbitMQ Messaging Server. ░░ Subject: A start job for unit rabbitmq-server.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit rabbitmq-server.service has finished with a failure. ░░ ░░ The job identifier is 3262 and the job result is failed. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Consumed 1.127s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service completed and consumed the indicated resources. Mai 11 15:20:48 koha sudo[41
[Koha] Starting rabbitmq-server fails with Koha 22.11.05-2
Hi When trying to install Koha 22.11.05-2 via package installation on a completely new machine with 4 virtual CPUs, 4 GB RAM and Debian GNU/Linux 11 the following error appears: rabbitmq-server (3.8.9-3) wird eingerichtet ... Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript rabbitmq-server, action "start" failed. ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:14:44 CEST; 4ms ago Process: 38141 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 38141 (code=exited, status=1/FAILURE) CPU: 1.071s Mai 11 15:14:44 koha systemd[1]: Failed to start RabbitMQ Messaging Server. Mai 11 15:14:44 koha systemd[1]: rabbitmq-server.service: Consumed 1.071s CPU time. Can someone please tell me how to solve this problem? You can see the output of "systemctl status rabbitmq-server.service" resp. "journalctl -xe" just below. 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@koha:~$ sudo systemctl status rabbitmq-server.service ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:19:57 CEST; 3s ago Process: 41298 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 41298 (code=exited, status=1/FAILURE) CPU: 1.066s koha@koha:~$ sudo journalctl -xe ░░ An ExecStart= process belonging to unit rabbitmq-server.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service has entered the 'failed' state with result 'exit-code'. Mai 11 15:20:47 koha systemd[1]: Failed to start RabbitMQ Messaging Server. ░░ Subject: A start job for unit rabbitmq-server.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit rabbitmq-server.service has finished with a failure. ░░ ░░ The job identifier is 3262 and the job result is failed. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Consumed 1.127s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service completed and consumed the indicated resources. Mai 11 15:20:48 koha sudo[41974]: koha : TTY=pts/0 ; PWD=/home/koha ; USER=root ; COMMAND=/usr/bin/journalctl -xe Mai 11 15:20:48 koha sudo[41974]: pam_unix(sudo:session): session opened for user root(uid=0) by koha(uid=1000) ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] How To Add OCLC in Koha Z39.50 Server.
Hi
You wrote:
> Dear, I changed the settings as you said but it says book search
> result not found. I have attached the modified Z30.50 screenshot link
> below please reply.
>
> Z30.50 Screenshot link: https://i.ibb.co/vwrx0rZ/Z39-50-Server.png
> Book Search Result: https://i.ibb.co/KFtGJCG/Capture-result.png
Please carefully read
https://help.oclc.org/Metadata_Services/Z3950_Cataloging/Get_started/Configuration_guide_for_OCLC_Z39.50_Cataloging
It says: "ID authentication: OCLC supports ID/authentication as
prescribed by the standard. We recognize the userId and password fields;
the groupId field is ignored. The service patron password is the
password that must be used."
As Mark Alexander showed in his posting, OCLC complains about "Invalid
Autho/password".
Thus I assume the Z30.50 service of OCLC is not freely available but you
will need to obtain a valid userId and password, or use another service.
Hope this helps.
Best wishes: Michael Kuhn
--
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 Fri, May 5, 2023 at 4:31 PM Mark Alexander wrote:
I'm not an expert on this, but it appears that zcat.oclc.org requires
you to provide your OCLC user name and password, as mentioned in the
message mentioned previously:
https://www.mail-archive.com/koha@lists.katipo.co.nz/msg25554.html
Here is what happened when I tried to connect using yaz-client without
username/password:
% yaz-client zcat.oclc.org:210/OLUCWorldCat
Connecting...OK.
Sent initrequest.
Connection rejected by v3 target.
UserInformationfield:
{
OID: 1 2 840 10003 10 1000 17 1
{
ANY (len=29)
}
}
OCLC UserInformation:
{
failReason TRUE
text 'Invalid Autho/password'
}
Options: search present delSet triggerResourceCtrl scan sort
extendedServices namedResultSets
Elapsed: 0.193017
--
Fundamentally, there may be no basis for anything. --Ashleigh Brilliant
___
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] How To Add OCLC in Koha Z39.50 Server.
Hi You wrote: > I Successfully Configuration to Z39.50 but the catalogue title search > result "Connection failed to zcat.oclc.org <http://zcat.oclc.org>" > > Z39.50 Server Configuration Details Link Enclosed Please check and > reply to me. > > https://i.ibb.co/CWxwZ56/Screenshot-2023-05-05-16-06-01.png In your screenshot I see you inserted "z3950.somedoamain.org" as the hostname - this was just an example. Of course you need to insert a valid hostname (like "zcat.oclc.org"). Also it probably isn't correct to use database "OCLCAuthoritiesLC" when using record type "Bibliographic". For this record type you will probably need database "OLUCWorldCat". Hope this helps. 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 I Successfully Configuration to Z39.50 but the catalogue title search result "Connection failed to zcat.oclc.org <http://zcat.oclc.org>" Z39.50 Server Configuration Details Link Enclosed Please check and reply to me. https://i.ibb.co/CWxwZ56/Screenshot-2023-05-05-16-06-01.png <https://i.ibb.co/CWxwZ56/Screenshot-2023-05-05-16-06-01.png> On Fri, May 5, 2023 at 3:54 PM Michael Kuhn <mailto:m...@adminkuhn.ch>> wrote: Hi MAMCET Library You wrote: > How to Add OCLC WORLD Catalogue in Koha Z39.50 Server. > http://classify.oclc.org/classify2/ <http://classify.oclc.org/classify2/> The following post by Heather Siemoin may help you: https://www.mail-archive.com/koha@lists.katipo.co.nz/msg25554.html <https://www.mail-archive.com/koha@lists.katipo.co.nz/msg25554.html> Also the following page by OCLC: https://help.oclc.org/Metadata_Services/Z3950_Cataloging/Get_started/Configuration_guide_for_OCLC_Z39.50_Cataloging <https://help.oclc.org/Metadata_Services/Z3950_Cataloging/Get_started/Configuration_guide_for_OCLC_Z39.50_Cataloging> Best wishes: Michael Kuhn -- 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 <mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> ___ Koha mailing list http://koha-community.org <http://koha-community.org> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha <https://lists.katipo.co.nz/mailman/listinfo/koha> -- Thanking you.. Librarian, MAMCET <http://mamcet.com/> Trichy-Chennai Trunk Road, Siruganur, Tiruchirappalli-621 105. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] How To Add OCLC in Koha Z39.50 Server.
Hi MAMCET Library You wrote: > How to Add OCLC WORLD Catalogue in Koha Z39.50 Server. > http://classify.oclc.org/classify2/ The following post by Heather Siemoin may help you: https://www.mail-archive.com/koha@lists.katipo.co.nz/msg25554.html Also the following page by OCLC: https://help.oclc.org/Metadata_Services/Z3950_Cataloging/Get_started/Configuration_guide_for_OCLC_Z39.50_Cataloging Best wishes: Michael Kuhn -- 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] Koha and IPV6
Hi Chris
On 20 February you wrote:
> If you want to run it via IPV6 you will just need to set up Apache (or
> Nginx or whatever you have in front of plack) to support IPV6 (and the
> networking itself of course) and then it should work fine.
> There should be no tricks needed
Thanks for your answer!
Meanwhile we have set up the Apache HTTP Server to support IPV6. Just
for anyone who may need this information in the future I describe what
we actually have done. I'm not exactly sure if everything is really
necessary but however it seems to work for us.
Here our instance is called "subdomain" ; IPV6 address is given as
::::::: ; IPV4 address is given as
xxx.xxx.xxx.xxx ; we are using a X.509 certifivate from Let's Encrypt.
1. Don't deactivate IPV6 in file "/etc/sysctl.conf".
# cat /proc/sys/net/ipv6/conf/all/disable_ipv6
1
2. In file "/etc/hosts" we included our IPV4 address as well as our IPV6
address.
xxx.xxx.xxx.xxx subdomain.domain.xx
::::::: subdomain.domain.xx
3. The configuration of the Apache HTTP Server in file
"/etc/apache2/sites-available/subdomain.conf" looks as follows.
# Koha instance opac Apache config.
# redirect http to https
xxx.xxx.xxx.xxx:80>
ServerName subdomain.domain.xx
ServerAlias subdomain.domain.xx
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
xxx.xxx.xxx.xxx:8080>
ServerName subdomain.domain.xx
ServerAlias subdomain.domain.xx
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/?(.*) https://%{SERVER_NAME}:8443/$1 [R,L]
# OPAC
xxx.xxx.xxx.xxx:443>
SSLEngine on
SSLProtocol +TLSv1.2 +TLSv1.1 +TLSv1
SSLCompression off
SSLHonorCipherOrder on
SSLCipherSuite
"ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-SA-
SSLCertificateKeyFile
/etc/letsencrypt/live/subdomain.domain.xx/privkey.pem
SSLCertificateFile
/etc/letsencrypt/live/subdomain.domain.xx/cert.pem
SSLCertificateChainFile
/etc/letsencrypt/live/subdomain.domain.xx/chain.pem
= 2.4>
Define instance "subdomain"
Include /etc/koha/apache-shared.conf
# Include /etc/koha/apache-shared-disable.conf
# Include /etc/koha/apache-shared-opac-plack.conf
Include /etc/koha/apache-shared-opac.conf
ServerName subdomain.domain.xx
SetEnv KOHA_CONF "/etc/koha/sites/subdomain/koha-conf.xml"
AssignUserID subdomain-koha subdomain-koha
ErrorLog/var/log/koha/subdomain/opac-error.log
# TransferLog /var/log/koha/subdomain/opac-access.log
# Intranet
xxx.xxx.xxx.xxx:8443>
SSLEngine on
SSLProtocol +TLSv1.2 +TLSv1.1 +TLSv1
SSLCompression off
SSLHonorCipherOrder on
SSLCipherSuite
"ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES
SSLCertificateKeyFile
/etc/letsencrypt/live/subdomain.domain.xx/privkey.pem
SSLCertificateFile
/etc/letsencrypt/live/subdomain.domain.xx/cert.pem
SSLCertificateChainFile
/etc/letsencrypt/live/subdomain.domain.xx/chain.pem
= 2.4>
Define instance "subdomain"
Include /etc/koha/apache-shared.conf
# Include /etc/koha/apache-shared-disable.conf
# Include /etc/koha/apache-shared-intranet-plack.conf
Include /etc/koha/apache-shared-intranet.conf
ServerName subdomain.domain.xx
SetEnv KOHA_CONF "/etc/koha/sites/subdomain/koha-conf.xml"
AssignUserID subdomain-koha subdomain-koha
ErrorLog/var/log/koha/subdomain/intranet-error.log
# TransferLog /var/log/koha/subdomain/intranet-access.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
Am 20.02.23 um 21:39 schrieb Chris Cormack:
Kia ora Michael
Chris
On 21/02/23 09:36, Michael Kuhn wrote:
Hi
Our library can access the the future virtual machine running Koha
only via IPV6. I coulnd't find the terms IPV4 or IPV6 neither in
https://wiki.koha-community.org/wiki/System_requirements_and_recommendations nor in the current Koha manual. Thus my question (since until now I have implemented only Koha-installations with IPV4):
Is Koha able to run just with IPV6 addresses, also when using Let's
Encrypt?
Are there maybe some caveats?
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 mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] auto_increment problem with holds in Koha 21.11
Hi We are working on Debian GNU/Linux 10 with MariaDB 10.3.38 and Koha 21.11.09. Since about September 2022 after the update from Koha 18.11 to 21.11 we see auto_increment problems with tables "reserves" and "old_reserves" (but NOT with any of the other tables): The following ids exist in both tables reserves and old_reserves: 372 In fact every single hold evokes the problem. Deleting the id manually from table "old_reserves" does always solve the problem: DELETE FROM old_reserves WHERE reserve_id IN (372); According to https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix the auto_increment problem should not occur at all after Koha 17.05. What could be the reason for this behavior? 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] Can the Koha Mailing List and DMARC become friends?
Hi David You wrote: > Again, a platform change is just something to consider. If there's no > critical mass of people reporting that the communications platforms > are insufficient or unsatisfying, then it's not worth discussing or > pursuing. For me the current mailing list is satisfying and completely sufficient. If I'd feel otherwise I'd first consider consulting the archives which can be found at * https://lists.katipo.co.nz/public/koha/ * https://lists.katipo.co.nz/pipermail/koha/ * https://koha.markmail.org/ 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 Thu, Mar 9, 2023 at 5:48 PM Thomas Dukleth wrote: [Resending to correct accidental paste in my message but adding consideration of use of Discourse as a partial workaround.] 2. Discourse. Does Discourse mailing list mode avoid problems with DMARC in a manner that is still sensible for offline use? Mailing lists are good for offline use. Does discourse provide something similar to Mailman "munging the from header" so that the message poster is identified in the email from header originating from the Discourse server allowing email clients to display lists of messages helpfully including by message poster in addition to subject and time? Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 ___ 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] Koha and IPV6
Hi Our library can access the the future virtual machine running Koha only via IPV6. I coulnd't find the terms IPV4 or IPV6 neither in https://wiki.koha-community.org/wiki/System_requirements_and_recommendations nor in the current Koha manual. Thus my question (since until now I have implemented only Koha-installations with IPV4): Is Koha able to run just with IPV6 addresses, also when using Let's Encrypt? Are there maybe some caveats? 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] Missing item type icons in staff client of Koha 22.11.00
Hi Fridolin You wrote: > Which icons are you using ? > > There has been this change in 20.11, 20.05 : > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23148 After my message from 8 February George Veranis filed the following bug and already wrote a working patch: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32908 (Item type icons broken in the bibliographic record details page) 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 Which icons are you using ? There has been this change in 20.11, 20.05 : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23148 Best regards, Le 08/02/2023 à 01:59, Michael Kuhn a écrit : Hi Our library uses Koha 22.11.00 with Debian GNU/Linux 11. We chose icons for our item types - these icons show correctly in the OPAC, e. g. the book icon plus the text "book". But in the staff client instead of the icon just the description of the item type is shown - which results showing "book" (instead of the icon) plus the text "book". Thus "book book". No icon. I have tested this also on my demo installation, it's the same. Is this a bug or can anyone give us a hint how to solve the problem? Best wishes: Michael ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] exportar registros marc bibliográficos en formato isbd
Hi Brenda You wrote: > Existe alguna herramienta o programación que pueda aplicarse para > exportar, en lote, registros bibliográficos en formato isbd? Is there > any tool or programming that can be applied to export, in batch, > bibliographic records in isbd format? If you're in the OPAC detail view, there is an option "Save record" on the right side, that allows you to export every bibliographic record in ISBD format. (In the staff client you will be able to display your records in the internal ISBD format, but not to download them) Also if you have filled your cart in the OPAC with some records, there is an option "Download" which allows to export all marked records in the cart to export in the ISBD format. Well in fact at least it says it is ISBD format; but in fact the result is - according to the content of Koha system parameter "OPACISBD" - some plain text, enriched with CR characters and some HTML entities, like the following (as shown in editor vi): Ein Engel kommt nach Babylon : eine fragmentarische Komödie in drei Akten / ^MFriedrich Dürrenmatt. ^M - Zürich : Diogenes, 1980. ^M - 141 p. ; 18 cm. ^M - Diogenes Taschenbuch ; 250/4 .^M "Neufassung 1980." ^MISBN: 3257208340 ^MLCCN: 84179304 ^MLC Class. No.: MLCS 84/8918 (P) ^M Also see * https://koha-community.org/manual/22.11/en/html/opacpreferences.html#opacisbd * https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13695 (Allow ISBD format export) Hope this helps. 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] Missing item type icons in staff client of Koha 22.11.00
Hi George Thank you very much! I tested your patch (by just including your correction into the file on our host) - it works as expected and the item type are now visible in the staff client! In Bugzilla I have just set the status of bug 32908 from "Needs Signoff" to "Signed off" (though I'm not sure if that's the way how to do 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 Am 08.02.23 um 13:33 schrieb gvera...@dataly.gr: Ok the patch is there : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32908 Please test it and if you like it sign off it! Thanks, George Veranis Dataly Tech Στις 2023-02-08 14:09, gvera...@dataly.gr έγραψε: Hi Michael, We will submit a patch today about that. The bug is : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32908 Στις 2023-02-08 13:59, Michael Kuhn έγραψε: Hi Our library uses Koha 22.11.00 with Debian GNU/Linux 11. We chose icons for our item types - these icons show correctly in the OPAC, e. g. the book icon plus the text "book". But in the staff client instead of the icon just the description of the item type is shown - which results showing "book" (instead of the icon) plus the text "book". Thus "book book". No icon. I have tested this also on my demo installation, it's the same. Is this a bug or can anyone give us a hint how to solve the problem? 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] Missing item type icons in staff client of Koha 22.11.00
Hi Our library uses Koha 22.11.00 with Debian GNU/Linux 11. We chose icons for our item types - these icons show correctly in the OPAC, e. g. the book icon plus the text "book". But in the staff client instead of the icon just the description of the item type is shown - which results showing "book" (instead of the icon) plus the text "book". Thus "book book". No icon. I have tested this also on my demo installation, it's the same. Is this a bug or can anyone give us a hint how to solve the problem? 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] Koha 22.05.04: Can't locate Koha/Script.pm in @INC
Hi Tomas You wrote: > Yeah, the docs are really generic, and there are several ways to > install Koha. Packages (i.e. having koha-shell) is one of them. Please > file an issue on the manual's project so we document it better. I have now filed https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32059 (How to run scripts found under https://perldoc.koha-community.org/) > Regarding the fact it worked before, have you changed the server? It > is not working because of the lack of some environment variables being > set, which is usually the case when we reinstall on a new server and > forgot all the tweaks we did over time. I've been there, many times > heh. No, it was a completely new server. I have done this many times on many different new servers in the past and it always worked. But yes, missing environment variables are a pain. > Regardless, running things as root can cause trouble with logs and > lock files permissions. Some default cronjobs can fail to run because > of that, hence the recommendation. There are also security concerns > but that's out of the scope here. Since it also worked using the command "koha-shell" that's how I'll do it in the future: sudo koha-shell -c "/usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=frameworkcode -file file.marcxml -v 2" instancename 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 El sáb, 29 oct 2022 5:11, Michael Kuhn <mailto:m...@adminkuhn.ch>> escribió: Hi Thomas You wrote: > Are you by chance running the command in the root shell? Yes I am, I always did (and it worked up to Koha 21.11). For now it worked using: # export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml # export PERL5LIB=/usr/share/koha/lib # /usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2 > You should always run it inside koha-shell OK - next time I'll try: $ sudo koha-shell -c "/usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2" library Unfortunately https://perldoc.koha-community.org/misc/migration_tools/bulkmarcimport.html <https://perldoc.koha-community.org/misc/migration_tools/bulkmarcimport.html> does not give the correct information how to run this script. 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 <mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> > El vie, 28 oct 2022 8:03, Michael Kuhn mailto:m...@adminkuhn.ch> > <mailto:m...@adminkuhn.ch <mailto:m...@adminkuhn.ch>>> escribió: > > Hi > > I am running a fresh installation of Koha 22.05.04 on Debian 11. > > I am trying to load some data using "bulkmarcimport.pl <http://bulkmarcimport.pl> > <http://bulkmarcimport.pl <http://bulkmarcimport.pl>>": > > # export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml > # /usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> > <http://bulkmarcimport.pl <http://bulkmarcimport.pl>> -b -m marcxml > -framework=ABC -file TITEL.marcxml -v 2 > Can't locate Koha/Script.pm in @INC (you may need to install the > Koha::Script module) (@INC contains: /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 > /usr/local/share/perl/5.32.1 > /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 > /usr/share/perl/5.32 /usr/local/lib/site_perl) at > /usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> > <http://bulkmarcimport.pl <http://bulkmarcimport.pl>> line 13. > BEGIN failed--compilation aborted at > /usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> > <http://bulkmarcimport.pl <http://bulkmarcimport.pl>> line 13. > > "Script.pm" seems to be there: > > # ls -al /usr/share/koha/lib/Koha/Script.pm > -rw-r--r-- 1 root root 4129 24. Aug 07:51 > /usr/share/koha/l
Re: [Koha] Koha 22.05.04: Can't locate Koha/Script.pm in @INC
Hi Thomas You wrote: > Are you by chance running the command in the root shell? Yes I am, I always did (and it worked up to Koha 21.11). For now it worked using: # export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml # export PERL5LIB=/usr/share/koha/lib # /usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2 > You should always run it inside koha-shell OK - next time I'll try: $ sudo koha-shell -c "/usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2" library Unfortunately https://perldoc.koha-community.org/misc/migration_tools/bulkmarcimport.html does not give the correct information how to run this script. 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 El vie, 28 oct 2022 8:03, Michael Kuhn <mailto:m...@adminkuhn.ch>> escribió: Hi I am running a fresh installation of Koha 22.05.04 on Debian 11. I am trying to load some data using "bulkmarcimport.pl <http://bulkmarcimport.pl>": # export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml # /usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2 Can't locate Koha/Script.pm in @INC (you may need to install the Koha::Script module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at /usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> line 13. BEGIN failed--compilation aborted at /usr/share/koha/bin/migration_tools/bulkmarcimport.pl <http://bulkmarcimport.pl> line 13. "Script.pm" seems to be there: # ls -al /usr/share/koha/lib/Koha/Script.pm -rw-r--r-- 1 root root 4129 24. Aug 07:51 /usr/share/koha/lib/Koha/Script.pm How can I get script "bulkmarcimport.pl <http://bulkmarcimport.pl>" to actually run? 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 <mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> ___ Koha mailing list http://koha-community.org <http://koha-community.org> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha <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] [Koha-devel] Koha 22.05.04: Can't locate Koha/Script.pm in @INC
Hi David and Indranil Thank you very much, this works! Interestingly addin variable PERL5LIB was never before necessary when I ran "bulkmarcimport.pl" (and I do this a lot). 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 28.10.22 um 13:14 schrieb David Schmidt: hi add that path to your PERL5LIB env var $ export PERL5LIB=/usr/share/koha/lib $ /usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2 cheers david Am 28.10.22 um 13:06 schrieb Indranil Das Gupta: > Hi Michael > > From the snippet shared by you, it seems that you are missing: > > export PERL5LIB="/usr/share/koha/lib" > > cheers > -idg On Fri, 28 Oct 2022, at 1:02 PM, Michael Kuhn wrote: Hi I am running a fresh installation of Koha 22.05.04 on Debian 11. I am trying to load some data using "bulkmarcimport.pl": # export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml # /usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2 Can't locate Koha/Script.pm in @INC (you may need to install the Koha::Script module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at /usr/share/koha/bin/migration_tools/bulkmarcimport.pl line 13. BEGIN failed--compilation aborted at /usr/share/koha/bin/migration_tools/bulkmarcimport.pl line 13. "Script.pm" seems to be there: # ls -al /usr/share/koha/lib/Koha/Script.pm -rw-r--r-- 1 root root 4129 24. Aug 07:51 /usr/share/koha/lib/Koha/Script.pm How can I get script "bulkmarcimport.pl" to actually run? 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 <mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> ___ Koha-devel mailing list koha-de...@lists.koha-community.org <mailto:koha-de...@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/> ___ Koha-devel mailing list koha-de...@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/ ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Koha 22.05.04: Can't locate Koha/Script.pm in @INC
Hi I am running a fresh installation of Koha 22.05.04 on Debian 11. I am trying to load some data using "bulkmarcimport.pl": # export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml # /usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=ABC -file TITEL.marcxml -v 2 Can't locate Koha/Script.pm in @INC (you may need to install the Koha::Script module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at /usr/share/koha/bin/migration_tools/bulkmarcimport.pl line 13. BEGIN failed--compilation aborted at /usr/share/koha/bin/migration_tools/bulkmarcimport.pl line 13. "Script.pm" seems to be there: # ls -al /usr/share/koha/lib/Koha/Script.pm -rw-r--r-- 1 root root 4129 24. Aug 07:51 /usr/share/koha/lib/Koha/Script.pm How can I get script "bulkmarcimport.pl" to actually run? 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] Introduction/Request for Assistance
Hi Mathew You wrote yesterday: > That being said, I played around with the framework and Koha mapping, > and now I cannot figure out how to run the “batch rebuild biblio > tables” perl script cronjob. Every time I try to run it, I get certain > errors such as “unable to locate dbh..” You didn't write what exactly you have tried. Usually script "batchRebuildBiblioTables.pl" isn't used as a cronjob. However, you may execute it as Linux user "koha" as follows. Just replace "instance" with the name of your Koha instance. sudo koha-shell -c "perl batchRebuildBiblioTables.pl" instance Also see: * https://perldoc.koha-community.org/misc/batchRebuildItemsTables.html * https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-shell Hope this helps. Best wishes: micahel -- 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] Excess fields in Koha 22.05 file "patron_import.csv"
Hi When unloading the field names of Koha 22.05 table "borrowers" I get 79 field names (plus "borrowernumber"). But when in Koha 22.05 menu "Tools > Import patrons" I click the link "Starter CSV file" the unloaded file "patron_import.csv" does include 82 fields. When comparing the two outputs I see there are three more fields in file "patron_import.csv" than in table "borrowers": patron_attributes guarantor_relationship guarantor_id These three fields aren't included in https://schema.koha-community.org/22_05/tables/borrowers.html What is the explanation for these excess fields? 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] [Koha-devel] Critical error on Koha website
Hi Liz You wrote: > This was related to an update to Wordpress and the theme we use. Have > sorted out those issues and things are seeming better now, if you'd > please test! I noticed two things: 1. For example in https://koha-community.org/koha-community-newsletter-september-2022/ I am using HTML headings , and - they should all use a larger font size than the normal writing. h2 should be larger than h3, h3 should be larger than h4. At the moment h4 seems to be larger than h3. (or did you just change that some minutes ago?) 2. For example in https://koha-community.org/koha-22-05-05-released/ I have noticed many wrong special characters, you can best see this in section "Credits" ath the end where many names are mutilated, like Tomás Cohen Arazi (10) Jérémy Breuillard (1) Frédéric Demians (1) Joonas Kylmälä (2) Adolfo RodrÃguez (1) etc. Seems like Wordpress isn't using proper UTF-8. 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 Thu, Sep 29, 2022 at 2:51 PM Michael Kuhn <mailto:m...@adminkuhn.ch>> wrote: Hi When I'm trying to preview or release the current Koha newsletter I'm getting the following message: There has been a critical error on this website. I'm also getting this message when I try to access older newsletters, for example * https://koha-community.org/koha-community-newsletter-april-2022/ <https://koha-community.org/koha-community-newsletter-april-2022/> * https://koha-community.org/koha-community-newsletter-august-2022/ <https://koha-community.org/koha-community-newsletter-august-2022/> Can someone with the necessary rights and knowledge please remove this problem? 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 <mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> ___ Koha-devel mailing list koha-de...@lists.koha-community.org <mailto:koha-de...@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/> ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Critical error on Koha website
Hi When I'm trying to preview or release the current Koha newsletter I'm getting the following message: There has been a critical error on this website. I'm also getting this message when I try to access older newsletters, for example * https://koha-community.org/koha-community-newsletter-april-2022/ * https://koha-community.org/koha-community-newsletter-august-2022/ Can someone with the necessary rights and knowledge please remove this problem? 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] Upgrade
Hi D. Gnanasekaran You wrote: > I am using the version 19.05 and would like to upgrade to the higher > versions. May I know the step by step procedures for the upgrade? > with thanks, You will find the official upgrading instructions at https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrading_Koha Of course it is also a good idea to create a backup before trying to upgrade. Hope this helps. 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
Hi Marcel
Yesterday you wrote:
> 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.
We have done this before and I did this again today. At the moment there
are no biblionumbers existing in table "deletedbiblio" that also exist
in table "biblio". Menu "About Koha > System information" does not show
errors anymore.
> 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.
I have checked the currentauto_increment values for all tables, the
values in the normal tables are always higher than the ones in the
respective deleted tables:
147200 - biblio
146933 - deletedbiblio
147200 - biblio_metadata
68588 - deletedbiblio_metadata
147200 - biblioitems
NULL - deletedbiblioitems
73229 - items
NULL - deleteditems
So if I understand right with this setup when using MariaDB 10.5.15 the
problem should no more happen.
Unfortunately I'm quite sure it will happen again anyway (as before). I
will then write to the list again.
PS: This is the 3rd trial to get this e-mail through.
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
____
Van: Koha namens Michael Kuhn
Verzonden: donderdag 25 augustus 2022 11:03
Aan: Koha
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-community.org%2Fwiki%2FDBMS_auto_increment_fixdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=5BkXPF4yrrhvuLP1nFx66eQITkFCQPhoGPDtsdCDWso%3Dreserved=0
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
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=fS0wgTtECweT98NfdwYV%2FV82IYhpm82iqLYuWP8war4%3Dreserved=0
___
Koha mailing list
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1
Re: [Koha] DBMS auto increment fix not working
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
: 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 m...@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 namens Michael Kuhn
Verzonden: donderdag 25 augustus 2022 11:03
Aan: Koha
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-community.org%2Fwiki%2FDBMS_auto_increment_fixdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=5BkXPF4yrrhvuLP1nFx66eQITkFCQPhoGPDtsdCDWso%3Dreserved=0
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
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=fS0wgTtECweT98NfdwYV%2FV82IYhpm82iqLYuWP8war4%3Dreserved=0
___
Koha mailing list
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=8d%2BiOpLG4oo49VF%2BwC9Y9hA7ZDJ6nUxcb2v7K1qdaxs%3Dreserved=0
Koha@lists.katipo.co.nz
Unsubscribe:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkohadata=05%7C01%7Cm.de.roo
Re: [Koha] DBMS auto increment fix not working
Hi Marcel On 30 August you wrote: > 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. We have done this before and I did this again today. At the moment there are no biblionumbers existing in table "deletedbiblio" that also exist in table "biblio". Menu "About Koha > System information" does not show errors anymore. > 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. I have checked the currentauto_increment values for all tables, the values in the normal tables are always higher than the ones in the respective deleted tables: 147200 - biblio 146933 - deletedbiblio 147200 - biblio_metadata 68588 - deletedbiblio_metadata 147200 - biblioitems NULL - deletedbiblioitems 73229 - items NULL - deleteditems So if I understand right with this setup when using MariaDB 10.5.15 the problem should no more happen. Unfortunately I'm quite sure it will happen again anyway (as before). I will then write to the list again. PS: This is the 4th trial to get this e-mail through, this time omitting the thread. 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
Hi Marcel
Yesterday you wrote:
> 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.
We have done this before and I did this again today. At the moment there
are no biblionumbers existing in table "deletedbiblio" that also exist
in table "biblio". Menu "About Koha > System information" does not show
errors anymore.
> 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.
I have checked the currentauto_increment values for all tables, the
values in the normal tables are always higher than the ones in the
respective deleted tables:
147200 - biblio
146933 - deletedbiblio
147200 - biblio_metadata
68588 - deletedbiblio_metadata
147200 - biblioitems
NULL - deletedbiblioitems
73229 - items
NULL - deleteditems
So if I understand right with this setup when using MariaDB 10.5.15 the
problem should no more happen.
Unfortunately I'm quite sure it will happen again anyway (as before). I
will then write to the list again.
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 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 namens Michael Kuhn
Verzonden: donderdag 25 augustus 2022 11:03
Aan: Koha
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-community.org%2Fwiki%2FDBMS_auto_increment_fixdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C5c1a779522df4601c58808da8678d0b4%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637970150719835805%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=5BkXPF4yrrhvuLP1nFx66eQITkFCQPhoGPDtsdCDWso%3Dreserved=0
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
https://eur03.safelinks.protection.outlook.com/?url=http%
Re: [Koha] DBMS auto increment fix not working
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
[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://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] Call for news - Newsletter August 2022
Hi I'm collecting news for the August 2022 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 -- 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] n-Tier deployment of Koha
Hi Admire David Cook has written: > - If you're getting a lot of traffic, you should check to see how much > traffic is from bots. You might need to implement something like > fail2ban to block bots that put too much load on your system. > Typically, I find when Koha is overwhelmed, it's due to bots. (You can > experiment with a robots.txt file to help with this but it's not a > completely effective solution.) To limit performance loss caused by bots it is also a good idea to create a Koha sitemap, see https://koha-community.org/manual/21.11/en/html/cron_jobs.html#sitemap Script "koha-sitemap" lets you manage sitemaps for your Koha instances (to avoid annoying bots eating up your CPU). https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-sitemap 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] [Koha-devel] Dependency problem when installing Koha 21.11.10 on Debian 11
Hi Harald You wrote: > under Ubuntu there is a file /var/log/apt/term.log, which has a > detailed protocol about the installation initiated by the apt command. > > Might be it exists also under debian. > > Have you checked this file after the half-done installation of > rabbitmq-server? No, I didn't, but thanks for the hint! Meanwhile I was able to solve the (networking) problem as described in the mail attached below. 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 Weitergeleitete Nachricht Betreff: Re: [Koha-devel] Dependency problem when installing Koha 21.11.10 on Debian 11 Datum: Fri, 5 Aug 2022 08:11:56 +0200 Von: Michael Kuhn Antwort an: Michael Kuhn Organisation: Admin Kuhn GmbH An: Michael Hafen Kopie (CC): koha-de...@lists.koha-community.org, Koha Hi Michael Thank you so much! After going througfh the files in directory "/var/log/rabbitmq" I found some error reading ERROR: epmd error for host YOUR_HOSTNAME: timeout (timed out) solution Eventually I was able to solve the problem by adding the hostname to the 127.0.0.1 line in file "/etc/hosts": 127.0.0.1 bib-katalog localhost There are probably other solutions but for now I'm fine. Thanks again! And of course, as Mason wrote, the following command is now successful: # systemctl status rabbitmq-server.service | grep -i status Status: "Initialized" 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 04.08.22 um 16:46 schrieb Michael Kuhn: Hi Mason You wrote: >> Do you maybe have any hint how to find out what could be the problem >> with the failing configuration of package "rabbitmq-server"? > > try reinstalling rabbitmq-server first, then installing koha-common > > # apt purge rabbitmq-server koha-common > # apt install rabbitmq-server > # apt install koha-common > > > note the 'Status' value when rabbitmq is running correctly > > root@deb11:# systemctl status rabbitmq-server.service > * rabbitmq-server.service - RabbitMQ Messaging Server > Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; > enabled; vendor pre> > Active: active (running) since Thu 2022-08-04 13:21:32 UTC; 2min > 56s ago > Main PID: 5844 (beam.smp) > Status: "Initialized" <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > Tasks: 86 (limit: 2190) > Memory: 75.3M > CPU: 11.458s > CGroup: /system.slice/rabbitmq-server.service > |-5844 /usr/lib/erlang/erts-11.1.8/bin/beam.smp -W w -K > true -A 64 -MBas> > |-5944 erl_child_setup 65536 > |-5994 inet_gethost 4 > `-5995 inet_gethost 4 > >> >> Did anyone out there successfully install either Koha 21.11.10 or >> Koha 22.05.03 on a new machine with Debian GNU/Linux 11? > > yes, i confirmed that both versions install ok on deb11 I just purged both packages, then tried to install "rabbitmq-server": root@bib-katalog:~# apt install rabbitmq-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: at daemon docbook-xml docbook-xsl fontconfig fonts-dejavu fonts-dejavu-extra gettext graphviz gsfonts icu-devtools idzebra-2.0 idzebra-2.0-common idzebra-2.0-doc idzebra-2.0-utils libalgorithm-c3-perl libalgorithm-checkdigits-perl libann0 libany-uri-escape-perl libanyevent-http-perl libanyevent-perl libapache-logformat-compiler-perl libapache2-mpm-itk libappconfig-perl libarchive-extract-perl libarchive-zip-perl libarray-utils-perl libasync-interrupt-perl libauth-googleauth-perl libauthen-cas-client-perl libb-debug-perl libb-hooks-endofscope-perl libb-hooks-op-check-perl libbarcode-code128-perl libbiblio-endnotestyle-perl libbit-vector-perl libbusiness-isbn-data-perl libbusiness-isbn-perl libbusiness-issn-perl libbytes-random-secure-perl libcache-memcached-fast-perl libcache-memcached-fast-safe-perl libcache-memcached-perl libcairo2 libcapture-tiny-perl libcarp-assert-more-perl libcarp-assert-perl libcarp-clan-perl libcdt5 libcgi-compile-perl libcgi-emulate-psgi-perl libcgi-session-driver-memcached-perl libcgi-session-perl libcgraph6 libclass-accessor-chained-perl libclass-accessor-grouped-perl libclass-accessor-perl libclass-adapter-perl libclass-c3-com
Re: [Koha] [Koha-devel] Dependency problem when installing Koha 21.11.10 on Debian 11
Hi Mason You wrote: >> Do you maybe have any hint how to find out what could be the problem >> with the failing configuration of package "rabbitmq-server"? > > try reinstalling rabbitmq-server first, then installing koha-common > > # apt purge rabbitmq-server koha-common > # apt install rabbitmq-server > # apt install koha-common > > > note the 'Status' value when rabbitmq is running correctly > > root@deb11:# systemctl status rabbitmq-server.service > * rabbitmq-server.service - RabbitMQ Messaging Server > Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; > enabled; vendor pre> > Active: active (running) since Thu 2022-08-04 13:21:32 UTC; 2min > 56s ago > Main PID: 5844 (beam.smp) > Status: "Initialized" <<< >Tasks: 86 (limit: 2190) > Memory: 75.3M > CPU: 11.458s > CGroup: /system.slice/rabbitmq-server.service > |-5844 /usr/lib/erlang/erts-11.1.8/bin/beam.smp -W w -K > true -A 64 -MBas> > |-5944 erl_child_setup 65536 > |-5994 inet_gethost 4 > `-5995 inet_gethost 4 > >> >> Did anyone out there successfully install either Koha 21.11.10 or >> Koha 22.05.03 on a new machine with Debian GNU/Linux 11? > > yes, i confirmed that both versions install ok on deb11 I just purged both packages, then tried to install "rabbitmq-server": root@bib-katalog:~# apt install rabbitmq-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: at daemon docbook-xml docbook-xsl fontconfig fonts-dejavu fonts-dejavu-extra gettext graphviz gsfonts icu-devtools idzebra-2.0 idzebra-2.0-common idzebra-2.0-doc idzebra-2.0-utils libalgorithm-c3-perl libalgorithm-checkdigits-perl libann0 libany-uri-escape-perl libanyevent-http-perl libanyevent-perl libapache-logformat-compiler-perl libapache2-mpm-itk libappconfig-perl libarchive-extract-perl libarchive-zip-perl libarray-utils-perl libasync-interrupt-perl libauth-googleauth-perl libauthen-cas-client-perl libb-debug-perl libb-hooks-endofscope-perl libb-hooks-op-check-perl libbarcode-code128-perl libbiblio-endnotestyle-perl libbit-vector-perl libbusiness-isbn-data-perl libbusiness-isbn-perl libbusiness-issn-perl libbytes-random-secure-perl libcache-memcached-fast-perl libcache-memcached-fast-safe-perl libcache-memcached-perl libcairo2 libcapture-tiny-perl libcarp-assert-more-perl libcarp-assert-perl libcarp-clan-perl libcdt5 libcgi-compile-perl libcgi-emulate-psgi-perl libcgi-session-driver-memcached-perl libcgi-session-perl libcgraph6 libclass-accessor-chained-perl libclass-accessor-grouped-perl libclass-accessor-perl libclass-adapter-perl libclass-c3-componentised-perl libclass-c3-perl libclass-c3-xs-perl libclass-data-inheritable-perl libclass-factory-util-perl libclass-inspector-perl libclass-isa-perl libclass-load-perl libclass-load-xs-perl libclass-makemethods-perl libclass-mix-perl libclass-returnvalue-perl libclass-singleton-perl libclass-tiny-perl libclass-unload-perl libclass-xsaccessor-perl libclone-choose-perl libconfig-any-perl libconfig-general-perl libconfig-tiny-perl libcontext-preserve-perl libconvert-base32-perl libconvert-binhex-perl libcookie-baker-perl libcookie-baker-xs-perl libcrypt-cbc-perl libcrypt-eksblowfish-perl libcrypt-jwt-perl libcrypt-random-seed-perl libcrypt-rc4-perl libcrypt-rijndael-perl libcryptx-perl libcurry-perl libdata-dumper-concise-perl libdata-ical-perl libdata-optlist-perl libdata-page-perl libdate-calc-perl libdate-calc-xs-perl libdate-manip-perl libdatetime-event-ical-perl libdatetime-event-recurrence-perl libdatetime-format-builder-perl libdatetime-format-ical-perl libdatetime-format-mail-perl libdatetime-format-mysql-perl libdatetime-format-strptime-perl libdatetime-format-w3cdtf-perl libdatetime-locale-perl libdatetime-perl libdatetime-set-perl libdatetime-timezone-perl libdatrie1 libdbd-mock-perl libdbd-pg-perl libdbd-sqlite3-perl libdbix-class-perl libdbix-class-schema-loader-perl libdbix-runsql-perl libdevel-argnames-perl libdevel-callchecker-perl libdevel-caller-perl libdevel-cover-perl libdevel-globaldestruction-perl libdevel-lexalias-perl libdevel-overloadinfo-perl libdevel-partialdump-perl libdevel-stacktrace-ashtml-perl libdevel-stacktrace-perl libdevel-symdump-perl libdigest-bubblebabble-perl libdigest-perl-md5-perl libdist-checkconflicts-perl libdynaloader-functions-perl libemail-abstract-perl libemail-address-perl libemail-address-xs-perl libemail-date-format-perl libemail-date-perl libemail-messageid-perl libemail-mime-contenttype-perl libemail-mime-encodings-perl libemail-mime-perl libemail-sender-perl libemail-simple-perl libemail-stuffer-perl libeval-closure-perl libevent-2.1-7 libex-monkeypatched-perl libexception-class-perl
Re: [Koha] [Koha-devel] Dependency problem when installing Koha 21.11.10 on Debian 11
s trying "journalctl -xe" to see why the "rabbitmq-server" isn't starting. Once you figure out the problem there and get it fixed, the rest of the package install process should go smoothly. On Wed, Aug 3, 2022 at 8:34 AM Michael Kuhn <mailto:m...@adminkuhn.ch>> wrote: Hi Meanwhile I have also tried to install Koha 22.05.03 (instead of Koha 21.11.10) on a new machine with Debian 11 but it gave me the same error concerning package "rabbitmq-server". Is it really true that it is not possible to install these two revisions on Debian 11? 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 <mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch> Am 03.08.22 um 14:50 schrieb Michael Kuhn: > Hi > > I've just run into problems when trying to install Koha 21.11.10 on a > newly installed machine with Debian GNU/Linux 11. > > 1. This is the content of file "/etc/apt/sources.list.d/koha.list": > > deb http://debian.koha-community.org/koha <http://debian.koha-community.org/koha> 21.11 main > > 2. When starting the installation of Koha "apt-get update" gave: > > OK:1 http://asi-fs-n.contabo.net/debian <http://asi-fs-n.contabo.net/debian> bullseye InRelease > OK:2 http://asi-fs-n.contabo.net/debian <http://asi-fs-n.contabo.net/debian> bullseye-updates InRelease > OK:3 http://security.debian.org/debian-security <http://security.debian.org/debian-security> bullseye-security InRelease > Holen:4 http://debian.koha-community.org/koha <http://debian.koha-community.org/koha> 21.11 InRelease [69,8 kB] > Holen:5 http://debian.koha-community.org/koha <http://debian.koha-community.org/koha> 21.11/main amd64 Packages > [25,6 kB] > Es wurden 95,4 kB in 1 s geholt (93,2 kB/s). > Paketlisten werden gelesen… Fertig > > 2. Unfortunately the installation of Koha ended with the following: > > ... > Fehler traten auf beim Bearbeiten von: > rabbitmq-server > koha-common > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) > > 3. However, now "apt-get update" only gives: > > OK:1 http://asi-fs-n.contabo.net/debian <http://asi-fs-n.contabo.net/debian> bullseye InRelease > OK:2 http://asi-fs-n.contabo.net/debian <http://asi-fs-n.contabo.net/debian> bullseye-updates InRelease > OK:3 http://security.debian.org/debian-security <http://security.debian.org/debian-security> bullseye-security InRelease > OK:4 http://debian.koha-community.org/koha <http://debian.koha-community.org/koha> 21.11 InRelease > Paketlisten werden gelesen… Fertig > > 4. When trying to complete the installation the following errors appear: > > $ sudo apt-get install koha-common > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > koha-common is already the newest version (21.11.10-1). > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 2 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] > Setting up rabbitmq-server (3.8.9-3) ... > Job for rabbitmq-server.service failed because the control process > exited with error code. > See "systemctl status rabbitmq-server.service" and "journalctl -xe" for > details. > invoke-rc.d: initscript rabbitmq-server, action "start" failed. > * rabbitmq-server.service - RabbitMQ Messaging Server > Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; > enabled; vendor preset: enabled) > Active: activating (auto-restart) (Result: exit-code) since Wed > 2022-08-03 14:30:23 CEST; 11ms ago > Process: 3343 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server > (code=exited, status=1/FAILURE) > Main PID: 3343 (code=exited, status=1/FAILURE) > CPU: 5.506s > > Aug 03 14:30:23 bib-katalog.sintiundroma.de <http://bib-katalog.sintiundroma.de> systemd[1]: > rabbitmq-server.service: Failed with result 'exit-code'. > Aug 03 14:30:23 bib-katalog.sintiundroma.de <http://bib-katalog.sintiundroma.de> systemd[1]: Failed to start
Re: [Koha] [Koha-devel] Dependency problem when installing Koha 21.11.10 on Debian 11
Hi Meanwhile I have also tried to install Koha 22.05.03 (instead of Koha 21.11.10) on a new machine with Debian 11 but it gave me the same error concerning package "rabbitmq-server". Is it really true that it is not possible to install these two revisions on Debian 11? 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 03.08.22 um 14:50 schrieb Michael Kuhn: Hi I've just run into problems when trying to install Koha 21.11.10 on a newly installed machine with Debian GNU/Linux 11. 1. This is the content of file "/etc/apt/sources.list.d/koha.list": deb http://debian.koha-community.org/koha 21.11 main 2. When starting the installation of Koha "apt-get update" gave: OK:1 http://asi-fs-n.contabo.net/debian bullseye InRelease OK:2 http://asi-fs-n.contabo.net/debian bullseye-updates InRelease OK:3 http://security.debian.org/debian-security bullseye-security InRelease Holen:4 http://debian.koha-community.org/koha 21.11 InRelease [69,8 kB] Holen:5 http://debian.koha-community.org/koha 21.11/main amd64 Packages [25,6 kB] Es wurden 95,4 kB in 1 s geholt (93,2 kB/s). Paketlisten werden gelesen… Fertig 2. Unfortunately the installation of Koha ended with the following: ... Fehler traten auf beim Bearbeiten von: rabbitmq-server koha-common needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) 3. However, now "apt-get update" only gives: OK:1 http://asi-fs-n.contabo.net/debian bullseye InRelease OK:2 http://asi-fs-n.contabo.net/debian bullseye-updates InRelease OK:3 http://security.debian.org/debian-security bullseye-security InRelease OK:4 http://debian.koha-community.org/koha 21.11 InRelease Paketlisten werden gelesen… Fertig 4. When trying to complete the installation the following errors appear: $ sudo apt-get install koha-common Reading package lists... Done Building dependency tree... Done Reading state information... Done koha-common is already the newest version (21.11.10-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up rabbitmq-server (3.8.9-3) ... Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript rabbitmq-server, action "start" failed. * rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2022-08-03 14:30:23 CEST; 11ms ago Process: 3343 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 3343 (code=exited, status=1/FAILURE) CPU: 5.506s Aug 03 14:30:23 bib-katalog.sintiundroma.de systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. Aug 03 14:30:23 bib-katalog.sintiundroma.de systemd[1]: Failed to start RabbitMQ Messaging Server. Aug 03 14:30:23 bib-katalog.sintiundroma.de systemd[1]: rabbitmq-server.service: Consumed 5.506s CPU time. dpkg: error processing package rabbitmq-server (--configure): installed rabbitmq-server package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of koha-common: koha-common depends on rabbitmq-server; however: Package rabbitmq-server is not configured yet. dpkg: error processing package koha-common (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: rabbitmq-server koha-common E: Sub-process /usr/bin/dpkg returned an error code (1) 5. How can I complete this incomplete installation? 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] Dependency problem when installing Koha 21.11.10 on Debian 11
Hi I've just run into problems when trying to install Koha 21.11.10 on a newly installed machine with Debian GNU/Linux 11. 1. This is the content of file "/etc/apt/sources.list.d/koha.list": deb http://debian.koha-community.org/koha 21.11 main 2. When starting the installation of Koha "apt-get update" gave: OK:1 http://asi-fs-n.contabo.net/debian bullseye InRelease OK:2 http://asi-fs-n.contabo.net/debian bullseye-updates InRelease OK:3 http://security.debian.org/debian-security bullseye-security InRelease Holen:4 http://debian.koha-community.org/koha 21.11 InRelease [69,8 kB] Holen:5 http://debian.koha-community.org/koha 21.11/main amd64 Packages [25,6 kB] Es wurden 95,4 kB in 1 s geholt (93,2 kB/s). Paketlisten werden gelesen… Fertig 2. Unfortunately the installation of Koha ended with the following: ... Fehler traten auf beim Bearbeiten von: rabbitmq-server koha-common needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) 3. However, now "apt-get update" only gives: OK:1 http://asi-fs-n.contabo.net/debian bullseye InRelease OK:2 http://asi-fs-n.contabo.net/debian bullseye-updates InRelease OK:3 http://security.debian.org/debian-security bullseye-security InRelease OK:4 http://debian.koha-community.org/koha 21.11 InRelease Paketlisten werden gelesen… Fertig 4. When trying to complete the installation the following errors appear: $ sudo apt-get install koha-common Reading package lists... Done Building dependency tree... Done Reading state information... Done koha-common is already the newest version (21.11.10-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up rabbitmq-server (3.8.9-3) ... Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript rabbitmq-server, action "start" failed. * rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2022-08-03 14:30:23 CEST; 11ms ago Process: 3343 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 3343 (code=exited, status=1/FAILURE) CPU: 5.506s Aug 03 14:30:23 bib-katalog.sintiundroma.de systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. Aug 03 14:30:23 bib-katalog.sintiundroma.de systemd[1]: Failed to start RabbitMQ Messaging Server. Aug 03 14:30:23 bib-katalog.sintiundroma.de systemd[1]: rabbitmq-server.service: Consumed 5.506s CPU time. dpkg: error processing package rabbitmq-server (--configure): installed rabbitmq-server package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of koha-common: koha-common depends on rabbitmq-server; however: Package rabbitmq-server is not configured yet. dpkg: error processing package koha-common (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: rabbitmq-server koha-common E: Sub-process /usr/bin/dpkg returned an error code (1) 5. How can I complete this incomplete installation? 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] Sharing library data with others via z30.50
Hi Noor You wrote: > Can I share my books data in koha with others via Z39.50 for copy > catalogue. > > If yes how? Just see: https://wiki.koha-community.org/wiki/Setting_up_the_Z39.50_and_SRU_Server Fred King has made a short video to show how to do it: https://www.youtube.com/watch?v=j_XOKvq8_TI Hope this helps. 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] Adding items to a list not possible in Koha 21.11.09
Hi Arturo You wrote: > Another tip for troubleshooting in case you haven't tried it - Bug > 14004 added the ability to disable both custom CSS and JS by appending > some parameters to your staff client's URL. This would let you load > these pages without also loading your library's custom CSS and > JavaScript, so that you can more definitively rule out that it isn't > a local issue. Thanks for the tip! But in the actual case there is no custom CSS or Javascript existing. > You'd add ?DISABLE_SYSPREF_IntranetUserJS=1_SYSPREF_IntranetUserCSS=1 to the end of your URL. For example, > if your staff client is accessed at http://www.mylibraryisthebest.com, > you'd load http://www.mylibraryisthebest.com/?DISABLE_SYSPREF_IntranetUserJS=1_SYSPREF_IntranetUserCSS=1 so that it does not load your CSS and JS. > > Just a thought for some further troubleshooting. > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14004 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] Adding items to a list not possible in Koha 21.11.09
Hi George > Could you please share some screenshots ? to give me a try to > replicate that ? 1. Perform a search and check an item on the first page * http://adminkuhn.ch/download/list-1.png 2. Click on "Add to list" and select a list, the message "No item was selected" appears * http://adminkuhn.ch/download/list-2.png 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 -Original Message- From: Michael Kuhn Sent: Wednesday, July 27, 2022 10:34 AM To: gvera...@dataly.gr; 'Andreas Roussos' ; 'Koha' Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 Hi George > Do you try to add items by barcode or by itemnumber ? I search for anything that gives me a result list. In this list (on the first page) I check one ore more items on the left side, then try to add it/them to an existing list. But Koha says "No item was selected" and doesn't add the item(s) to the list. 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 Do you try to add items by barcode or by itemnumber ? Best Regards, George Veranis -Original Message- From: Koha On Behalf Of Michael Kuhn Sent: Tuesday, July 26, 2022 7:32 PM To: Andreas Roussos ; Koha Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 Hello Andreas > Thank you very much for taking the time to provide these details! > > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? No customisations. > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. > Have you tried adding a record to a list using a different browser? I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". > Does anything helpful get printed in your browser's console? > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") Just after the search the following is written into the browser console: sendRemoveListener on closed conduit text...@jlebon.com.3985729651140 ConduitsChild.jsm:108 _send resource://gre/modules/ConduitsChild.jsm:108 _send self-hosted:1282 removeListener resource://gre/modules/ExtensionChild.jsm:663 removeListener resource://gre/modules/ExtensionChild.jsm:886 onChanged chrome://extensions/content/child/ext-storage.js:332 removeListener resource://gre/modules/ExtensionCommon.jsm:2534 revoke resource://gre/modules/ExtensionCommon.jsm:2556 close resource://gre/modules/ExtensionCommon.jsm:2561 unload resource://gre/modules/ExtensionCommon.jsm:922 close resource://gre/modules/ExtensionContent.jsm:934 destroyed resource://gre/modules/ExtensionContent.jsm:1012 observe resource://gre/modules/ExtensionContent.jsm:1030 But there is no further message when actually trying to add the checked record to the list. > Have you had any Koha plugins installed or enabled recently? No, there are no Koha plugins installed on this host. As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... 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 2022-07-25 10:40, Michael Kuhn wrote: Hi Andreas You wrote: > I've tried to reproduce the issue you describe on a development > 21.11.09 instance that I set up, but was not successful. > > So, I have a few questions for you to help me diagnose this ;-) > > Assuming a package installation, have you restarted the koha-com
Re: [Koha] Adding items to a list not possible in Koha 21.11.09
Hi George > Do you try to add items by barcode or by itemnumber ? I search for anything that gives me a result list. In this list (on the first page) I check one ore more items on the left side, then try to add it/them to an existing list. But Koha says "No item was selected" and doesn't add the item(s) to the list. 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 Do you try to add items by barcode or by itemnumber ? Best Regards, George Veranis -Original Message- From: Koha On Behalf Of Michael Kuhn Sent: Tuesday, July 26, 2022 7:32 PM To: Andreas Roussos ; Koha Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 Hello Andreas > Thank you very much for taking the time to provide these details! > > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? No customisations. > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. > Have you tried adding a record to a list using a different browser? I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". > Does anything helpful get printed in your browser's console? > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") Just after the search the following is written into the browser console: sendRemoveListener on closed conduit text...@jlebon.com.3985729651140 ConduitsChild.jsm:108 _send resource://gre/modules/ConduitsChild.jsm:108 _send self-hosted:1282 removeListener resource://gre/modules/ExtensionChild.jsm:663 removeListener resource://gre/modules/ExtensionChild.jsm:886 onChanged chrome://extensions/content/child/ext-storage.js:332 removeListener resource://gre/modules/ExtensionCommon.jsm:2534 revoke resource://gre/modules/ExtensionCommon.jsm:2556 close resource://gre/modules/ExtensionCommon.jsm:2561 unload resource://gre/modules/ExtensionCommon.jsm:922 close resource://gre/modules/ExtensionContent.jsm:934 destroyed resource://gre/modules/ExtensionContent.jsm:1012 observe resource://gre/modules/ExtensionContent.jsm:1030 But there is no further message when actually trying to add the checked record to the list. > Have you had any Koha plugins installed or enabled recently? No, there are no Koha plugins installed on this host. As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... 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 2022-07-25 10:40, Michael Kuhn wrote: Hi Andreas You wrote: > I've tried to reproduce the issue you describe on a development > 21.11.09 instance that I set up, but was not successful. > > So, I have a few questions for you to help me diagnose this ;-) > > Assuming a package installation, have you restarted the koha-common > service following the upgrade? Yes, we have. We have also restarted the complete host. > Have you performed a hard refresh of your web browser's cache? (hit > CTRL-F5) Yes, we did. > Finally, which version of Koha did you upgrade from? We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. 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 mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Adding items to a list not possible in Koha 21.11.09
Hello Andreas > Thank you very much for taking the time to provide these details! > > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? No customisations. > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. > Have you tried adding a record to a list using a different browser? I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". > Does anything helpful get printed in your browser's console? > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") Just after the search the following is written into the browser console: sendRemoveListener on closed conduit text...@jlebon.com.3985729651140 ConduitsChild.jsm:108 _send resource://gre/modules/ConduitsChild.jsm:108 _send self-hosted:1282 removeListener resource://gre/modules/ExtensionChild.jsm:663 removeListener resource://gre/modules/ExtensionChild.jsm:886 onChanged chrome://extensions/content/child/ext-storage.js:332 removeListener resource://gre/modules/ExtensionCommon.jsm:2534 revoke resource://gre/modules/ExtensionCommon.jsm:2556 close resource://gre/modules/ExtensionCommon.jsm:2561 unload resource://gre/modules/ExtensionCommon.jsm:922 close resource://gre/modules/ExtensionContent.jsm:934 destroyed resource://gre/modules/ExtensionContent.jsm:1012 observe resource://gre/modules/ExtensionContent.jsm:1030 But there is no further message when actually trying to add the checked record to the list. > Have you had any Koha plugins installed or enabled recently? No, there are no Koha plugins installed on this host. As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... 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 2022-07-25 10:40, Michael Kuhn wrote: Hi Andreas You wrote: > I've tried to reproduce the issue you describe on a development > 21.11.09 instance that I set up, but was not successful. > > So, I have a few questions for you to help me diagnose this ;-) > > Assuming a package installation, have you restarted the koha-common > service following the upgrade? Yes, we have. We have also restarted the complete host. > Have you performed a hard refresh of your web browser's cache? (hit > CTRL-F5) Yes, we did. > Finally, which version of Koha did you upgrade from? We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. Best wishes: Michael ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Accessing DNB databases via SRU and HTTPS
Hi Anke Thank you very much! You wrote: > our config still works well - see screenshot. We have exactly the same configuration - but when trying to access we are getting the following error message: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server I tested the same configuration on my demo installation https://koha.adminkuhn.ch - there it works well. The demo installation is directly in the internet with no (outgoing) firewalls involved. > Changing 80 to 443 doesn't help - the SRU search doesn't work anymore > with that setting. Changing 80 to 443 didn't help either on my demo installation. Thus I think this is a problem of the local firewall of our library that doesn't like the redirect from port 80 to 443. It will have to be solved locally. 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] Accessing DNB databases via SRU and HTTPS
Hi We had a working Koha configuration to access the database of the German national library (Deutsche Nationalbibliothek / DNB) via SRU and HTTP. But since 19 July requests using the HTTP-protocol will be redirected to the HTTPS-protocol by "HTTP-Statuscode 301 Moved Permanently" (see https://lists.dnb.de/pipermail/ons-sru-ru/2022-July/15.html). The search via HTTPS is working via yaz-client: # yaz-client https://services.dnb.de/sru/dnb Z> sru GET 1.1 Z> find "Marx" Z> s 1 So in our Koha configuration we changed port 80 to port 443 - but when searching anything Koha immediately (apparently without really searching) returns "Nothing found". It's is the same with both databases "sru/dnb" (bibliographic data) and "sru/authorities" (authorities). Has anyone been successful recently when trying to access the DNB databases via SRU and HTTPS? 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] Adding items to a list not possible in Koha 21.11.09
Hi Andreas You wrote: > I've tried to reproduce the issue you describe on a development > 21.11.09 instance that I set up, but was not successful. > > So, I have a few questions for you to help me diagnose this ;-) > > Assuming a package installation, have you restarted the koha-common > service following the upgrade? Yes, we have. We have also restarted the complete host. > Have you performed a hard refresh of your web browser's cache? (hit > CTRL-F5) Yes, we did. > Finally, which version of Koha did you upgrade from? We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. 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] Adding items to a list not possible in Koha 21.11.09
Hi Marcel Are you maybe talking about Bug 30925 (Creating public list by adding items to new list creates a private list)? System preference "OpacAllowPublicListCreation" was already set to "Allow". I changed files "addbybiblionumber.tt" and "opac-addbybiblionumber.tt" according to https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=136373=diff - I even restarted the full host. It didn't change the behaviour in Koha 21.11.09. This it is not possible anymore to add items to lists. 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 19.07.22 um 15:25 schrieb Marcel de Rooy: Sounds like a bug I recently resolved. Check Bugzilla. -------- *Van:* Koha namens Michael Kuhn *Verzonden:* dinsdag 19 juli 2022 15:13 *Aan:* Koha *Onderwerp:* [Koha] Adding items to a list not possible in Koha 21.11.09 Hi Recently we updated to Koha 21.11.09. Now in the staff client when selecting one or more items in a result list and trying to add it to a list by clicking "Add to list", then selecting the respective list, Koha says "No item was selected". Which is of course not true. However it is not possible to add any items from a result list to "Your lists" or "Public lists". Is this a bug or does anyone know the reason for this behaviour? Maybe there is some connection to bug https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2Fbugzilla3%2Fshow_bug.cgi%3Fid%3D24522data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=5xd%2BUXz6rMh3jqpRH28UoSOt5NyiL7w5bz9Sgugf0ws%3Dreserved=0 <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2Fbugzilla3%2Fshow_bug.cgi%3Fid%3D24522data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=5xd%2BUXz6rMh3jqpRH28UoSOt5NyiL7w5bz9Sgugf0ws%3Dreserved=0> (Nothing happens when trying to add nothing to a list in staff) 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 https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=j%2FZYs4eilzQZXFp%2Fe6fmzouPLBvS9kdw7qOx71hmH2k%3Dreserved=0 <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=j%2FZYs4eilzQZXFp%2Fe6fmzouPLBvS9kdw7qOx71hmH2k%3Dreserved=0> ___ Koha mailing list https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=t4YI4miSfzY0f6im89q6g3GB6Zv1jcGtsgS8GEBYylc%3Dreserved=0 <https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2Fdata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=t4YI4miSfzY0f6im89q6g3GB6Zv1jcGtsgS8GEBYylc%3Dreserved=0> Koha@lists.katipo.co.nz Unsubscribe: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkohadata=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=eaV4pr%2BN0y1RAuwrWH%2FYiV9tA7qKGv7TqxOtbmlv7Xw%3Dreserved=0 <https://eur03.safelinks.protection.outlook.com/?url=
[Koha] Adding items to a list not possible in Koha 21.11.09
Hi Recently we updated to Koha 21.11.09. Now in the staff client when selecting one or more items in a result list and trying to add it to a list by clicking "Add to list", then selecting the respective list, Koha says "No item was selected". Which is of course not true. However it is not possible to add any items from a result list to "Your lists" or "Public lists". Is this a bug or does anyone know the reason for this behaviour? Maybe there is some connection to bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24522 (Nothing happens when trying to add nothing to a list in staff) 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] Failing authentication via CAS after update to Koha 21.11.09
Hi Katrin Meanwhile I was able to login into Koha using casServerUrl https://casserver.herokuapp.com/cas and CAS/Koha-User "casuser" (which I first had to create) on my Koha 22.05.00 demo site as well as on the productive Koha 21.11.09 installation. But the login using the original casServerUrl still doesn't work. So for the moment I think there is a problem with the original CAS-Server. Best wishes and thanks for your support! 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 18.07.22 um 12:48 schrieb Katrin Fischer: Hi Michael, sorry, it was probably a glitch with the local login, I now also see the "Sorry, the CAS login failed." message and the login doesn't work :( But the login link now appeared. Katrin On 18.07.22 12:34, Katrin Fischer wrote: Hi Michael, I have tried to set it up in your demo, hope you don't mind! You also need a user with username casuser, but the problem I am seeing is that the login link doesn't show in the OPAC in the first place. Only the heading. So there is some problem there for sure. But: If I log in on the website and then refresh the login page in Koha, I am logged in successfully. Hope this helps, Katrin On 18.07.22 12:25, Michael Kuhn wrote: Hi Katrin You wrote: > do you have user information for this CAS server? I didn't find any > sample login yet. Can you log in using the URL directly in the > browser? Yes, the URL and the login (casuser / Mellon) for the demo sites can be found at https://apereo.github.io/cas/Demos.html Logging in at https://casserver.herokuapp.com/cas using these credentials is successful. It's just Koha that won't accept it. 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 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] Failing authentication via CAS after update to Koha 21.11.09
Hi Katrin
You wrote:
> do you have user information for this CAS server? I didn't find any
> sample login yet. Can you log in using the URL directly in the
> browser?
Yes, the URL and the login (casuser / Mellon) for the demo sites can be
found at https://apereo.github.io/cas/Demos.html
Logging in at https://casserver.herokuapp.com/cas using these
credentials is successful. It's just Koha that won't accept 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
On 18.07.22 12:03, Michael Kuhn wrote:
Hi Tomas
I saw I was using the wrong URL to the Apereo XAS demo site - instead
of "https://apereo.github.io/cas/; it is actually
"https://casserver.herokuapp.com/cas;. So I tried anew using this URL
but still the CAS login into Koha fails ("Sorry, the CAS login failed.").
I also tried this URL on my Koha demo site using 22.05.00 but the
login doesn't work either.
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 mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Failing authentication via CAS after update to Koha 21.11.09
Hi Tomas
I saw I was using the wrong URL to the Apereo XAS demo site - instead of
"https://apereo.github.io/cas/; it is actually
"https://casserver.herokuapp.com/cas;. So I tried anew using this URL
but still the CAS login into Koha fails ("Sorry, the CAS login failed.").
I also tried this URL on my Koha demo site using 22.05.00 but the login
doesn't work either.
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 18.07.22 um 11:22 schrieb Michael Kuhn:
Hi Tomas
You wrote:
> Are you sure the CAS server is functional?
Yes, when clicking "Log in using a CAS account" the login dialogue of
the CAS server appears, after logging in it can be proven that the login
there was successful.
But the Koha OPAC seems to think the login failed and it says "Sorry,
the CAS login failed." This seems to happen because Koha script
"Auth.pm" returns 1 for "invalidCasLogin" but I can't find out why.
> Can you try pointing your Koha or a replica to the Apereo XAS demo
> sites?
I found https://apereo.github.io/cas/index.html and I changed
"casServerUrl" to "https://apereo.github.io/cas/; but when I click "Log
in using a CAS account" there is a message "404 File not found" instead
of showing me a the CAS server dialogue.
> For debugging, you should use
>
> warn "$variable";
>
> And look for those warns in the usual logs. Remember to restart plack
> everytime you change the code.
This worked but due to my limited knowledge of Perl and the Koha
authentication process via CAS it didn't help me further...
Can maybe someone confirm that the CAS server login actually works with
Koha 21.11.09? As said we didn't change the CAS configuration since Koha
19.05.02.
Best wishes: Michael
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Failing authentication via CAS after update to Koha 21.11.09
Hi Tomas
You wrote:
> Are you sure the CAS server is functional?
Yes, when clicking "Log in using a CAS account" the login dialogue of
the CAS server appears, after logging in it can be proven that the login
there was successful.
But the Koha OPAC seems to think the login failed and it says "Sorry,
the CAS login failed." This seems to happen because Koha script
"Auth.pm" returns 1 for "invalidCasLogin" but I can't find out why.
> Can you try pointing your Koha or a replica to the Apereo XAS demo
> sites?
I found https://apereo.github.io/cas/index.html and I changed
"casServerUrl" to "https://apereo.github.io/cas/; but when I click "Log
in using a CAS account" there is a message "404 File not found" instead
of showing me a the CAS server dialogue.
> For debugging, you should use
>
> warn "$variable";
>
> And look for those warns in the usual logs. Remember to restart plack
> everytime you change the code.
This worked but due to my limited knowledge of Perl and the Koha
authentication process via CAS it didn't help me further...
Can maybe someone confirm that the CAS server login actually works with
Koha 21.11.09? As said we didn't change the CAS configuration since Koha
19.05.02.
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
El lun, 11 jul 2022 8:41, Michael Kuhn <mailto:m...@adminkuhn.ch>> escribió:
Hi
We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update
from Debian 9 and Koha 19.05.02).
Since the update the CAS authentication via Koha OPAC is no more
working. The content of system preferences "OPACBaseURL",
"casAuthentication", "casLogout" and "casServerUrl" has not changed;
the
new preference "casServerVersion" ist correctly set to "CAS 2 or
earlier".
It is possible to successfully log into the CAS server but when trying
to access the Koha OPAC via CAS ("Log in using a CAS account") the
response is always "Sorry, the CAS login failed." and the user is not
logged into his Koha account. The logs don't show no error.
I was checking all changes made in bugs 21973 22585 23771 20854 and
28417 but to no avail.
Does anyone have an idea how to debug this problem?
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
<mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch>
___
Koha mailing list http://koha-community.org <http://koha-community.org>
Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
<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] Lock a Certain field
Hi Himanshu > Is there a way to restrict editing of Date by catalogers The following article by Kelly McElligott (Bywater Solutions) may answer your question: * https://bywatersolutions.com/education/monday-minutes-protecting-marc-fields Hope this helps. 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] Failing authentication via CAS after update to Koha 21.11.09
Hi
We're quite desperate since using CAS all our users can no more log into
their Koha accounts. Is there really no way how to debug problems with
the authentication via CAS?
We would be very happy if there is a way how to find out what Perl
scripts "opac-user.pl" or "Auth_with_cas.pm" are really doing.
Unfortunately they are not verbose at all and don't write anything into
the log files. Is it possible to force these scripts to output what they
are actually doing?
For example I tried the following in "Auth_with_cas.pm", but file
"/tmp/perloutput.txt" stayed empty.
open STDERR, ">", "/tmp/perloutput.txt" or die "$0: dup: $!";
print STDERR "defaultcasserver: $defaultcasserver\n";
print STDERR "casservers: $casservers\n";
close (STDERR);
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
Weitergeleitete Nachricht
Betreff: [Koha] Failing authentication via CAS after update to Koha 21.11.09
Datum: Mon, 11 Jul 2022 13:41:03 +0200
Von: Michael Kuhn
Antwort an: Michael Kuhn
Organisation: Admin Kuhn GmbH
An: Koha
Hi
We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update
from Debian 9 and Koha 19.05.02).
Since the update the CAS authentication via Koha OPAC is no more
working. The content of system preferences "OPACBaseURL",
"casAuthentication", "casLogout" and "casServerUrl" has not changed; the
new preference "casServerVersion" ist correctly set to "CAS 2 or earlier".
It is possible to successfully log into the CAS server but when trying
to access the Koha OPAC via CAS ("Log in using a CAS account") the
response is always "Sorry, the CAS login failed." and the user is not
logged into his Koha account. The logs don't show no error.
I was checking all changes made in bugs 21973 22585 23771 20854 and
28417 but to no avail.
Does anyone have an idea how to debug this problem?
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] Call for news - Newsletter July 2022
Hi I'm collecting news for the July 2022 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 -- 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] Failing authentication via CAS after update to Koha 21.11.09
Hi
We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update
from Debian 9 and Koha 19.05.02).
Since the update the CAS authentication via Koha OPAC is no more
working. The content of system preferences "OPACBaseURL",
"casAuthentication", "casLogout" and "casServerUrl" has not changed; the
new preference "casServerVersion" ist correctly set to "CAS 2 or earlier".
It is possible to successfully log into the CAS server but when trying
to access the Koha OPAC via CAS ("Log in using a CAS account") the
response is always "Sorry, the CAS login failed." and the user is not
logged into his Koha account. The logs don't show no error.
I was checking all changes made in bugs 21973 22585 23771 20854 and
28417 but to no avail.
Does anyone have an idea how to debug this problem?
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] System preference "AutoRenewalNotices"
Hi Meanwhile it turned out there is another (but no more used) Koha instance on the same host. Since the mentioned e-mail is not referring to any specific instance or database I have now also set system preference "AutoRenewalNotices" to "never" in this other instance, hoping this will cure the hiccup. 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 27.06.22 um 12:44 schrieb Michael Kuhn: Hi After updating to Koha 21.11.06 the system is sending us the following e-mail every day: ### START ### /etc/cron.daily/koha-common: The "AutoRenewalNotices" syspref is set to 'Follow the cron switch'. The send_notices switch for this script is deprecated, you should either set the preference to 'Never send emails' or 'Follow patron messaging preferences' The "EnhancedMessagingPreferences" syspref is off. Therefore, it is unlikely that this script will actually produce any messages to be sent. To change this, edit the "EnhancedMessagingPreferences" syspref. ### END ### In fact we have already set the value of system preference "AutoRenewalNotices" to "never" after the first such e-mail: select variable, value from systempreferences where variable="AutoRenewalNotices"; ++---+ | variable | value | ++---+ | AutoRenewalNotices | never | ++---+ Also, in fact system preference "EnhancedMessagingPreferences" is on (not off): select variable, value from systempreferences where variable="EnhancedMessagingPreferences"; +--+---+ | variable | value | +--+---+ | EnhancedMessagingPreferences | 1 | +--+---+ How can we get rid of these annoying e-mails? 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] System preference "AutoRenewalNotices"
Hi After updating to Koha 21.11.06 the system is sending us the following e-mail every day: ### START ### /etc/cron.daily/koha-common: The "AutoRenewalNotices" syspref is set to 'Follow the cron switch'. The send_notices switch for this script is deprecated, you should either set the preference to 'Never send emails' or 'Follow patron messaging preferences' The "EnhancedMessagingPreferences" syspref is off. Therefore, it is unlikely that this script will actually produce any messages to be sent. To change this, edit the "EnhancedMessagingPreferences" syspref. ### END ### In fact we have already set the value of system preference "AutoRenewalNotices" to "never" after the first such e-mail: select variable, value from systempreferences where variable="AutoRenewalNotices"; ++---+ | variable | value | ++---+ | AutoRenewalNotices | never | ++---+ Also, in fact system preference "EnhancedMessagingPreferences" is on (not off): select variable, value from systempreferences where variable="EnhancedMessagingPreferences"; +--+---+ | variable | value | +--+---+ | EnhancedMessagingPreferences | 1 | +--+---+ How can we get rid of these annoying e-mails? 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] Background jobs in Koha menu "Administration"
Hi Christopher Thanks for your meesage. You wrote: > With just a cursory look, I would assume something like 1/1 means 1 > job, 1 completed. Something like 2/1 would mean 2 jobs, 1 completed. > 0/0, I would assume, means there are no jobs. Yes this is also our assumption - but we ask ourselves if there is no job, why is there a line at all saying there is no job?! The library is afraid that maybe something went wrong in such a case. As said, unfortunately clicking the button "View" does not show more information like WHAT biblio or item exactly the job is referring to. 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 Message: 5 Date: Mon, 20 Jun 2022 14:48:02 +0200 From: Michael Kuhn To: Koha Subject: [Koha] Background jobs in Koha menu "Administration" Message-ID: Content-Type: text/plain; charset=UTF-8; format=flowed Hi We saw in Koha 22.05 there is a new Koha menu "Administration > Manage background jobs". Unfortunately there seems to be no entry in the Koha manual 22.05 for it, also the context-sensitive help just leads to https://koha-community.org/manual//21.11/en/html/ (this is in an installation of Koha 22.05!). However the shown list has a column "progress" which can say "1/1" or "0/0" for example. What does ist mean? Library personnel thinks "0/0" suggests that something went wrong even if column "Status" says "Finished". Unfortunately clicking the button "View" does not show more information like WHAT biblio or item exactly the entry is referring to. We saw that Bywater Solutions wrote an article about this new menu ( https://bywatersolutions.com/education/koha-21-11-background-jobs-and-task-queue-enhancements ) but our question is not answered there. Can someone please enlighten us what "0/0" means? 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 mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Background jobs in Koha menu "Administration"
Hi We saw in Koha 22.05 there is a new Koha menu "Administration > Manage background jobs". Unfortunately there seems to be no entry in the Koha manual 22.05 for it, also the context-sensitive help just leads to https://koha-community.org/manual//21.11/en/html/ (this is in an installation of Koha 22.05!). However the shown list has a column "progress" which can say "1/1" or "0/0" for example. What does ist mean? Library personnel thinks "0/0" suggests that something went wrong even if column "Status" says "Finished". Unfortunately clicking the button "View" does not show more information like WHAT biblio or item exactly the entry is referring to. We saw that Bywater Solutions wrote an article about this new menu ( https://bywatersolutions.com/education/koha-21-11-background-jobs-and-task-queue-enhancements ) but our question is not answered there. Can someone please enlighten us what "0/0" means? 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] Roadbump in installing system
Hi C. S. You wrote: > I want to install Koha on a public server, and I came across a minor > roadbump in following the wiki instructions: > > wget -q -O- https://debian.koha-community.org/koha/gpg.asc | sudo apt- > key add - > > gives output of: > > gpg: no valid OpenPGP data found. > > Is this appropriate and to be expected? If not, what should I do? Try to omit the "-q". I usually use: wget -O- http://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - Maybe you're behind a proxy? Hope this helps. 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] Plack error after update to Koha 21.11.06
Hi Fridolin Today you wrote: > What is your line for Koha packages in apt config please ? > > What says "dpkg -l koha*" ? Thanks for your message! As I wrote in my third e-mail regarding this case (see below) the problem is already solved. 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 Weitergeleitete Nachricht Betreff: Re: [Koha] Plack error after update to Koha 21.11.06 Datum: Fri, 10 Jun 2022 18:54:39 +0200 Von: Michael Kuhn Antwort an: Michael Kuhn Organisation: Admin Kuhn GmbH An: koha@lists.katipo.co.nz Hi As I found out the needed packages "libjson-validator-perl" and "libmojolicious-plugin-openapi-perl" do not come with Debian GNU/Linux 10 but as dependencies for package "koha-common". For some reason they were not installed during the installation of package "koha-common". However I was now able to install them and our problem is solved; Plack is running. 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 10.06.22 um 14:30 schrieb Michael Kuhn: > Hi > > As I just saw Koha menu "About Koha > Perl moules" says the following > modules are not installed: > > * JSON::Validator 3.14 > * Mojolicious::Plugin::OpenAPI 2.16 > > But Debian GNU/Linux 10 says: > > # apt-cache policy libjson-validator-perl > libjson-validator-perl: >Installed: 3.06+dfsg-1 >Candidate: 3.06+dfsg-1 >Version table: > *** 3.06+dfsg-1 500 > 500 http://deb.debian.org/debian buster/main amd64 Packages > 100 /var/lib/dpkg/status > > # apt-cache policy libmojolicious-plugin-openapi-perl > libmojolicious-plugin-openapi-perl: >Installed: 1.15-1~kohadev1 >Candidate: 1.15-1~kohadev1 >Version table: > *** 1.15-1~kohadev1 100 > 100 /var/lib/dpkg/status > > As said this is a Debian package installation. So how should we proceed > to install the needed version of the missing modules? > > 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 mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Plack error after update to Koha 21.11.06
Hi As I found out the needed packages "libjson-validator-perl" and "libmojolicious-plugin-openapi-perl" do not come with Debian GNU/Linux 10 but as dependencies for package "koha-common". For some reason they were not installed during the installation of package "koha-common". However I was now able to install them and our problem is solved; Plack is running. 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 10.06.22 um 14:30 schrieb Michael Kuhn: Hi As I just saw Koha menu "About Koha > Perl moules" says the following modules are not installed: * JSON::Validator 3.14 * Mojolicious::Plugin::OpenAPI 2.16 But Debian GNU/Linux 10 says: # apt-cache policy libjson-validator-perl libjson-validator-perl: Installed: 3.06+dfsg-1 Candidate: 3.06+dfsg-1 Version table: *** 3.06+dfsg-1 500 500 http://deb.debian.org/debian buster/main amd64 Packages 100 /var/lib/dpkg/status # apt-cache policy libmojolicious-plugin-openapi-perl libmojolicious-plugin-openapi-perl: Installed: 1.15-1~kohadev1 Candidate: 1.15-1~kohadev1 Version table: *** 1.15-1~kohadev1 100 100 /var/lib/dpkg/status As said this is a Debian package installation. So how should we proceed to install the needed version of the missing modules? Best wishes: Michael ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Plack error after update to Koha 21.11.06
Hi As I just saw Koha menu "About Koha > Perl moules" says the following modules are not installed: * JSON::Validator 3.14 * Mojolicious::Plugin::OpenAPI 2.16 But Debian GNU/Linux 10 says: # apt-cache policy libjson-validator-perl libjson-validator-perl: Installed: 3.06+dfsg-1 Candidate: 3.06+dfsg-1 Version table: *** 3.06+dfsg-1 500 500 http://deb.debian.org/debian buster/main amd64 Packages 100 /var/lib/dpkg/status # apt-cache policy libmojolicious-plugin-openapi-perl libmojolicious-plugin-openapi-perl: Installed: 1.15-1~kohadev1 Candidate: 1.15-1~kohadev1 Version table: *** 1.15-1~kohadev1 100 100 /var/lib/dpkg/status As said this is a Debian package installation. So how should we proceed to install the needed version of the missing modules? 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 10.06.22 um 14:17 schrieb Michael Kuhn: Hi We were updating from Debian GNU/Linux 9 to 10, then from Koha 20.11.03 to Koha 21.11.06. This is a Debian package installation. Now Plack throws many error messages like the following in file "/var/log/koha/plack-error.log": Error while loading /etc/koha/plack.psgi: Can't load application from file "/usr/share/koha/api/v1/app.pl": Can't locate JSON/Validator/OpenAPI/Mojolicious.pm in @INC (you may need to install the JSON::Validator::OpenAPI::Mojolicious module) (@INC contains: /usr/share/koha/lib /usr/share/koha/installer /usr/share/koha/lib/installer /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base /var/lib/koha/whu/plugins) at /usr/share/koha/lib/Koha/REST/V1.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/Koha/REST/V1.pm line 25. Compilation failed in require at (eval 507) line 1. Compilation failed in require at (eval 506) line 1. Child process 21538 exited with status 255 I see there is bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi concerning this problem but there doesn't seem to be a solution for our case. On our Debian GNU/Linux 10 system package "libjson-validator-perl" is the newest version (3.06+dfsg-1). Does anyone know how to solve this problem? 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] Plack error after update to Koha 21.11.06
Hi We were updating from Debian GNU/Linux 9 to 10, then from Koha 20.11.03 to Koha 21.11.06. This is a Debian package installation. Now Plack throws many error messages like the following in file "/var/log/koha/plack-error.log": Error while loading /etc/koha/plack.psgi: Can't load application from file "/usr/share/koha/api/v1/app.pl": Can't locate JSON/Validator/OpenAPI/Mojolicious.pm in @INC (you may need to install the JSON::Validator::OpenAPI::Mojolicious module) (@INC contains: /usr/share/koha/lib /usr/share/koha/installer /usr/share/koha/lib/installer /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base /var/lib/koha/whu/plugins) at /usr/share/koha/lib/Koha/REST/V1.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/Koha/REST/V1.pm line 25. Compilation failed in require at (eval 507) line 1. Compilation failed in require at (eval 506) line 1. Child process 21538 exited with status 255 I see there is bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi concerning this problem but there doesn't seem to be a solution for our case. On our Debian GNU/Linux 10 system package "libjson-validator-perl" is the newest version (3.06+dfsg-1). Does anyone know how to solve this problem? 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] Koha 22.05 on Ubuntu 22.04?
Hi Isabel You wrote: > Does Koha 22.05 support Ubuntu 22.04? In the system requirements I can > see that it goes only from Ubuntu version 18.04 to 21.10. According to https://wiki.koha-community.org/wiki/System_requirements_and_recommendations#Koha_22.05 Ubuntu 22.04 is not one of officially supported operating systems yet. Hope this helps. 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] [Koha-devel] Getting Koha 19.11 web installer when installing Koha 20.11.19
Hi Mason You wrote: > oops, sorry about that > > you can run the following commands to fix the problem... > > $ sudo apt-get update > $ sudo apt-get upgrade koha-common > > $ sudo apt-cache show koha-common | grep Version > Version: 20.11.19-3 Unfortunatley it didn't work to just update and the upgrade package "koha-common" - instead hundreds of error messages regarding the database etc appeared. Thus I rebuilt the complete machine from scratch, using the new package. This worked. Thank you very much! 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 4/06/22 4:56 am, Michael Kuhn wrote: Hi Today I was installing Koha 20.11.19 on a completely new virtual host using Debian 11. $ sudo cat /etc/apt/sources.list.d/koha.list deb http://debian.koha-community.org/koha 20.11 main $ sudo apt-get update $ sudo apt-cache show koha-common | grep Version Version: 20.11.19-1 $ sudo apt-get install koha-common mariadb-server In the output I see lines like: Get:16 http://debian.koha-community.org/koha 20.11/main amd64 libcache-memcached-fast-safe-perl all 0.06-1~koha1 [7,410 B] Get:22 http://debian.koha-community.org/koha 20.11/main amd64 libhttp-oai-3.27-perl all 3.27-1~koha+1 [92.7 kB] Get:16 http://debian.koha-community.org/koha 20.11/main amd64 libcache-memcached-fast-safe-perl all 0.06-1~koha1 [7,410 B] Get:22 http://debian.koha-community.org/koha 20.11/main amd64 libhttp-oai-3.27-perl all 3.27-1~koha+1 [92.7 kB] Get:36 http://debian.koha-community.org/koha 20.11/main amd64 libmojolicious-perl all 9.90+really8.12-koha1 [794 kB] Get:75 http://debian.koha-community.org/koha 20.11/main amd64 libjson-validator-perl all 5.99+really3.14-koha1 [54.2 kB] Get:85 http://debian.koha-community.org/koha 20.11/main amd64 libmojolicious-plugin-openapi-perl all 5.99+really2.16-koha1 [57.1 kB] Get:88 http://debian.koha-community.org/koha 20.11/main amd64 libpdf-fromhtml-perl all 0.31-1~koha1 [102 kB] Get:98 http://debian.koha-community.org/koha 20.11/main amd64 libtemplate-plugin-htmltotext-perl all 0.03-1koha1 [6,134 B] Get:99 http://debian.koha-community.org/koha 20.11/main amd64 koha-common all 20.11.19-1 [34.5 MB] Preparing to unpack .../523-koha-common_20.11.19-1_all.deb ... Unpacking koha-common (20.11.19-1) ... Setting up koha-common (20.11.19-1) ... However after the installation when calling the web installer it annoyingly greets me saying "Welcome to the Koha 19.11 web installer"! Can someone please explain what is going wrong here? 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-devel mailing list koha-de...@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/ ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Getting Koha 19.11 web installer when installing Koha 20.11.19
Hi Today I was installing Koha 20.11.19 on a completely new virtual host using Debian 11. $ sudo cat /etc/apt/sources.list.d/koha.list deb http://debian.koha-community.org/koha 20.11 main $ sudo apt-get update $ sudo apt-cache show koha-common | grep Version Version: 20.11.19-1 $ sudo apt-get install koha-common mariadb-server In the output I see lines like: Get:16 http://debian.koha-community.org/koha 20.11/main amd64 libcache-memcached-fast-safe-perl all 0.06-1~koha1 [7,410 B] Get:22 http://debian.koha-community.org/koha 20.11/main amd64 libhttp-oai-3.27-perl all 3.27-1~koha+1 [92.7 kB] Get:16 http://debian.koha-community.org/koha 20.11/main amd64 libcache-memcached-fast-safe-perl all 0.06-1~koha1 [7,410 B] Get:22 http://debian.koha-community.org/koha 20.11/main amd64 libhttp-oai-3.27-perl all 3.27-1~koha+1 [92.7 kB] Get:36 http://debian.koha-community.org/koha 20.11/main amd64 libmojolicious-perl all 9.90+really8.12-koha1 [794 kB] Get:75 http://debian.koha-community.org/koha 20.11/main amd64 libjson-validator-perl all 5.99+really3.14-koha1 [54.2 kB] Get:85 http://debian.koha-community.org/koha 20.11/main amd64 libmojolicious-plugin-openapi-perl all 5.99+really2.16-koha1 [57.1 kB] Get:88 http://debian.koha-community.org/koha 20.11/main amd64 libpdf-fromhtml-perl all 0.31-1~koha1 [102 kB] Get:98 http://debian.koha-community.org/koha 20.11/main amd64 libtemplate-plugin-htmltotext-perl all 0.03-1koha1 [6,134 B] Get:99 http://debian.koha-community.org/koha 20.11/main amd64 koha-common all 20.11.19-1 [34.5 MB] Preparing to unpack .../523-koha-common_20.11.19-1_all.deb ... Unpacking koha-common (20.11.19-1) ... Setting up koha-common (20.11.19-1) ... However after the installation when calling the web installer it annoyingly greets me saying "Welcome to the Koha 19.11 web installer"! Can someone please explain what is going wrong here? 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] Subject headings in two languages
Hi We are using Koha 19.05.02 on Debian GNU/Linux 9. In many ways Koha supports the use of multiple languages - this does not seem to be the case concerning authority records We would like to add subject headings in two languages (German and English) to our bibliographic records. Thus we'd like to ask for best practices how to manage subject headings in two languages: 1. How to create them, how to edit them, how to link the German subject heading to the English one and vice versa? 2. How to display subject headings in two languages in the OPAC? 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] Advanced editor page keeps loading
Hi We are using Koha 18.11.03 with Debian GNU/Linux 9. When trying to edit a bibliographic record using the advanced editor sometimes only part of the page appears, saying "Loading, please wait.." - but loading never comes to an end. See the screenshot at http://adminkuhn.ch/download/AdvancedEditor.JPG - Though editing the record in the basic editor is working. It does not help reloading the page, or logging out and logging in again, also we couldn't find an obvious mistake in the bibliographic record. Does anyone know the solution to this problem? 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] How to copy patron permissions?
Hi Christopher You wrote: > I've had some jQuery in the Koha library for quite a while. You should > take a look at https://wiki.koha-community.org/wiki/JQuery_Library#Add_clear_and_preset_permission_buttons.2C_and_a_copy_button_to_user_permissions_page_.28v20.x.29 > > There are 3 versions of this for different versions of Koha, but this > latest one includes a clear permissions button, a couple of preset > permission buttons, and a copy permissions button. Please check it > out. We also did a video tutorial on this enhancement in season one of > The Terrific Every-Other-Thursday Training Videos. You can find that > here: https://youtu.be/M6aQITCJY0U. Thank you very much for the information! I have noted it for a possible other use case in the future. As I have written in an earlier post of this thread the current library is trying to avoid non-Koha-standard methods like (ever-changing) external Javascript or plugins. It doesn't need to copy patron permissions very often, so it will wait until Koha implements a proper way to copy patron permissions, e. g. according to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30623 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] How to copy patron permissions?
Hi Katrin You wrote: > this will work as long as you only assign 'module/top level > permissions. > As soon as you only assign some sub-permissions of a module to a user, > you'll also need the entries from the user_permissions table. Yes, you are right. To circumvent this problem it is necessary to do the following. 1. Find the borrowernumber (here: 11) of a patron which has the desired patron permissions, then search for the patron permissions of this patron: SELECT flags FROM borrowers WHERE borrowernumber=11; 2. The result will show the number associated with the staff member’s permissions, for example: +---+ | flags | +---+ | 16900 | +---+ 3. Then update the field "flags" of a new patron (here with borrowernumber 12) which currently has no permissions but which should receive the same top level permissions as the original patron: UPDATE borrowers SET flags=16900 WHERE borrowernumber=12; 4. Update the fields in table "user_permissions" of this patron (here with borrowernumber 12) which should also receive the same sub-permissions as the original patron (here with borrowernumber 11): INSERT INTO user_permissions (borrowernumber, module_bit, code) SELECT 12, module_bit, code FROM user_permissions WHERE borrowernumber=11; I have tested this successfully on my demo installation. 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] How to copy patron permissions?
Hi Katrin You wrote: > this will work as long as you only assign 'module/top level > permissions. > As soon as you only assign some sub-permissions of a module to a user, > you'll also need the entries from the user_permissions table. Thanks for this important hint! Yes, in this case it is not as easy as I described it. Unfortunately. 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 27.04.22 12:31, Michael Kuhn wrote: Hi Thanks to all who answered my e-mail concerning patron permissions! Raymund Delahunty, Owen Leonard, David Nind, Joel Coehoorn, Michael Sutherland and Katrin Fischer! I have saved all the information you gave me for other uses cases. But in our current library we are hesitating to use non-Koha-standard methods like external Javascript or plugins. Since we don't need to copy patron permissions very often we will wait until Koha implements a proper way to copy patron permissions, e. g. according to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30623 For the cases when we actually need to copy patron permissions, for us the following way seems to be the easiest (instead of manual "box ticking") : 1. Find the cardnumber (here: 25) of a patron which has the desired patron permissions, then search for the patron permissions of this patron: SELECT flags FROM borrowers WHERE cardnumber=25; 2. The result will show the number associated with the staff member’s permissions, for example: +---+ | flags | +---+ | 16900 | +---+ 3. Then update the field "flags" of another patron (here with cardnumber 26) which should receive the same patron permissions: UPDATE borrowers SET flags=16900 WHERE cardnumber=26; I have tested this successfully on my demo installation. 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 mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] How to copy patron permissions?
Hi Thanks to all who answered my e-mail concerning patron permissions! Raymund Delahunty, Owen Leonard, David Nind, Joel Coehoorn, Michael Sutherland and Katrin Fischer! I have saved all the information you gave me for other uses cases. But in our current library we are hesitating to use non-Koha-standard methods like external Javascript or plugins. Since we don't need to copy patron permissions very often we will wait until Koha implements a proper way to copy patron permissions, e. g. according to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30623 For the cases when we actually need to copy patron permissions, for us the following way seems to be the easiest (instead of manual "box ticking") : 1. Find the cardnumber (here: 25) of a patron which has the desired patron permissions, then search for the patron permissions of this patron: SELECT flags FROM borrowers WHERE cardnumber=25; 2. The result will show the number associated with the staff member’s permissions, for example: +---+ | flags | +---+ | 16900 | +---+ 3. Then update the field "flags" of another patron (here with cardnumber 26) which should receive the same patron permissions: UPDATE borrowers SET flags=16900 WHERE cardnumber=26; I have tested this successfully on my demo installation. 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] How to copy patron permissions?
Hi Is it possible to copy the permissions of another patron when creating a new one? I always thought this would happen when copying/duplicating an existing patron. But when I actually tried it today the permissions were not there with the new patron and I had to set them manually. Best wishes: Michael Kuhn -- 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
