Re: [Koha-devel] Rabbitmq
No. In a Docker container with a gitified package install. Op di 16 nov. 2021 om 14:27 schreef Jonathan Druart < jonathan.dru...@bugs.koha-community.org>: > Are you seeing this in koha-testing-docker? > > Le mar. 16 nov. 2021 à 14:11, Marcel de Rooy a > écrit : > > > > Hi all, > > > > Nobody seeing things like this? > > > > mkdir: cannot create directory ‘/var/run/rabbitmq’: Permission denied > > Failed to create directory: /var/run/rabbitmq > > /usr/lib/rabbitmq/bin/rabbitmq-server: 51: > /usr/lib/rabbitmq/bin/rabbitmq-server: cannot create /var/run/rabbitmq/pid: > Permission denied > > > > Look in /var/log/rabbitmq. Does your rabbitmq service start when you run > or restart a container? > > > > The solution is simple (mkdir and chown), but it needs to be placed > somewhere. > > > > Marcel > > > > ___ > > 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/ > ___ 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/
Re: [Koha-devel] Rabbitmq
Are you seeing this in koha-testing-docker? Le mar. 16 nov. 2021 à 14:11, Marcel de Rooy a écrit : > > Hi all, > > Nobody seeing things like this? > > mkdir: cannot create directory ‘/var/run/rabbitmq’: Permission denied > Failed to create directory: /var/run/rabbitmq > /usr/lib/rabbitmq/bin/rabbitmq-server: 51: > /usr/lib/rabbitmq/bin/rabbitmq-server: cannot create /var/run/rabbitmq/pid: > Permission denied > > Look in /var/log/rabbitmq. Does your rabbitmq service start when you run or > restart a container? > > The solution is simple (mkdir and chown), but it needs to be placed somewhere. > > Marcel > > ___ > 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/ ___ 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/
[Koha-devel] Rabbitmq
Hi all, Nobody seeing things like this? mkdir: cannot create directory ‘/var/run/rabbitmq’: Permission denied Failed to create directory: /var/run/rabbitmq /usr/lib/rabbitmq/bin/rabbitmq-server: 51: /usr/lib/rabbitmq/bin/rabbitmq-server: cannot create /var/run/rabbitmq/pid: Permission denied Look in /var/log/rabbitmq. Does your rabbitmq service start when you run or restart a container? The solution is simple (mkdir and chown), but it needs to be placed somewhere. Marcel ___ 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/
Re: [Koha-devel] RabbitMQ / bug 26742: in production message broker on a specific server ?
Hi Devid and all, I confirm that I will use Koha Debian packages (probably I will use Debian 10 with ES 6.x and PSGI/Plack). As you say, it is not a drama to use RabbitMQ. as local service. That you for the info. Bye Zeno Tajoli Il 24/11/2020 01:26, dc...@prosentient.com.au ha scritto: Hi Zeno, I certainly do remember you! I think that you misunderstand a little bit. The RabbitMQ dependency is necessary for both PSGI/Plack and CGI Koha when doing the batch record updates. (Over time, we'll change other parts of Koha to use RabbitMQ for message passing to a background worker as well.) I admit that I'm not 100% sure what 20.11.x is going to look like. I've been advocating for running RabbitMQ on a separate server, as that is the best practice recommended by the RabbitMQ community, but most patches have required that RabbitMQ runs on the same host as Koha. For now, I would say just trust the Koha Debian packages to do the right thing. Or are you not using the Koha Debian packages? For what it's worth, I already run RabbitMQ on production servers collocated with Koha, as I created a local tool in Koha that uses RabbitMQ. It shouldn't be too much of a drama. David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -Original Message- From: Koha-devel On Behalf Of Zeno Tajoli Sent: Tuesday, 24 November 2020 10:15 AM To: koha-devel Subject: [Koha-devel] RabbitMQ / bug 26742: in production message broker on a specific server ? Hi to all, I hope many of yours rember me (more then two years ago !!). I'm helping a library (in Italy) to update to Koha 20.11.x I read mailing list and bugs about addiction of RabbitMQ as task queue / message broker. I understand that all start from using Plack, if I use it there are problem with task queue. From 20.11.x if you use Plack, you need to use RabbitMQ, at least for batch update record tools. So, what is the suggestion for a production server ? To install always RabbitMQ in specific server ? Or is a specific server for RabbitMQ only for multi-instance installation ? I'm working with 250.000 bibliographic records and 1.700 users in single-instance installation. Cheers Zeno Tajoli -- Zeno Tajoli System Librarian ___ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Zeno Tajoli System Librarian ___ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] RabbitMQ / bug 26742: in production message broker on a specific server ?
Hi Zeno, I certainly do remember you! I think that you misunderstand a little bit. The RabbitMQ dependency is necessary for both PSGI/Plack and CGI Koha when doing the batch record updates. (Over time, we'll change other parts of Koha to use RabbitMQ for message passing to a background worker as well.) I admit that I'm not 100% sure what 20.11.x is going to look like. I've been advocating for running RabbitMQ on a separate server, as that is the best practice recommended by the RabbitMQ community, but most patches have required that RabbitMQ runs on the same host as Koha. For now, I would say just trust the Koha Debian packages to do the right thing. Or are you not using the Koha Debian packages? For what it's worth, I already run RabbitMQ on production servers collocated with Koha, as I created a local tool in Koha that uses RabbitMQ. It shouldn't be too much of a drama. David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -Original Message- From: Koha-devel On Behalf Of Zeno Tajoli Sent: Tuesday, 24 November 2020 10:15 AM To: koha-devel Subject: [Koha-devel] RabbitMQ / bug 26742: in production message broker on a specific server ? Hi to all, I hope many of yours rember me (more then two years ago !!). I'm helping a library (in Italy) to update to Koha 20.11.x I read mailing list and bugs about addiction of RabbitMQ as task queue / message broker. I understand that all start from using Plack, if I use it there are problem with task queue. From 20.11.x if you use Plack, you need to use RabbitMQ, at least for batch update record tools. So, what is the suggestion for a production server ? To install always RabbitMQ in specific server ? Or is a specific server for RabbitMQ only for multi-instance installation ? I'm working with 250.000 bibliographic records and 1.700 users in single-instance installation. Cheers Zeno Tajoli -- Zeno Tajoli System Librarian ___ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ ___ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] RabbitMQ / bug 26742: in production message broker on a specific server ?
Hi to all, I hope many of yours rember me (more then two years ago !!). I'm helping a library (in Italy) to update to Koha 20.11.x I read mailing list and bugs about addiction of RabbitMQ as task queue / message broker. I understand that all start from using Plack, if I use it there are problem with task queue. From 20.11.x if you use Plack, you need to use RabbitMQ, at least for batch update record tools. So, what is the suggestion for a production server ? To install always RabbitMQ in specific server ? Or is a specific server for RabbitMQ only for multi-instance installation ? I'm working with 250.000 bibliographic records and 1.700 users in single-instance installation. Cheers Zeno Tajoli -- Zeno Tajoli System Librarian ___ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
