eacces (permission denied) error preventing RabbitMQ node from starting.

Products

• Support Only for OpenSource RabbitMQ

Issue/Introduction

RabbitMQ nodes bind to ports (open server TCP sockets) in order to accept client and CLI tool connections. An eacces (permission denied) error as shown in the example below, is generated when binding to a socket is denied due to insufficient permissions at the OS level or is blocked by processes or tools. This can prevent nodes from starting. Read more about it here- https://www.rabbitmq.com/install-debian.html#ports.

 [info] <0.1700.0> Management plugin: HTTP (non-TLS) listener started on port 15672
 [info] <0.1730.0> Statistics database started.
 [info] <0.1729.0> Starting worker pool 'management_worker_pool' with 3 processes in    it
 [info] <0.1740.0> rabbit_stomp: default user 'guest' enabled
 [info] <0.1759.0> started STOMP TCP listener on [::]:61613 
 [error] <0.1766.0> Failed to start Ranch listener {acceptor,{0,0,0,0},61613} in ranch_tcp:listen(#{connection_type => supervisor,handshake_timeout => 5000,max_connections => infinity,num_acceptors => 10,num_conns_sups => 1,socket_opts => [{cacerts,'...'},{key,'...'},{cert,'...'},{ip,{0,0,0,0}},{port,61613},inet,{backlog,128},{nodelay,true}]})
for reason eacces (permission denied)

Resolution

This can be prevented by having appropriate OS level permissions and security settings. Also verify if you have processes and tools  preventing RabbitMQ from binding to ports. An example of such a tool for a Linux environment would be SELinux. This error is out of scope for the RabbitMQ support team as the product doesn't set or override OS level permissions.