Koha 20.11 - RabbitMQ and lock_dir
After our upgrade to Koha 20.11, we have noticed a couple of errors. I'm trying to track them down and understand the changes. - lockdir in XML configuration file I get a warning about lockdir missing from the XML file, even after adding the line. I added: <lockdir>/var/lock/koha</lockdir> to my /etc/koha-conf.xml file but the error is still showing up in the About Koha screen. Do I have to do something to clear it? Or did I miss something? - RabbitMQ as message broker Reading the documentation, the addition of RabbitMQ as a message broker is specifically done for PLACK. Do I really have to set up a local RabbitMQ or is there another workaround? What am I gaining that did not work before? Because adding another little piece of software is a bit of hassle. If it is needed, where do I find documentation on setup? The Wiki has nothing that I found to be worthwhile. And if it is not (yet) needed, then how do I remove the error? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra@nd.edu
Hello Tom, - Which error do you have on the about page? Did you create the directory? Are the permissions correct? Did you restart memcached? - About RabbitMQ, it's not mandatory so far, there is a fallback to run the jobs when they are "enqueued". In 20.05 it's only used for the batch record modification tool, but it will be used for other background jobs in the upcoming versions. Its main goal is to avoid the different problems we have with the way we fork background jobs in the current implementation (see 22417 related bug reports) and have them executed by a worker script. To have RabbitMQ works it should be as easy as rabbitmq-plugins enable rabbitmq_stomp service rabbitmq-server restart Let me know if you have additional questions. Regards, Jonathan Le ven. 12 mars 2021 à 20:51, Tom Hanstra <hanstra@nd.edu> a écrit :
After our upgrade to Koha 20.11, we have noticed a couple of errors. I'm trying to track them down and understand the changes.
- lockdir in XML configuration file
I get a warning about lockdir missing from the XML file, even after adding the line. I added:
<lockdir>/var/lock/koha</lockdir>
to my /etc/koha-conf.xml file but the error is still showing up in the About Koha screen. Do I have to do something to clear it? Or did I miss something?
- RabbitMQ as message broker
Reading the documentation, the addition of RabbitMQ as a message broker is specifically done for PLACK. Do I really have to set up a local RabbitMQ or is there another workaround? What am I gaining that did not work before? Because adding another little piece of software is a bit of hassle.
If it is needed, where do I find documentation on setup? The Wiki has nothing that I found to be worthwhile. And if it is not (yet) needed, then how do I remove the error?
Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra@nd.edu _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Thanks for the response, Johathan. I figured out the lockdir issue. There was an ownership problem that I could address. For the RabbitMQ piece, I have a separate RabbitMQ server which I would like to use. Where in the configuration files would I address setting this to be a separate RabbitMQ server? And then, something has to create the initial setup on that server. What sets that all up? I am not finding that documentation. Thanks, Tom On Mon, Mar 15, 2021 at 4:49 AM Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Hello Tom,
- Which error do you have on the about page? Did you create the directory? Are the permissions correct? Did you restart memcached?
- About RabbitMQ, it's not mandatory so far, there is a fallback to run the jobs when they are "enqueued". In 20.05 it's only used for the batch record modification tool, but it will be used for other background jobs in the upcoming versions. Its main goal is to avoid the different problems we have with the way we fork background jobs in the current implementation (see 22417 related bug reports) and have them executed by a worker script. To have RabbitMQ works it should be as easy as rabbitmq-plugins enable rabbitmq_stomp service rabbitmq-server restart
Let me know if you have additional questions.
Regards, Jonathan
Le ven. 12 mars 2021 à 20:51, Tom Hanstra <hanstra@nd.edu> a écrit :
After our upgrade to Koha 20.11, we have noticed a couple of errors. I'm trying to track them down and understand the changes.
- lockdir in XML configuration file
I get a warning about lockdir missing from the XML file, even after
the line. I added:
<lockdir>/var/lock/koha</lockdir>
to my /etc/koha-conf.xml file but the error is still showing up in the About Koha screen. Do I have to do something to clear it? Or did I miss something?
- RabbitMQ as message broker
Reading the documentation, the addition of RabbitMQ as a message broker is specifically done for PLACK. Do I really have to set up a local RabbitMQ or is there another workaround? What am I gaining that did not work before? Because adding another little piece of software is a bit of hassle.
If it is needed, where do I find documentation on setup? The Wiki has nothing that I found to be worthwhile. And if it is not (yet) needed,
adding then
how do I remove the error?
Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra@nd.edu _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- *Tom Hanstra* *Sr. Systems Administrator* hanstra@nd.edu
participants (2)
-
Jonathan Druart -
Tom Hanstra