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

Re: [Koha-devel] [Koha] Starting rabbitmq-server fails with Koha 22.11.05-2
by Michael Kuhn 11 May '23

11 May '23

Hi Costantino You wrote: > Do not move /var/lib/rabbitmq directory, just its content It seems to make no difference, since the content was recreated when trying to start rabbitmq-server anew: root@koha:/var/lib# ls -al rabbitmq/ insgesamt 3860 drwxr-xr-x 3 rabbitmq rabbitmq 4096 11. Mai 17:03 . drwxr-xr-x 33 root root 4096 11. Mai 17:03 .. -r-------- 1 rabbitmq rabbitmq 20 11. Mai 00:00 .erlang.cookie -rw-r----- 1 rabbitmq rabbitmq 3934248 11. Mai 17:13 erl_crash.dump drwxr-x--- 2 rabbitmq rabbitmq 4096 11. Mai 17:03 mnesia These are the same files as movedto /BACKUPTMP: root@koha:/var/lib# ls -al /BACKUPTMP/rabbitmq/ insgesamt 3860 drwxr-xr-x 3 rabbitmq rabbitmq 4096 11. Mai 15:10 . drwxr-xr-x 3 root root 4096 11. Mai 16:49 .. -r-------- 1 rabbitmq rabbitmq 20 11. Mai 00:00 .erlang.cookie -rw-r----- 1 rabbitmq rabbitmq 3934442 11. Mai 16:48 erl_crash.dump drwxr-x--- 2 rabbitmq rabbitmq 4096 10. Apr 2021 mnesia I would prefer to just forget about Koha 22.11.05-2 and try with Koha 22.11.03-1, but I don't know how to do that when using Debian packages. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch > Do not move /var/lib/rabbitmq directory, just its content > > El 11-05-2023 11:52, Michael Kuhn escribió: > >> 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: <mailto:koha@koha:>~$ sudo systemctl stop mysql >> koha@koha: <mailto:koha@koha:>~$ sudo systemctl stop rabbitmq-server >> koha@koha: <mailto:koha@koha:>~$ sudo mkdir /BACKUPTMP >> koha@koha: <mailto:koha@koha:>~$ sudo mv /var/lib/rabbitmq /BACKUPTMP >> koha@koha: <mailto:koha@koha:>~$ sudo systemctl start mysql >> koha@koha: <mailto: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 · Emik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch> · Wwww.adminkuhn.ch <http://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 mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch> · W >>>> www.adminkuhn.ch <http://www.adminkuhn.ch> [1] koha@koha: >>>> <mailto: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: <mailto: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 >>>> <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 >>>> <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 >>>> <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 <http://koha-community.org> [3] >>>> Koha(a)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> [4] > > -- > > *Costantino, Fernán* > División Nuevas Tecnologías > Biblioteca Central Francisco P. Moreno > Universidad Nacional del Comahue > Santa Fe y Leloir (Q8300) Neuquén Cap.- Tel 54(0299)4490398 >

1 0

Re: [Koha-devel] Starting rabbitmq-server fails with Koha 22.11.05-2
by Michael Kuhn 11 May '23

11 May '23

