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

Re: [Koha-devel] [Koha] Roles for 24.05 are open
by Fridolin SOMERS 03 Nov '23

03 Nov '23

Hi community :D I'm happy to propose for the role of Release Maintainer for 23.11. I see we are currently missing a Release Maintainer for 22.11 LTS. This is a very important role for our LTS proposition : https://wiki.koha-community.org/wiki/Koha_Versioning#LTS_Releases Best regards, Le 18/10/2023 à 03:18, Tomas Cohen Arazi a écrit : > A new cycle is about to start. It is time for you all to put your names for > the next release. > > Here: https://wiki.koha-community.org/wiki/Roles_for_24.05 > > Best regards > -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 1

Is koha-common.postinst restarting services in the correct order?
by Aleisha Amohia 03 Nov '23

03 Nov '23

Hello everyone Curious what other people think here... We have set up koha-common to be upgraded using unattended upgrades. Whenever we do this, something happens to koha-worker and eventually worker-output.log fills up the disk. The only solution appears to be deleting the log file then restarting memcached and koha-common - but it would be good to avoid doing this if our packages get upgraded for us overnight. Keen on a discussion here! How do you manage this? Does koha-common.postinst need to be changed to restart services better or do we want to keep it as is so Koha administrators must restart services manually after koha-common is upgraded? -- *Aleisha Amohia (she/her)* Koha Technical Lead *Catalyst.Net Limited - Expert Open Source Solutions* *Catalyst.Net Ltd - a Catalyst IT group company* Tel: +64 4 803 2259 or +61 3 9116 2642 | www.catalyst.net.nz <http://www.catalyst.net.nz> Follow Catalyst Koha on Twitter <https://twitter.com/catalystkoha> | Subscribe to the Catalyst Koha newsletter <https://catalyst.us4.list-manage.com/subscribe?u=62457ff5060d15ee3c07d3fc4&…> Catalyst Logo CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

2 1

Koha Community Newsletter: October 2023
by Koha Newsletter 01 Nov '23

01 Nov '23

The Koha Community Newsletter for October 2023 is here: https://koha-community.org/koha-community-newsletter-october-2023/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

2 1

Memory footprint of Koha processes
by Philippe Blouin 24 Oct '23

24 Oct '23

Howdy! I'm trying to run a server with MANY koha instances (for educational purposes), but although the usage is very small, the resources required just make everything explode. background_jobs_worker.pl for instance uses 170M per instance, and plack uses 200M without anything being loaded. Any suggestion how this could be hacked (locally) to allow for 200 koha instances on a machine without requiring 100G of memory ? The object model seems at fault here, but I see no way to go around "use Koha::BackgroundJobs;" at the top of the script. Thanks! -- Philippe Blouin, Directeur de la technologie Tél. : (833) 465-4276, poste 230 philippe.blouin(a)inLibro.com inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

4 5

Elasticsearch issue in koha v22.05.06
by Amar Londhe 23 Oct '23

23 Oct '23

Hello, We've recently installed Koha (version 22.05.06) and are attempting to enable Elasticsearch for our system. However, we've encountered some difficulties during the configuration process. The problem arises when we attempt to rebuild or perform searches in the OPAC (Online Public Access Catalog). The error message we encounter is as follows: $ export KOHA_CONF=/etc/pnvmkoha/koha-conf.xml $ export PERL5LIB=/usr/share/pnvmkoha/lib $ /usr/share/pnvmkoha/bin/search_tools/rebuild_elasticsearch.pl -v -d [NoNodes] ** No nodes are available: [localhost:9200], called from sub Search::Elasticsearch::Role::Client::Direct::ANON at /usr/share/koha_inst/lib/Koha/SearchEngine/Elasticsearch/Indexer.pm line 421. Here are some key details: *Elastic search : * root@server1:~# curl localhost:9200 { "name" : "YKwcLd8", "cluster_name" : "elasticsearch", "cluster_uuid" : "kKKWjSXJTPeRCCMYDVNdTw", "version" : { "number" : "6.8.23", "build_flavor" : "default", "build_type" : "deb", "build_hash" : "4f67856", "build_date" : "2022-01-06T21:30:50.087716Z", "build_snapshot" : false, "lucene_version" : "7.7.3", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" } *Java version : * root@server1:~# java --version openjdk 11.0.20.1 2023-08-24 OpenJDK Runtime Environment (build 11.0.20.1+1-post-Ubuntu-0ubuntu122.04) OpenJDK 64-Bit Server VM (build 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, mixed mode, sharing) *koha-conf.xml : * <elasticsearch> <server>localhost:9200</server> <index_name>KOHA__INST</index_name>  <cxn_pool>Static</cxn_pool>   </elasticsearch> <elasticsearch_index_mappings>/etc/koha_inst/searchengine/elasticsearch/mappings.yaml</elasticsearch_index_mappings> *Server Details : * Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy Note : We have tried to enabled ES on koha v20.11.06 and its working fine without any error. Please let me know if you need any additional information or if you have any suggestions to resolve this Elasticsearch configuration problem. -- Thanks and Regards, Amar Londhe

