A new request with request id 8041 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :

Title : Koha-devel Digest, Vol 201, Issue 5
Category :
Description :
Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Re: Dependency problem when installing Koha 21.11.10 on
Debian 11 (Mason James)
2. Getting "count" when using REST API (dcook@prosentient.com.au)
3. Re: Dependency problem when installing Koha 21.11.10 on
Debian 11 (Michael Kuhn)


----------------------------------------------------------------------

Message: 1
Date: Thu, 4 Aug 2022 17:15:24 +1200
From: Mason James <mtj@kohaaloha.com>
To: Michael Kuhn <mik@adminkuhn.ch>,
    koha-devel@lists.koha-community.org, Koha <koha@lists.katipo.co.nz>
Subject: Re: [Koha-devel] Dependency problem when installing Koha
    21.11.10 on Debian 11
Message-ID: <d1ae917f-33ad-c473-89a7-84dab64a2625@kohaaloha.com>
Content-Type: text/plain; charset=UTF-8; format=flowed


On 4/08/22 2:34 am, Michael Kuhn 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

hi Michael
i often use docker to confirm that koha installs successfully

you can use the following transcript to confirm it is possible to install...

------------------------------------------
mason@xen1:~$ docker run -it debian:11
root@104f8750cb71:/# apt-get update
root@104f8750cb71:/# apt-get -y install ca-certificates wget gnupg2 dialog apt-utils sudo
root@104f8750cb71:/# wget -q -O- https://debian.koha-community.org/koha/gpg.asc | sudo apt-key add -
root@104f8750cb71:/# echo 'deb http://debian.koha-community.org/koha 22.05 main' | sudo tee /etc/apt/sources.list.d/koha.list
root@104f8750cb71:/# apt-get update


root@104f8750cb71:/# apt-get -y install koha-common
...
Setting up koha-common (22.05.03-1) ...
...
root@2941ef956ace:/# echo $?
0


root@104f8750cb71:/# apt policy koha-common
koha-common:
  Installed: 22.05.03-1
  Candidate: 22.05.03-1
  Version table:
 *** 22.05.03-1 500
        500 http://debian.koha-community.org/koha 22.05/main amd64 Packages
        100 /var/lib/dpkg/status

root@104f8750cb71:/# apt policy rabbitmq-server
rabbitmq-server:
  Installed: 3.8.9-3
  Candidate: 3.8.9-3
  Version table:
 *** 3.8.9-3 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status

root@2941ef956ace:/# exit
exit
mason@xen1:~$
------------------------------------------



------------------------------

Message: 2
Date: Thu, 4 Aug 2022 16:54:15 +1000
From: <dcook@prosentient.com.au>
To: "'Koha Devel'" <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Getting "count" when using REST API
Message-ID: <0f7b01d8a7cf$09241c60$1b6c5520$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"

Hi all,



Is there a method for getting a "count" using the REST API without fetching
every record?



When building a paging lookup outside of Koha, it would be useful to get a
total record count and then just fetch the page of records that you need.



Thanks!



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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220804/a83c3470/attachment-0001.htm>

------------------------------

Message: 3
Date: Thu, 4 Aug 2022 09:46:22 +0200
From: Michael Kuhn <mik@adminkuhn.ch>
To: Michael Hafen <michael.hafen@washk12.org>
Cc: koha-devel@lists.koha-community.org, Koha
    <koha@lists.katipo.co.nz>
Subject: Re: [Koha-devel] Dependency problem when installing Koha
    21.11.10 on Debian 11
Message-ID: <9b190da6-b068-c2e8-d2f1-b43cc6bfb853@adminkuhn.ch>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi Michael

Thanks fpr your answer! Unfortunately I'm not able to figure out the
problem. "journalctl -xe" and "systemctl status rabbitmq-server.service"
both seem to show a working rabbitmq-server, but when trying to finish
the installation of package "koha-common" it fails with the same error
as before:

