Docker container Permission issue (rabbitmq:3-management)

7,954 views
Skip to first unread message

AJ NOURI

unread,
May 28, 2016, 9:34:56 PM5/28/16
to rabbitmq-users


First start of rabbitmq server process on Docker container, the offficial docker hub repository rabbitmq:3-management

Problem with permission

# /usr/sbin/rabbitmq-server
/usr/lib/rabbitmq/bin/rabbitmq-server: 49: /usr/lib/rabbitmq/bin/rabbitmq-server: cannot create /var/lib/rabbitmq/mnesia/rab...@rabbitmq-srv-1.pid: Permission denied
Failed to write pid file: /var/lib/rabbitmq/mnesia/rab...@rabbitmq-srv-1.pid

# su root
root@rabbitmq-srv-1:/# /usr/sbin/rabbitmq-server
/usr/lib/rabbitmq/bin/rabbitmq-server: 49: /usr/lib/rabbitmq/bin/rabbitmq-server: cannot create /var/lib/rabbitmq/mnesia/rab...@rabbitmq-srv-1.pid: Permission denied
Failed to write pid file: /var/lib/rabbitmq/mnesia/rab...@rabbitmq-srv-1.pid


Did I miss something?

AJ NOURI

unread,
May 28, 2016, 9:58:56 PM5/28/16
to rabbitmq-users
OK, I was using the wrong file

Now

root@rabbitmq-srv-1:/# /etc/init.d/rabbitmq-server start
[warn] Starting message broker: rabbitmq-server[....] FAILED - check /var/log/rabbitmq/startup_\{log, _err\} ... (warning).
 failed!

root@rabbitmq-srv-1:/# cat /var/log/rabbitmq/startup_err

Crash dump is being written to: erl_crash.dump...Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Error when reading /var/lib/rabbit


root@rabbitmq-srv-1:/# cat /var/log/rabbitmq/startup_log
{error_logger,{{2016,5,29},{1,54,5}},"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",[]}
{error_logger,{{2016,5,29},{1,54,5}},crash_report,[[{initial_call,{auth,init,['Argument__1']}},{pid,<0.21.0>},{registered_name,[]},{error_info,{exit,{"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,352}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}},{ancestors,[net_sup,kernel_sup,<0.10.0>]},{messages,[]},{links,[<0.19.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,27},{reductions,636}],[]]}
{error_logger,{{2016,5,29},{1,54,5}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}},{offender,[{pid,undefined},{id,auth},{mfargs,{auth,start_link,[]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2016,5,29},{1,54,5}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{shutdown,{failed_to_start_child,auth,{"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}}}},{offender,[{pid,undefined},{id,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2016,5,29},{1,54,5}},crash_report,[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.9.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}}}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,134}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}},{ancestors,[<0.8.0>]},{messages,[{'EXIT',<0.10.0>,normal}]},{links,[<0.8.0>,<0.7.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,27},{reductions,181}],[]]}
{error_logger,{{2016,5,29},{1,54,5}},std_info,[{application,kernel},{exited,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",[{auth,init_cookie,0,[{file,"auth.erl"},{line,286}]},{auth,init,1,[{file,"auth.erl"},{line,140}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}}}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{\"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces\",[{auth,init_cookie,0,[{file,\"auth.erl\"},{line,286}]},{auth,init,1,[{file,\"auth.erl\"},{line,140}]},{gen_server,init_it,6,[{file,\"gen_server.erl\"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,240}]}]}}}}},{kernel,start,[normal,[]]}}}"}

Michael Klishin

unread,
May 29, 2016, 4:16:02 AM5/29/16
to rabbitm...@googlegroups.com
EACCESS is fairly unambiguous

AJ NOURI

unread,
May 29, 2016, 10:19:09 PM5/29/16
to rabbitmq-users
Checked the file permission:

ls -l var/lib/rabbitmq/.erlang.cookie
-r-------- 1 root root 20 May 29 00:00 var/lib/rabbitmq/.erlang.cookie

Added all permissions to root user only("Cookie file /var/lib/rabbitmq/.erlang.cookie must be accessible by owner only")

chmod 700 /var/lib/rabbitmq/.erlang.cookie
root@rabbitmq-srv-1:/# ls -l var/lib/rabbitmq/.erlang.cookie
-rwx------ 1 root root 20 May 29 00:00 var/lib/rabbitmq/.erlang.cookie

Resulting in the exact same error

Michael Klishin

unread,
May 30, 2016, 2:16:06 AM5/30/16
to rabbitm...@googlegroups.com
RabbitMQ does not run as root when installed from packages. Nobody should run it as root, period.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Alpha Shuro

unread,
Sep 8, 2016, 5:06:26 AM9/8/16
to rabbitmq-users
I am not running rabbit as root, i'm just trying to fire up the container, and i am getting this error

Gabriel Silva

unread,
May 9, 2017, 3:24:54 PM5/9/17
to rabbitmq-users
Are you trying to starting up the container with volume parameters? Maybe you don't have permissions in your host files.
You could remove volume links and try again
Reply all
Reply to author
Forward
0 new messages