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

Michael Kuhn mik at adminkuhn.ch
Thu May 11 17:17:07 CEST 2023


Hi Costantino

You wrote:

 > Do not move /var/lib/rabbitmq directory, just its content

It seems to make no difference, since the content was recreated when 
trying to start rabbitmq-server anew:

root at koha:/var/lib# ls -al rabbitmq/
insgesamt 3860
drwxr-xr-x  3 rabbitmq rabbitmq    4096 11. Mai 17:03 .
drwxr-xr-x 33 root     root        4096 11. Mai 17:03 ..
-r--------  1 rabbitmq rabbitmq      20 11. Mai 00:00 .erlang.cookie
-rw-r-----  1 rabbitmq rabbitmq 3934248 11. Mai 17:13 erl_crash.dump
drwxr-x---  2 rabbitmq rabbitmq    4096 11. Mai 17:03 mnesia

These are the same files as movedto /BACKUPTMP:

root at koha:/var/lib# ls -al /BACKUPTMP/rabbitmq/
insgesamt 3860
drwxr-xr-x 3 rabbitmq rabbitmq    4096 11. Mai 15:10 .
drwxr-xr-x 3 root     root        4096 11. Mai 16:49 ..
-r-------- 1 rabbitmq rabbitmq      20 11. Mai 00:00 .erlang.cookie
-rw-r----- 1 rabbitmq rabbitmq 3934442 11. Mai 16:48 erl_crash.dump
drwxr-x--- 2 rabbitmq rabbitmq    4096 10. Apr 2021  mnesia

I would prefer to just forget about Koha 22.11.05-2 and try with Koha 
22.11.03-1, but I don't know how to do that when using Debian packages.

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




> Do not move /var/lib/rabbitmq directory, just its content
> 
> El 11-05-2023 11:52, Michael Kuhn escribió:
> 
>> Hi Costantino
>>
>> You wrote:
>>> Hi, try this: sudo service mysql stop sudo service rabbitmq-server 
>>> stop Create a "backup-temp" folder, move files from 
>>> /var/lib/rabbitmq/ Then start services again. sudo service mysql 
>>> start sudo service rabbitmq-server start
>> I did the following but it didn't help:
>>
>> koha at koha:  <mailto:koha at koha:>~$ sudo systemctl stop mysql
>> koha at koha:  <mailto:koha at koha:>~$ sudo systemctl stop rabbitmq-server
>> koha at koha:  <mailto:koha at koha:>~$ sudo mkdir /BACKUPTMP
>> koha at koha:  <mailto:koha at koha:>~$ sudo mv /var/lib/rabbitmq /BACKUPTMP
>> koha at koha:  <mailto:koha at koha:>~$ sudo systemctl start mysql
>> koha at koha:  <mailto:koha at 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.
>>
>> As said, the basic problem seems to be that package "koha-common"
>> 22.11.05-2 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 · Emik at adminkuhn.ch  <mailto:mik at adminkuhn.ch>  · Wwww.adminkuhn.ch  <http://www.adminkuhn.ch>
>>> El 11-05-2023 10:27, Michael Kuhn escribió:
>>>> 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 <mailto:mik at adminkuhn.ch> · W 
>>>> www.adminkuhn.ch <http://www.adminkuhn.ch> [1] koha at koha: 
>>>> <mailto: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: <mailto: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 
>>>> <https://www.debian.org/support> [2] ░░ ░░ 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 
>>>> <https://www.debian.org/support> [2] ░░ ░░ 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 
>>>> <https://www.debian.org/support> [2] ░░ ░░ 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 mailing list 
>>>> http://koha-community.org <http://koha-community.org> [3] 
>>>> Koha at lists.katipo.co.nz <mailto:Koha at lists.katipo.co.nz> 
>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha 
>>>> <https://lists.katipo.co.nz/mailman/listinfo/koha> [4]
> 
> -- 
> 
> *Costantino, Fernán*
> División Nuevas Tecnologías
> Biblioteca Central Francisco P. Moreno
> Universidad Nacional del Comahue
> Santa Fe y Leloir (Q8300) Neuquén Cap.- Tel 54(0299)4490398
> 




More information about the Koha-devel mailing list