[Koha] Koha common upgrades fails as rabbitmq service is not running

[Mike Lake]

Hi all

Thanks Mason :-) That looks like it has fixed the problem.

I added the message_broker section then rebooted. Now rabbitmq server is 
running, the About Koha page/Server and System information tabs show 
message broker rabitmq is running and no errors.
The upgrade from Koha 21.05.00-1 to 21.05.01-1 then went fine.

The username & password is literally "guest" I presume? It all seems to 
be working.

I did not see anywhere where there were directions to add that section 
to the conf file. There were mentions of it in the git commit and bugs 
section but nothing that told me as an admin "you need to do this .... 
before your next upgrade" :-)

Thanks from Mike.

On 2021-07-02 12:46, Mason James wrote:
> hi Mike
> upgrading from 21.05.00 to 21.05.01 is recommended
> 
> you are probably missing this new RMQ block in your instance's
> koha-conf.xml file
> 
>  <message_broker>
>    <hostname>localhost</hostname>
> <port>61613</port>
>    <username>guest</username>
>    <password>guest</password>
>    <vhost></vhost>
>  </message_broker>
> 
> check the /etc/koha/koha-conf-site.xml.in template file, as an example
> 
> then reboot
> 
> 
> On 1/07/21 11:34 pm, Mike Lake wrote:
>> Hi
>> 
>> Anyone had this problem? There is already a new Koha common 21.05.01-1 
>> which will probably have the same problem if I try and upgrade.
>> 
>> Mike
>> 
>> On 2021-06-26 22:24, Mike Lake wrote:
>>> Hi
>>> 
>>> I have a problem with our library and RabbitMQ.
>>> Koha version: 21.05.00.000 on Debian 9.13
>>> 
>>> During the latest update just tonight ....
>>> 
>>> Setting up koha-common (21.05.00-1) ...
>>> Upgrading database schema for library       <== this instance is 
>>> disabled
>>> Upgrading database schema for libtest2      <== this instance is 
>>> running OK
>>> Plugin configuration unchanged.
>>> ....
>>> Applying plugin configuration to rabbit at asf3... failed.
>>>   * Could not contact node rabbit at asf3.
>>>     Changes will take effect at broker restart.
>>>   * Options: --online  - fail if broker cannot be contacted.
>>>              --offline - do not try to contact broker.
>>>  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.
>>> 
>>> systemctl shows rabbitmq service is not running and it cannot start 
>>> because:
>>> 
>>> # cat /var/log/rabbitmq/startup_log
>>> ERROR: node with name "rabbit" already running on "asf3"
>>> 
>>> and in the intranet About Koha / System Information for instance 
>>> libtest2 says:
>>> 
>>>   Impossible to connect to the message broker
>>>   There is an error when trying to connect to the message broker
>>> (RabbitMQ), check the Koha log files.
>>>   Maybe it is not installed and configured correctly?
>>>   Contact your system administrator.
>>> 
>>> In /etc/rabbitmq/rabbitmq-env.conf  all options are commented out.
>>> 
>>> When this instance was installed last year there was nothing that
>>> suggested that this needed to be configured.
>>> 
>>> I also see in worker-output.log I'm getting:
>>> Error connecting to localhost:61613: Connection refused at
>>> /usr/share/perl5/Net/Stomp.pm line 26.
>>> 
>>> I'm not sure if this is a firewall issue or not. I am running the
>>> stock Debian fail2ban.
>>> 
>>> 
>>> Thanks
>> 
> 
> _______________________________________________
> 
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Mike