# journalctl -xe
░░ up or be started at any later time.
░░
░░ Startup of the manager took 238830 microseconds.
Aug 04 09:07:14 bib-katalog.sintiundroma.de systemd[1]: Started User
Manager fo>
░░ Subject: A start job for unit user@1000.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit user@1000.service has finished successfully.
░░
░░ The job identifier is 87146.
Aug 04 09:07:14 bib-katalog.sintiundroma.de systemd[1]: Started Session
40 of u>
░░ Subject: A start job for unit session-40.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-40.scope has finished successfully.
░░
░░ The job identifier is 87212.
Aug 04 09:07:14 bib-katalog.sintiundroma.de sudo[312293]: koha :
TTY=pts/0 >
Aug 04 09:07:14 bib-katalog.sintiundroma.de sudo[312293]:
pam_unix(sudo:session>
Aug 04 09:07:14 bib-katalog.sintiundroma.de su[312294]: (to root) koha
on pts/0
Aug 04 09:07:14 bib-katalog.sintiundroma.de su[312294]:
pam_unix(su-l:session):>


# systemctl status rabbitmq-server.service
● rabbitmq-server.service - RabbitMQ Messaging Server
Loaded: loaded (/lib/systemd/system/rabbitmq-server.service;
enabled; vend>
Active: activating (start) since Thu 2022-08-04 09:11:43 CEST; 4s ago
Main PID: 313407 (beam.smp)
Tasks: 90 (limit: 9510)
Memory: 54.3M
CPU: 2.952s
CGroup: /system.slice/rabbitmq-server.service
├─313407 /usr/lib/erlang/erts-11.1.8/bin/beam.smp -W w -K
true -A >
├─313509 erl_child_setup 65536
├─313566 inet_gethost 4
└─313567 inet_gethost 4

Aug 04 09:11:43 bib-katalog.sintiundroma.de systemd[1]: Starting
RabbitMQ Messa>


Here I am trying to finish the installation. It is the same if I only
try to (finish to) install "koha-common" and/or "mariadb-server". In the
past this always worked without any problems.

# apt-get install koha-common mariadb-server
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
koha-common is already the newest version (22.05.03-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] Y
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 Thu
2022-08-04 09:16:53 CEST; 20ms ago
Process: 314689 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server
(code=exited, status=1/FAILURE)
Main PID: 314689 (code=exited, status=1/FAILURE)
CPU: 6.436s

Aug 04 09:16:53 bib-katalog.sintiundroma.de systemd[1]:
rabbitmq-server.service: Consumed 6.436s 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
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


The following command gives the same error:

# dpkg --configure rabbitmq-server
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 Thu
2022-08-04 09:33:47 CEST; 8ms ago
Process: 319999 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server
(code=exited, status=1/FAILURE)
Main PID: 319999 (code=exited, status=1/FAILURE)
CPU: 7.157s
dpkg: error processing package rabbitmq-server (--configure):
installed rabbitmq-server package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
rabbitmq-server


In the files "/var/log/daemon.log" and "/var/log/daemon.log" the
following can be seen. Apparently the RabbitMQ Messaging server fails
during the configuration process and then tries to start several times
but unsuccessfully. Thus the configuration stays incomplete and the
installation of "koha-common" cannot be finished.

Aug 4 09:38:38 bib-katalog systemd[1]: Starting RabbitMQ Messaging
Server...
Aug 4 09:39:13 bib-katalog systemd[1]: rabbitmq-server.service: Main
process exited, code=exited, status=1/FAILURE
Aug 4 09:39:13 bib-katalog systemd[1]: rabbitmq-server.service: Failed
with result 'exit-code'.
Aug 4 09:39:13 bib-katalog systemd[1]: Failed to start RabbitMQ
Messaging Server.
Aug 4 09:39:13 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 4.505s CPU time.
Aug 4 09:39:23 bib-katalog systemd[1]: rabbitmq-server.service:
Scheduled restart job, restart counter is at 1359.
Aug 4 09:39:23 bib-katalog systemd[1]: Stopped RabbitMQ Messaging Server.
Aug 4 09:39:23 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 4.505s CPU time.
Aug 4 09:39:23 bib-katalog systemd[1]: Starting RabbitMQ Messaging
Server...
Aug 4 09:39:58 bib-katalog systemd[1]: rabbitmq-server.service: Main
process exited, code=exited, status=1/FAILURE
Aug 4 09:39:58 bib-katalog systemd[1]: rabbitmq-server.service: Failed
with result 'exit-code'.
Aug 4 09:39:58 bib-katalog systemd[1]: Failed to start RabbitMQ
Messaging Server.
Aug 4 09:39:58 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 3.872s CPU time.
Aug 4 09:40:09 bib-katalog systemd[1]: rabbitmq-server.service:
Scheduled restart job, restart counter is at 1360.
Aug 4 09:40:09 bib-katalog systemd[1]: Stopped RabbitMQ Messaging Server.
Aug 4 09:40:09 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 3.872s CPU time.
Aug 4 09:40:09 bib-katalog systemd[1]: Starting RabbitMQ Messaging
Server...
Aug 4 09:40:44 bib-katalog systemd[1]: rabbitmq-server.service: Main
process exited, code=exited, status=1/FAILURE
Aug 4 09:40:44 bib-katalog systemd[1]: rabbitmq-server.service: Failed
with result 'exit-code'.
Aug 4 09:40:44 bib-katalog systemd[1]: Failed to start RabbitMQ
Messaging Server.
Aug 4 09:40:44 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 4.508s CPU time.
Aug 4 09:40:55 bib-katalog systemd[1]: rabbitmq-server.service:
Scheduled restart job, restart counter is at 1361.
Aug 4 09:40:55 bib-katalog systemd[1]: Stopped RabbitMQ Messaging Server.
Aug 4 09:40:55 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 4.508s CPU time.
Aug 4 09:40:55 bib-katalog systemd[1]: Starting RabbitMQ Messaging
Server...
Aug 4 09:41:30 bib-katalog systemd[1]: rabbitmq-server.service: Main
process exited, code=exited, status=1/FAILURE
Aug 4 09:41:30 bib-katalog systemd[1]: rabbitmq-server.service: Failed
with result 'exit-code'.
Aug 4 09:41:30 bib-katalog systemd[1]: Failed to start RabbitMQ
Messaging Server.
Aug 4 09:41:30 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 4.051s CPU time.
Aug 4 09:41:40 bib-katalog systemd[1]: rabbitmq-server.service:
Scheduled restart job, restart counter is at 1362.
Aug 4 09:41:40 bib-katalog systemd[1]: Stopped RabbitMQ Messaging Server.
Aug 4 09:41:40 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 4.051s CPU time.
Aug 4 09:41:40 bib-katalog systemd[1]: Starting RabbitMQ Messaging
Server...
Aug 4 09:42:16 bib-katalog systemd[1]: rabbitmq-server.service: Main
process exited, code=exited, status=1/FAILURE
Aug 4 09:42:16 bib-katalog systemd[1]: rabbitmq-server.service: Failed
with result 'exit-code'.
Aug 4 09:42:16 bib-katalog systemd[1]: Failed to start RabbitMQ
Messaging Server.
Aug 4 09:42:16 bib-katalog systemd[1]: rabbitmq-server.service:
Consumed 4.523s CPU time.


Do you maybe have any hint how to find out what could be the problem
with the failing configuration of package "rabbitmq-server"?

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?

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@adminkuhn.ch · W www.adminkuhn.ch



Am 03.08.22 um 19:46 schrieb Michael Hafen:
> The "rabbitmq-server" service is not starting for some reason.  Since it
> doesn't successfully start, the package manager considers it as not
> installed correctly; and since koha-common depends on it, the package
> manager doesn't do anything with koha-common.
> The output from the package manager mentions 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 <mik@adminkuhn.ch
> <mailto:mik@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 mik@adminkuhn.ch
> <mailto:mik@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
> > RabbitMQ Messaging Server.
> > Aug 03 14:30:23 bib-katalog.sintiundroma.de
> <http://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-devel mailing list
> 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>
> 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/>
>
>
>
> --
> Michael Hafen
> Washington County School District Technology Department
> Systems Analyst
>




------------------------------

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@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/


------------------------------

End of Koha-devel Digest, Vol 201, Issue 5
******************************************


NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.