I have been trying to start RabbitMQ 3.5.6-1 on CentOS 7.
I have installed RabbitMQ 3.5.6-1 (from rabbitmq-server-3.5.6-1.noarch.rpm) on CentOS 7.
RabbitMQ fails to start showing errors shown (briefly) at the end of this email.
A look into SELinux log file shows "avc denied" (errors below).
How can I remedy this issue.
#grep -e denied /var/log/audit/audit.log
type=AVC msg=audit(1446475116.096:6602): avc: denied { read } for pid=30524 comm="beam.smp" name=".erlang.cookie" dev="zfs" ino=63754 scontext=system_u:system_r:rabbitmq_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file
type=AVC msg=audit(1446475116.096:6603): avc: denied { read } for pid=30525 comm="beam.smp" name=".erlang.cookie" dev="zfs" ino=63754 scontext=system_u:system_r:rabbitmq_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file
type=AVC msg=audit(1446475116.611:6604): avc: denied { add_name } for pid=30579 comm="beam.smp" name="erl_crash.dump" scontext=system_u:system_r:rabbitmq_t:s0 tcontext=unconfined_u:object_r:unlabeled_t:s0 tclass=dir
type=AVC msg=audit(1446475577.682:6706): avc: denied { read } for pid=32660 comm="beam.smp" name=".erlang.cookie" dev="zfs" ino=3173010 scontext
#sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 28
[Errors on RabbitMQ start are shown below]
etrieving
http://packages.erlang-solutions.com/erlang-solutions-1.0-1.noarch.rpmPreparing... ################################# [100%]
package erlang-solutions-1.0-1.noarch is already installed
Preparing... ################################# [100%]
Updating / installing...
1:rabbitmq-server-3.5.6-1 ################################# [100%]
Starting rabbitmq-server (via systemctl): Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.
[FAILED]
Mon Nov 2 17:46:19 AST 2015
Plugin configuration unchanged.
Applying plugin configuration to rabbit@somecomputer... failed.
* Could not contact node rabbit@somecomputer.
Changes will take effect at broker restart.
* Options: --online - fail if broker cannot be contacted.
--offline - do not try to contact broker.
Mon Nov 2 17:46:19 AST 2015
Error: unable to connect to node rabbit@somecomputer: nodedown
DIAGNOSTICS
===========
attempted to contact: [rabbit@somecomputer]
rabbit@somecomputer:
* connected to epmd (port 4369) on somecomputer
* epmd reports: node 'rabbit' not running at all
no other nodes on somecomputer
* suggestion: start the node
current node details:
- node name: 'rabbitmq-cli-33119@somecomputer'
- home dir: /var/lib/rabbitmq
- cookie hash: i6io7eruUKNmXyHsdfbNAQ==
....
Regards,
Allan.