Hi Veronica You wrote: > our hostname was a long one like "webserver-20983.hosteurope.com". > Changing the hostname in /etc/hostname to something simpler (like > "kohaserver") enabled us to install Koha without problem. > But maybe you have another problem. The hostname in file "/etc/hostname" is just "koha", so it seems simple enough. But yes, as I already wrote in another e-mail, 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 mik(a)adminkuhn.ch · W www.adminkuhn.ch > El jueves, 11 de mayo de 2023, 11:48:14 ART, Michael Kuhn > <mik(a)adminkuhn.ch> escribió: > > > Hi Veronica > > You wrote: > > > we had a similar problem installing Koha 22.05. Solution was changing > > the hostname to something more simple. > > Hope you can solve this. > > What do you mean with "more simple"? Our hostname is just "koha"... > > Best wishes: Michael > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz > T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch> · > W www.adminkuhn.ch > > > > > > El jueves, 11 de mayo de 2023, 11:37:00 ART, Michael Kuhn > > <mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch>> escribió: > > > > > > Hi Philippe > > > > You wrote: > > > > > Simple typo, it's > > > > > > systemctl COMMAND servicename > > > > > > as > > > > > > systemctl stop rabbitmq-server > > > > Thanks for the hint ( I could have seen that) but it doesn't help: > > > > koha@koha:~$ sudo systemctl stop rabbitmq-server > > 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. > > > > The basic problem seems to be that package "koha-common" 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 mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch> > <mailto:mik@adminkuhn.ch> · > > W www.adminkuhn.ch > > > > > > > > > > > On 2023-05-11 10:18, Michael Kuhn wrote: > > >> 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 > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > > <mailto:Koha-devel@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> > > <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/> <https://www.koha-community.org/ > <https://www.koha-community.org/>> > > git : https://git.koha-community.org/ > <https://git.koha-community.org/> <https://git.koha-community.org/ > <https://git.koha-community.org/>> > > bugs : https://bugs.koha-community.org/ > <https://bugs.koha-community.org/> <https://bugs.koha-community.org/ > <https://bugs.koha-community.org/>> > > >

1 0

Re: [Koha-devel] Starting rabbitmq-server fails with Koha 22.11.05-2
by Michael Kuhn 11 May '23

11 May '23

Hi Veronica You wrote: > we had a similar problem installing Koha 22.05. Solution was changing > the hostname to something more simple. > Hope you can solve this. What do you mean with "more simple"? Our hostname is just "koha"... Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch > El jueves, 11 de mayo de 2023, 11:37:00 ART, Michael Kuhn > <mik(a)adminkuhn.ch> escribió: > > > Hi Philippe > > You wrote: > > > Simple typo, it's > > > > systemctl COMMAND servicename > > > > as > > > > systemctl stop rabbitmq-server > > Thanks for the hint ( I could have seen that) but it doesn't help: > > koha@koha:~$ sudo systemctl stop rabbitmq-server > 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. > > The basic problem seems to be that package "koha-common" 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 mik(a)adminkuhn.ch <mailto:mik@adminkuhn.ch> · > W www.adminkuhn.ch > > > > > > On 2023-05-11 10:18, Michael Kuhn wrote: > >> 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 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@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/>

1 0

Re: [Koha-devel] Starting rabbitmq-server fails with Koha 22.11.05-2
by Michael Kuhn 11 May '23

11 May '23

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 mik(a)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 <mik(a)adminkuhn.ch> 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 mik(a)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-devel mailing list >> Koha-devel(a)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/

2 2

Timeouts when doing stocktake/inventory
by David Cook 10 May '23

10 May '23

Hi all, Recently, I've had several libraries getting timeouts when using the stocktake/inventory feature. The timeout isn't coming from the server-side, but rather from the HTTP forward proxies being used by these libraries (or rather the much larger organisations to which the libraries belong). They appear to timeout after about 55-60 seconds of inactivity. So far the stocktake/inventory feature is the key pain point. I'm wondering if we should aim at moving at least some of the stocktake/inventory work into background processing, or at the very least staged processing, so fewer steps are happening during a single HTTP request. Before I do any work on it, I'd like to get a sense of what other people think is a good idea for this feature. 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

Author search links on 110 and 710...
by David Cook 10 May '23

10 May '23

Hi all, When clicking on an author search link, only the "a" subfield is used, but corporate authors often need both the "a" and "b" subfields in order to differentiate between corporate authors in a meaningful way. For instance, "110 $a United States. $b Court of Appeals" vs "110 $a United States. $b Congress". Another thought I had was that we should do an au,phr search on the same text that we're displaying on the page. What do folk think of that? 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

Re: [Koha-devel] Error when importing file
by David Nind 08 May '23

08 May '23

