abbitmq-server-3.4.3 could not write core file rabbit@rabbitmqNode0/schema.TMP when restart
822 views
Skip to first unread message
yi ya
Aug 12, 2015, 11:13:09 PM8/12/15
to rabbitmq-users
Here is the steps:
1,stop rabbitmq-server
2,use 'rabbitmq-server -detached' to start rabbitmq-server
3,try to use 'rabbitmqctl change_password' to change password.
4,try to use 'rabbitmqctl status' to get rabbitmq-server status, if not ok, go to step 3.until it's status is ok.
when I restart rabbitmq-server, some error appear.
The time is 7-Aug-2015::03:51:02 to 7-Aug-2015::03:51:14.
I have two log file: rab...@rabbitmqNode0-sasl.log, rab...@rabbitmqNode0.log
rab...@rabbitmqNode0-sasl.log 7-Aug-2015::03:51:02 mnesia_kernel_sup child_terminated ,shutdown
rab...@rabbitmqNode0.log 7-Aug-2015::03:51:02 "Open of file before dump to disc failed",{file_error,"/opt/platform/data/rabbitmq/rabbit@rabbitmqNode0/schema.TMP",eacces}}
rab...@rabbitmqNode0.log 7-Aug-2015::03:51:02 Schema update error
rab...@rabbitmqNode0-sasl.log 7-Aug-2015::03:51:14 exception exit: killed in function gen_server:terminate/6 (gen_server.erl, line 737)
rab...@rabbitmqNode0.log 7-Aug-2015::03:51:14 Generic server mnesia_monitor terminating
rab...@rabbitmqNode0.log 7-Aug-2015::03:51:14 mnesia_event got unexpected event: {'EXIT',<0.60.0>,killed}
rab...@rabbitmqNode0-sasl.log
Enter code here...=SUPERVISOR REPORT==== 7-Aug-2015::03:50:31 === Supervisor: {<0.30938.0>,amqp_connection_sup}
Context: child_terminated
Reason: {remote_node_down,shutdown}
Offender: [{pid,<0.30940.0>},
{name,connection},
{mfargs,
{amqp_gen_connection,start_link,
[<0.30939.0>,
{amqp_params_direct,<<"rabbit">>,
<<"Sphere123">>,<<"/">>,
rabbit@rabbitmqNode0,none,[]}]}},
{restart_type,intrinsic},
{shutdown,brutal_kill},
{child_type,worker}]
=SUPERVISOR REPORT==== 7-Aug-2015::03:50:31 ===
Supervisor: {<0.30938.0>,amqp_connection_sup}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.30940.0>},
{name,connection},
{mfargs,
{amqp_gen_connection,start_link,
[<0.30939.0>,
{amqp_params_direct,<<"rabbit">>,
<<"Sphere123">>,<<"/">>,
rabbit@rabbitmqNode0,none,[]}]}},
{restart_type,intrinsic},
{shutdown,brutal_kill},
{child_type,worker}]
=SUPERVISOR REPORT==== 7-Aug-2015::03:51:02 ===
Supervisor: {local,mnesia_kernel_sup}
Context: child_terminated
Reason: killed
Offender: [{pid,<0.61.0>},
{name,mnesia_locker},
{mfargs,{mnesia_locker,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=SUPERVISOR REPORT==== 7-Aug-2015::03:51:02 ===
Supervisor: {local,mnesia_kernel_sup}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.61.0>},
{name,mnesia_locker},
{mfargs,{mnesia_locker,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=CRASH REPORT==== 7-Aug-2015::03:51:14 ===
crasher:
initial call: mnesia_recover:init/1
pid: <0.62.0>
registered_name: mnesia_recover
exception exit: killed
in function gen_server:terminate/6 (gen_server.erl, line 737)
ancestors: [mnesia_kernel_sup,mnesia_sup,<0.55.0>]
messages: []
links: []
dictionary: []
trap_exit: true
status: running
heap_size: 610
stack_size: 27
reductions: 575
neighbours:
=CRASH REPORT==== 7-Aug-2015::03:51:14 ===
crasher:
initial call: gen_event:init_it/6
pid: <0.57.0>
registered_name: mnesia_event
exception exit: killed
in function gen_event:terminate_server/4 (gen_event.erl, line 304)
ancestors: [mnesia_sup,<0.55.0>]
messages: []
links: []
dictionary: []
trap_exit: true
status: running
heap_size: 10958
stack_size: 27
reductions: 1089
neighbours:
=CRASH REPORT==== 7-Aug-2015::03:51:14 ===
crasher:
initial call: mnesia_monitor:init/1
pid: <0.59.0>
registered_name: mnesia_monitor
exception exit: killed
in function gen_server:terminate/6 (gen_server.erl, line 737)
ancestors: [mnesia_kernel_sup,mnesia_sup,<0.55.0>]
messages: []
links: [<3079.63.0>,<0.125.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 2586
stack_size: 27
reductions: 2391
neighbours:
=CRASH REPORT==== 7-Aug-2015::03:51:14 ===
crasher:
initial call: application_master:init/4
pid: <0.54.0>
registered_name: []
exception exit: killed
in function application_master:terminate/2 (application_master.erl, line 227)
ancestors: [<0.53.0>]
messages: []
links: [<0.7.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 610
stack_size: 27
reductions: 42424
neighbours:
=SUPERVISOR REPORT==== 7-Aug-2015::06:47:55 ===
Supervisor: {<0.28497.118>,amqp_channel_sup_sup}
Context: shutdown_error
Reason: shutdown
Offender: [{nb_children,1},
{name,channel_sup},
{mfargs,
{amqp_channel_sup,start_link,
[direct,<0.28496.118>,
<<"<rab...@rabbitmqNode0.2.28496.118>">>]}},
{restart_type,temporary},
{shutdown,brutal_kill},
{child_type,supervisor}]
=INFO REPORT==== 7-Aug-2015::03:51:01 ===node : rabbit@rabbitmqNode0home dir : /usr/local/lib/rabbitmqconfig file(s) : /usr/local/lib/rabbitmq/sbin/../etc/rabbitmq/rabbitmq.configcookie hash : P7Imk5s8lUeR70yzdvPyDA==log : /var/log/sphere/component/rabbitmq/rab...@rabbitmqNode0.logsasl log : /var/log/sphere/component/rabbitmq/rab...@rabbitmqNode0-sasl.logdatabase dir : /opt/platform/data/rabbitmq/rabbit@rabbitmqNode0
=INFO REPORT==== 7-Aug-2015::03:51:02 ===Limiting to approx 44900 file handles (40408 sockets)
=INFO REPORT==== 7-Aug-2015::03:51:02 ===Node 'rabbit@rabbitmqNode1' selected for auto-clustering
=ERROR REPORT==== 7-Aug-2015::03:51:02 ===Mnesia(rabbit@rabbitmqNode0): ** ERROR ** (could not write core file: eacces) ** FATAL ** Schema update error {"Open of file before dump to disc failed", {file_error, "/opt/platform/data/rabbitmq/rabbit@rabbitmqNode0/schema.TMP", eacces}} [{op,merge_schema, [{name, mirrored_sup_childspec}, {type,ordered_set}, {ram_copies, ..................... {version, {{7,0}, {rabbit@rabbitmqNode0, {1438,890662, 601552}}}}]}]=ERROR REPORT==== 7-Aug-2015::03:51:04 ===Mnesia(rabbit@rabbitmqNode0): ** ERROR ** (ignoring core) ** FATAL ** Schema update error {function_clause, [{mnesia_dumper, insert_op, [{tid, .......................... {rabbit@rabbitmqNode0, {1438, 890662, 601552}}}}]}]=INFO REPORT==== 7-Aug-2015::03:51:05 ===Changing password for 'rabbit'
=INFO REPORT==== 7-Aug-2015::03:51:07 ===Changing password for 'rabbit'
=ERROR REPORT==== 7-Aug-2015::03:51:14 ===** Generic server mnesia_monitor terminating ** Last message in was {'EXIT',<0.58.0>,killed}** When Server state == {state,<0.58.0>,[],[],true,[],undefined,[],[]}** Reason for termination == ** killed
=ERROR REPORT==== 7-Aug-2015::03:51:14 ===** Generic server mnesia_recover terminating ** Last message in was {'EXIT',<0.58.0>,killed}** When Server state == {state,<0.58.0>,undefined,undefined,undefined,0,false, true,[]}** Reason for termination == ** killed
=ERROR REPORT==== 7-Aug-2015::03:51:14 ===Mnesia(rabbit@rabbitmqNode0): ** ERROR ** mnesia_event got unexpected event: {'EXIT', <0.60.0>, killed}
=INFO REPORT==== 7-Aug-2015::04:34:08 ===Starting RabbitMQ 3.4.3 on Erlang 17.3Copyright (C) 2007-2014 GoPivotal, Inc.Licensed under the MPL. See http://www.rabbitmq.com/yi ya
Aug 12, 2015, 11:22:19 PM8/12/15
to rabbitmq-users
why it cann't write /opt/platform/data/rabbitmq/rabbit@rabbitmqNode0/schema.TMP ? Does it matter with mnesia's shutdown?
Michael Klishin
Aug 13, 2015, 4:22:50 AM8/13/15
to rabbitm...@googlegroups.com
EACCESS means RabbitMQ process could not write or reads to/from a file. Make sure you run it with effective user that has sufficient permissions to do that, for example.
why it cann't write /opt/platform/data/rabbitmq/rabbit@rabbitmqNode0/schema.TMP ? Does it matter with mnesia's shutdown?
--
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.
yi ya
Aug 13, 2015, 9:01:48 AM8/13/15
to rabbitmq-users
The user is rabbitmq and it's dir '/opt/fusionplatform/data/rabbitmq/rabbit@rabbitmqNode0 ' is also rabbitmq.
We will delete the floder when stop rabbitmq and create the floder before start rabbitmq.
So the floder's permissions is OK. Just this time's restart is error,it's normal before.
Michael Klishin
Aug 13, 2015, 9:04:20 AM8/13/15
to rabbitm...@googlegroups.com, yi ya
On 13 August 2015 at 16:01:52, yi ya (yiya1...@gmail.com) wrote:
> The user is rabbitmq and it's dir '/opt/fusionplatform/data/rabbitmq/rabbit@rabbitmqNode0
> ' is also rabbitmq.
> We will delete the floder when stop rabbitmq and create the floder
> before start rabbitmq.
> So the floder's permissions is OK. Just this time's restart is
> error,it's normal before.
EACCESS is unambiguous: Erlang/OTP could not open a file (seemingly for writing).
> The user is rabbitmq and it's dir '/opt/fusionplatform/data/rabbitmq/rabbit@rabbitmqNode0
> ' is also rabbitmq.
> We will delete the floder when stop rabbitmq and create the floder
> before start rabbitmq.
> So the floder's permissions is OK. Just this time's restart is
> error,it's normal before.
Permissions is just one possible cause of that.
--
MK
Staff Software Engineer, Pivotal/RabbitMQ
yiya1989
Aug 13, 2015, 9:45:43 AM8/13/15
to rabbitmq-users, yiya1...@gmail.com
Thanks for your replay. Two questions.
First one, Is there any possible the schema.TMP is write by some progress,but the progress is crashed. So the another try to read it,but it cann't read it ?
Another question is: schema.TMP is write by which module? Is it rabbit_mnesia.erl ?
Michael Klishin
Aug 13, 2015, 9:58:11 AM8/13/15
to rabbitm...@googlegroups.com, yiya1989
On 13 August 2015 at 16:45:46, yiya1989 (yiya1...@gmail.com) wrote:
> First one, Is there any possible the schema.TMP is write by some
> progress,but the progress is crashed. So the another try to read
> it,but it cann't read it ?
That wouldn't result in an EACCESS. EACCESS means the OS prevented RabbitMQ process
> First one, Is there any possible the schema.TMP is write by some
> progress,but the progress is crashed. So the another try to read
> it,but it cann't read it ?
from even opening a file.
> Another question is: schema.TMP is write by which module? Is
> it rabbit_mnesia.erl ?
Reply all
Reply to author
Forward
0 new messages