Bug 1340275 - rabbitmq-server does not start on a fresh Fedora 24 installation
Summary: rabbitmq-server does not start on a fresh Fedora 24 installation
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitmq-server
Version: 24
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-26 22:37 UTC by Randy Barlow
Modified: 2017-03-09 21:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-09 15:00:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Randy Barlow 2016-05-26 22:37:27 UTC
Description of problem:
I installed rabbitmq-server and tried to start it, but it failed to start.


Version-Release number of selected component (if applicable):
rabbitmq-server-3.6.2-1.fc24.noarch


How reproducible:
Every time.


Steps to Reproduce:
1. $ sudo dnf install rabbitmq-server
2. $ sudo systemctl start rabbitmq-server


Actual results:
$ 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.


Expected results:
It should start successfully.


Additional info:
There seem to be some AVC denials:

$ sudo audit2allow -al


#============= init_t ==============
allow init_t rabbitmq_var_lib_t:file getattr;
allow init_t rabbitmq_var_log_t:file getattr;
allow init_t unconfined_service_t:tcp_socket create;

$ sudo grep rabbit /var/log/audit/audit.log
type=AVC msg=audit(1464301890.501:728): avc:  denied  { getattr } for  pid=5944 comm="rabbitmqctl" path="/var/log/rabbitmq/rabbit" dev="vda1" ino=142758 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:rabbitmq_var_log_t:s0 tclass=file permissive=0
type=AVC msg=audit(1464301890.501:729): avc:  denied  { getattr } for  pid=5944 comm="rabbitmqctl" path="/var/log/rabbitmq/rabbit" dev="vda1" ino=142758 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:rabbitmq_var_log_t:s0 tclass=file permissive=0
type=SERVICE_START msg=audit(1464301891.682:730): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rabbitmq-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Comment 1 Randy Barlow 2016-06-09 15:00:14 UTC
I tried this again more recently and it worked, so I'm going to mark this as fixed.

Comment 2 Peter "Pessoft" Kolínek 2017-03-09 21:38:58 UTC
I just encountered similar issue ( on Fedora 25 ), which has been caused by unresolvable hostname. In your case probably rbarlow-install-f24 could not resolve to IP address correctly.


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