Bug 1486564 - Rabbitmq-Server does not start automatically at boot of a VM
Summary: Rabbitmq-Server does not start automatically at boot of a VM
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rabbitmq-server
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-30 07:29 UTC by Yann ILAS
Modified: 2024-07-09 02:12 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 02:12:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output of journalctl -b output + add of "set -x" on startup script (3.82 KB, text/plain)
2017-08-30 07:29 UTC, Yann ILAS
no flags Details

Description Yann ILAS 2017-08-30 07:29:39 UTC
Created attachment 1319887 [details]
Output of journalctl -b output + add of "set -x" on startup script

Description of problem:
The RabbitMQ server does not start at the boot of a VM. Indeed, the network service is not finished yet when the rabbitmq-server starts. It means that the network interfaces are not UP when the daemon starts.
The deamon tries to bind to network interface which are not yet started.


Version-Release number of selected component (if applicable):
# rpm -q rabbitmq-server
rabbitmq-server-3.6.9-1.el7.noarch


How reproducible:
Always

Steps to Reproduce:
1. Restart the server/VM
2. The daemon does not start


Actual results:

The daemon does not start. The journalctl -b output is :

Aug 29 15:34:19 XXXXXXXXXXXXXXXXX rabbitmq-server[788]: ERROR: epmd error for host XXXXXXXXXXXXXXXXX: address (cannot connect to host/port)
Aug 29 15:34:19 XXXXXXXXXXXXXXXXX systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX systemd[1]: Cannot find unit for notify message of PID 1357.
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX systemd[1]: Cannot find unit for notify message of PID 1358.
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX systemd[1]: Cannot find unit for notify message of PID 1361.
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: Stopping and halting node rabbit@XXXXXXXXXXXXXXXXX ...
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: Error: unable to connect to node rabbit@XXXXXXXXXXXXXXXXX: nodedown
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: DIAGNOSTICS
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: ===========
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: attempted to contact: [rabbit@XXXXXXXXXXXXXXXXX]
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: rabbit@XXXXXXXXXXXXXXXXX:
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: * unable to connect to epmd (port 4369) on XXXXXXXXXXXXXXXXX: address (cannot connect to host/port)
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: current node details:
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: - node name: 'rabbitmq-cli-58@XXXXXXXXXXXXXXXXX'
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: - home dir: .
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX rabbitmqctl[1230]: - cookie hash: iSYBjA9VPehmSB31MGQTSQ==
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX systemd[1]: Failed to start RabbitMQ broker.
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX systemd[1]: Unit rabbitmq-server.service entered failed state.
Aug 29 15:34:20 XXXXXXXXXXXXXXXXX systemd[1]: rabbitmq-server.service failed.


Expected results:

[root@l1vrpsatqsses01 system]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2017-08-29 16:43:17 CEST; 16h ago


Additional info:

As the RabbitMQ-server tries to bind to network interfaces, I suggest to change the "after" to network-online.target instead of network.target in the file rabbitmq-server.service

Comment 1 Troy Dawson 2024-07-09 02:12:00 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.


Note You need to log in before you can comment on or make changes to this bug.