3 3

I'm not getting your emails on bugs...
by David Cook 23 Oct '23

23 Oct '23

Hi all, It looks like my "bugmail has been disabled" for the last 10 days on Bugzilla, so if I haven't responded to a comment on Bugzilla, it's not because I'm ignoring you. It's because I'm not getting the emails. (If an administrator sees this, please re-enable my bugmail. Thanks!) I've been trying to weed through the contents from koha-bugs(a)lists.koha-community.org <mailto:koha-bugs@lists.koha-community.org> which I still receive but there's so many emails I'm likely to miss the vast majority. So if you need anything from me urgently, shoot me an email directly? David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 1

Anyone else having issues attaching patches to Bugzilla?
by David Cook 23 Oct '23

23 Oct '23

Hi all, Trying to attach a patch to Bugzilla this afternoon and I get the following error: Cleaning up back to original state on error Traceback (most recent call last): File "/usr/bin/git-bz", line 2840, in <module> do_attach(*args) File "/usr/bin/git-bz", line 2168, in do_attach add_url(bug, commits) File "/usr/bin/git-bz", line 1719, in add_url add_url_to_head_commit(commit, bug) File "/usr/bin/git-bz", line 1682, in add_url_to_head_commit git.commit(file="-", amend=True, _input=input) File "/usr/bin/git-bz", line 197, in f o = git_run(command, *args, **kwargs) File "/usr/bin/git-bz", line 167, in git_run output, error = process.communicate(input) File "/usr/lib/python3.9/subprocess.py", line 1134, in communicate stdout, stderr = self._communicate(input, endtime, timeout) File "/usr/lib/python3.9/subprocess.py", line 1961, in _communicate input_view = memoryview(self._input) TypeError: memoryview: a bytes-like object is required, not 'str' I figure it's probably a "me problem" but just want to check. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 3

Keycloak as Identity Provider using Koha's users
by David Cook 23 Oct '23

23 Oct '23

Hi all, I've posted the Keycloak extension for using Koha's user database as Keycloak's user datastore: https://gitlab.com/minusdavid/keycloak-user-storage-koha This effectively allows you to use Koha (version 22.11.03 and upwards) as an Identity Provider - mediated via Keycloak (version 20 and up). So you can set up Koha to use Keycloak via SAML or OIDC and then have other third-party services like EBSCO EDS using the Keycloak, and thus you have SSO across the board while the users are fully managed through Koha, which is pretty cool. At some point, I might look into how I can host the built JAR on Gitlab as well, but I've provided the command to build the JAR using Docker, so it is very easy to do even if you're not a Java expert. Let me know if you need any help trying it out. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 2

Background jobs quirks
by David Cook 20 Oct '23

20 Oct '23