> In code, is correct, but log file has _ on final > Apologies, it wasn't that then! See bug 33412 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412 The code used to fix the issue (bug is signed off, but has not passed QA or been pushed yet): $overlay_framework = undef if $overlay_framework eq '_USE_ORIG';

1 1

Error when importing file
by Tiago Murakami 05 May '23

05 May '23

Hi, I try to import an MARC file in koha and job failed. I search the log file intranet-error.log and found this error: [Fri May 05 08:50:43.696999 2023] [cgi:error] [pid 7720] [client ::1:42966] AH01215: Found = in conditional, should be == at /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl line 93.: /usr/share/koha/intranet/cgi-bin/tools/manage-marc-import.pl, referer: http://localhost:8080/cgi-bin/koha/tools/manage-marc-import.pl?import_batch… Can you please let me know if this is a configuration error or a system error? Thanks -- Tiago Rodrigo Marçal Murakami Bibliotecário

4 6

Reorganising the contents of the manual - feedback
by David Nind 05 May '23

05 May '23

Late last year, I did some work on reorganising the contents of the manual. I thought I would ask for feedback on the development list first, before seeking feedback on the main one. Currently, the contents of the manual is a long list of modules/features/topics in a seemingly random order. This makes it harder for Koha Community members to see what is documented, and find what they are looking for. The proposed reorganisation has these main sections on the manual landing/home page: - What's new - Getting started - Using Koha - Implementing Koha - Installing Koha - System preferences Further work is required for each of these sections, but the existing manual content mostly fits under each of these (and can be updated over time). A document about the proposed contents sets out some more details - feel free to add your comments, questions or ideas: Google doc <https://docs.google.com/document/d/1KyrsMVWG_kcVvbFsUkysRC9oovIbFCNTNgCwSyM…> or Framapad doc <https://annuel.framapad.org/p/koha-manual-contents-reorganisation> You can view the proposed changes on this demo site <https://davidnind.gitlab.io/koha-docs-reorganise/> (it was generated in December last year, so doesn't reflect the changes made since then to the current manual). The bug for this is 32391 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32391>. I would welcome any feedback, either positive or negative. Feel free to comment on the bug, add comments or questions to the documents, or reply to the list (or directly to me). David Nind | david(a)davidnind.com m. +64 21 0537 847

1 0

Last week to submit your Koha talk for the KohaCon: Perl and Koha conference in Helsinki 2023
by Perl Koha 03 May '23

03 May '23

