[Koha] [Koha-devel] Starting rabbitmq-server fails with Koha 22.11.05-2

[Michael Kuhn]

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 at koha:~$ sudo systemctl rabbitmq-server stop
Unknown command verb rabbitmq-server.
koha at 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
-- 
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 at adminkuhn.ch · W www.adminkuhn.ch



Am 11.05.23 um 16:08 schrieb Jonathan Druart:
> 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
> Looks like it's not started so it won't certainly help.
> Rebooted the VM? Do you have elastic running as well (in such case 4G
> of RAM won't be enough)
> 
> Le jeu. 11 mai 2023 à 15:27, Michael Kuhn <mik at adminkuhn.ch> a écrit :
>>
>> Hi
>>
>> When trying to install Koha 22.11.05-2 via package installation on a
>> completely new machine with 4 virtual CPUs, 4 GB RAM and Debian
>> GNU/Linux 11 the following error appears:
>>
>>
>> rabbitmq-server (3.8.9-3) wird eingerichtet ...
>> 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
>> 2023-05-11 15:14:44 CEST; 4ms ago
>>       Process: 38141 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server
>> (code=exited, status=1/FAILURE)
>>      Main PID: 38141 (code=exited, status=1/FAILURE)
>>           CPU: 1.071s
>>
>> Mai 11 15:14:44 koha systemd[1]: Failed to start RabbitMQ Messaging Server.
>> Mai 11 15:14:44 koha systemd[1]: rabbitmq-server.service: Consumed
>> 1.071s CPU time.
>>
>>
>> Can someone please tell me how to solve this problem?
>>
>> You can see the output of "systemctl status rabbitmq-server.service"
>> resp. "journalctl -xe" just below.
>>
>> 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 at adminkuhn.ch · W www.adminkuhn.ch
>>
>>
>>
>>
>> koha at koha:~$ sudo systemctl status rabbitmq-server.service
>> ● 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
>> 2023-05-11 15:19:57 CEST; 3s ago
>>       Process: 41298 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server
>> (code=exited, status=1/FAILURE)
>>      Main PID: 41298 (code=exited, status=1/FAILURE)
>>           CPU: 1.066s
>>
>> koha at koha:~$ sudo journalctl -xe
>> ░░ An ExecStart= process belonging to unit rabbitmq-server.service has
>> exited.
>> ░░
>> ░░ The process' exit code is 'exited' and its exit status is 1.
>> Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Failed with
>> result 'exit-code'.
>> ░░ Subject: Unit failed
>> ░░ Defined-By: systemd
>> ░░ Support: https://www.debian.org/support
>> ░░
>> ░░ The unit rabbitmq-server.service has entered the 'failed' state with
>> result 'exit-code'.
>> Mai 11 15:20:47 koha systemd[1]: Failed to start RabbitMQ Messaging Server.
>> ░░ Subject: A start job for unit rabbitmq-server.service has failed
>> ░░ Defined-By: systemd
>> ░░ Support: https://www.debian.org/support
>> ░░
>> ░░ A start job for unit rabbitmq-server.service has finished with a failure.
>> ░░
>> ░░ The job identifier is 3262 and the job result is failed.
>> Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Consumed
>> 1.127s CPU time.
>> ░░ Subject: Resources consumed by unit runtime
>> ░░ Defined-By: systemd
>> ░░ Support: https://www.debian.org/support
>> ░░
>> ░░ The unit rabbitmq-server.service completed and consumed the indicated
>> resources.
>> Mai 11 15:20:48 koha sudo[41974]:     koha : TTY=pts/0 ; PWD=/home/koha
>> ; USER=root ; COMMAND=/usr/bin/journalctl -xe
>> Mai 11 15:20:48 koha sudo[41974]: pam_unix(sudo:session): session opened
>> for user root(uid=0) by koha(uid=1000)
>>
>>
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at 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/