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@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