Hi all, Have you seen something like the following in your worker-error.log? 20231018 07:44:06 instance-koha-worker-long_tasks: client (pid 3949888) killed by signal 13, respawning 20231019 07:21:26 instance-koha-worker-long_tasks: client (pid 4082852) killed by signal 13, respawning I found some discussion in a thread https://www.mail-archive.com/koha@lists.katipo.co.nz/msg30046.html Signal 13 would be a SIGPIPE I believe. At first, I assumed it was the connection between the background worker and RabbitMQ, but based off the RabbitMQ logs[1] that seemed unlikely. MariaDB is another possibility. Looking at its logs [2] and I see some timed out connections. I might monitor the connections between the background workers and the database tonight and see if it's related. It might also explain why it happens on my MariaDB system but not my MySQL system. Anyway, just putting out some feelers. [1] 2023-10-18 07:44:06.492400+11:00 [info] <0.30487.131> accepting STOMP connection <0.30487.131> (127.0.0.1:59120 -> 127.0.0.1:61613) 2023-10-18 07:44:06.500534+11:00 [info] <0.30487.131> closing STOMP connection <0.30487.131> (127.0.0.1:59120 -> 127.0.0.1:61613) 2023-10-18 07:44:06.510426+11:00 [info] <0.20712.130> closing STOMP connection <0.20712.130> (127.0.0.1:57508 -> 127.0.0.1:61613) 2023-10-18 07:44:08.703380+11:00 [info] <0.30518.131> accepting STOMP connection <0.30518.131> (127.0.0.1:59882 -> 127.0.0.1:61613) 2023-10-19 07:21:26.254065+11:00 [info] <0.27344.133> accepting STOMP connection <0.27344.133> (127.0.0.1:54116 -> 127.0.0.1:61613) 2023-10-19 07:21:26.259129+11:00 [info] <0.27344.133> closing STOMP connection <0.27344.133> (127.0.0.1:54116 -> 127.0.0.1:61613) 2023-10-19 07:21:26.269652+11:00 [info] <0.30518.131> closing STOMP connection <0.30518.131> (127.0.0.1:59882 -> 127.0.0.1:61613) 2023-10-19 07:21:26.660604+11:00 [info] <0.27372.133> accepting STOMP connection <0.27372.133> (127.0.0.1:46178 -> 127.0.0.1:61613) [2] Oct 18 02:08:28 awesome-host mariadbd[959]: 2023-10-18 2:08:28 6308 [Warning] Aborted connection 6308 to db: 'koha_instance' user: 'koha_instance' host: 'localhost' (Got timeout reading communication packets) Oct 18 02:15:58 awesome-host mariadbd[959]: 2023-10-18 2:15:58 6304 [Warning] Aborted connection 6304 to db: 'koha_instance' user: 'koha_instance' host: 'localhost' (Got timeout reading communication packets) Oct 18 02:16:06 awesome-host mariadbd[959]: 2023-10-18 2:16:06 6303 [Warning] Aborted connection 6303 to db: 'koha_instance' user: 'koha_instance' host: 'localhost' (Got timeout reading communication packets) Oct 18 21:10:08 awesome-host mariadbd[959]: 2023-10-18 21:10:08 6380 [Warning] Aborted connection 6380 to db: 'koha_instance' user: 'koha_instance' host: 'localhost' (Got timeout reading communication packets) Oct 19 02:21:17 awesome-host mariadbd[959]: 2023-10-19 2:21:17 6431 [Warning] Aborted connection 6431 to db: 'koha_instance' user: 'koha_instance' host: 'localhost' (Got timeout reading communication packets) Oct 19 02:24:02 awesome-host mariadbd[959]: 2023-10-19 2:24:02 6432 [Warning] Aborted connection 6432 to db: 'koha_instance' user: 'koha_instance' host: 'localhost' (Got timeout reading communication packets) David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 5

MIssing emails for CC list?
by David Cook 19 Oct '23

19 Oct '23

Hi all, I'm used to getting emails for issues I'm CCed to, but I don't think I've gotten any for the last 1 week. Is this happening to anyone else or is it just me? I'm still getting emails addressed to koha-bugs(a)lists.koha-community.org <mailto:koha-bugs@lists.koha-community.org> but not to me specifically. I'll check the mail server next I guess but figured I'd ask the question. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0