*TL;DR :* 1. There's only one week left before our call for talks closes on April 30th. Don't hesitate to submit your draft ideas or works in progress here: ➡️ CALL FOR TALKS SUBMISSION PAGE: perlkohacon.fi/cft <https://perlkohacon.fi/Call-For-Talks-Perl-Koha-Helsinki-August-2023.html> 2. The Perl and Koha Conference in Helsinki will happen from 📅 *August 14th to 18th, 2023* More hints on this soon! 3. Track our social channels (we prefer Telegram): - *t*.me/PerlKohaCon <http://t.me/PerlKohaCon> - *Facebook*.com/PerlKohaCon <http://Facebook.com/PerlKohaCon> - *Twitter*.com/PerlKohaCon <http://Twitter.com/PerlKohaCon> - *Instagram*.com/PerlKohaCon <http://Instagram.com/PerlKohaCon> - *LinkedIn*.com/showcase/PerlKohaCon <http://LinkedIn.com/showcase/PerlKohaCon> - (Mastodon) *Fosstodon*.org/@perlkohacon <http://Fosstodon.org/@perlkohacon> ... and share the link to this message you are reading among your friendly bubble. 🤗 We need more interesting talks, we need more attendees, and you. *LONG VERSION, with some fun and suspense:* We're inspired to bring you the "Perl and Koha Conference in Helsinki" (also known as KohaCon with YAPC::Europe/PerlCon) taking place from 📅 August 14th to 18th, 2023. The conference will feature three days of talk streams (August 14th to 16th) and two additional days of workshops and special meetings (August 17th to 18th). Among all the usual things you know about KohaCon, this time, we have a unique event that gives an opportunity for the Koha and Perl communities to unite, exchange insights, and forge (unwind together!) new connections. As a valued member of the Koha community of all of you, we need your expertise! 🌟 We also need your help to present Koha to the Perl community in the best possible way, as Koha could become the flagship product for the Perl community. To make that happen, we need to unite, present ourselves, and share all the ideas we can come up with! (By the way, you can propose ideas through our channels or by reaching out directly to the main organizer, Andrii, at nugged(a)gmail.com) There's only one week left before our call for talks closes on April 30th. Don't hesitate to submit your draft ideas or works in progress here: ➡️ CALL FOR TALKS SUBMISSION PAGE: perlkohacon.fi/cft <https://perlkohacon.fi/Call-For-Talks-Perl-Koha-Helsinki-August-2023.html> After you make a placeholder for a talk (i.e. send the form), we will know this, and confirm with you later, and this will help us to select the best talks, make the conference most interesting and useful, and plan our schedule. Afterward, you can progress with your talk development further, this means no need to have the talk ready in one week, so no panic. No-panic more: if you want, you can talk to our dedicated team, who is ready to help you refine your talk and provide guidance if needed. Reach out to us at perlkohacon(a)gmail.com 💌. If you have experience in Koha or around, but no experience in stage-action: we value first more, so we'll try to cover your back! Mind that talk is only one part of the reason and only ignition point to share your experience: you might find mates and interested people after your presentation, so that might be just the beginning of something greater! We will talk all about expansion, improvement, and experience exchange, and these are engaging topics for your talk (but keep your experience in priority of anything below): Best practices, tips, hacks, and challenges in using Koha in the library Koha software development, including integrations with other systems The future of BIBFRAME, MARC, and Linked Open Data in Koha Features needed for Koha to become more capable, which the Perl community can contribute to, such as ILL, ERM, and others Upcoming or requested Koha feature developments: proposals, progress, and collaboration opportunities As this will be an event with many IT professionals and developers from the Perl community, we will also cover geekier and dev-related topics. However, we will have one separate stream fully dedicated to libraries (usage, pro-tips, and KohaCon-related topics). You will meet library and Koha experts from 🇫🇮Finland, a country that has already switched hundreds of libraries to Koha, as well as experts from ByWater Solutions, BibLibre, PTFS Europe, Koha-and-library IT-topic activists from France, Germany, Sweden, and more. Even from Ukraine (consider there will be something special about this). This conference is an excellent opportunity to make meaningful connections with the Perl community and explore how these relationships can benefit the Koha community! 🤝 Don't forget, August is an ideal time for a summer vacation in Helsinki with your family. ☀️ Extend your stay over the weekends to experience the city's culture and attractions while attending the conference. We will have a partners program and more coordinated activities (might be even sponsored, but we need more participants and attendees to make that happen!). Stay connected by following us on social media, there, we will publish more and announce things that we will have these weeks soon before the conference (yes, something gifty or nifty is planned). We'll target as main social channel Telegram one: - t.me/PerlKohaCon and encourage you to use this geeky, fast, and comfortable groups, channels, and messaging platform. But feel free to join us on any of these platforms for news and updates: - Facebook.com/PerlKohaCon - Twitter.com/PerlKohaCon - Instagram.com/PerlKohaCon - LinkedIn.com/showcase/PerlKohaCon - (Mastodon) Fosstodon.org/@perlkohacon Feel free to use the platform where you have the most connections to share and spread the word! *🙏 "Kiitos" - this means "Thank you" in Finnish.* Btw, and sounds as it reads, no fine prints! Please share this message with colleagues and friends who might be interested in presenting at the conference or attending. Together, let's make this event a significant and enriching experience for both the Koha and Perl communities! 🚀 ... and we look forward to seeing you in Helsinki! Warm regards, The Perl and Koha Conference Organizing Team === Andrii and the National Library of Finland Koha team!

1 1