Boot failed, segmentation fault (core dumped) on start-up

[V Z]

I stopped node using 'rabbitmqctl stop_app'. Then, after about 5 minutes, attempted to start it using 'rabbitmqctl start_app', and got this:

[root@svm2093pdv ~]# rabbitmqctl start_app
Starting node rabbit@svm2093pdv ...

BOOT FAILED
===========

Error description:
   badarg

Log files (may contain more information):
   /var/log/rabbitmq/rabbit@svm2093pdv.log
   /var/log/rabbitmq/rabbit@svm2093pdv-sasl.log

Stack trace:
   [{erlang,group_leader,[undefined,<5565.1305.17>],[]},
    {rabbit_log,with_local_io,1,[{file,"src/rabbit_log.erl"},{line,99}]},
    {rabbit,broker_start,0,[{file,"src/rabbit.erl"},{line,292}]},
    {rabbit,start_it,1,[{file,"src/rabbit.erl"},{line,300}]},
    {rpc,'-handle_call_call/6-fun-0-',5,[{file,"rpc.erl"},{line,206}]}]

Segmentation fault (core dumped)

The node did start, though, and is usable. Running 3.6.0 (erlang 18.2) on RedHat 4.4.7-16. Logs are attached. Thanks in advance!

[V Z]

Tried to stop it again with 'rabbitmqctl stop_app', and getting this:

[root@svm2093pdv ~]# rabbitmqctl stop_app

Stopping node rabbit@svm2093pdv ...

Error: {badarg,[{erlang,group_leader,[undefined,<5565.8143.17>],[]},

                {rabbit_log,with_local_io,1,

                            [{file,"src/rabbit_log.erl"},{line,99}]},

                {rabbit,stop,0,[{file,"src/rabbit.erl"},{line,322}]},

                {rpc,'-handle_call_call/6-fun-0-',5,

                     [{file,"rpc.erl"},{line,206}]}]}

The node is still running...

[V Z]

Tried to stop using 'rabbitmqctl stop' but the same result; node is still running, so cannot stop it at all.

[Michael Klishin]

This is a standard library problem: https://github.com/rabbitmq/rabbitmq-server/pull/747.

On Wed, May 4, 2016 at 2:56 AM, V Z <uvzu...@gmail.com> wrote:

Tried to stop using 'rabbitmqctl stop' but the same result; node is still running, so cannot stop it at all.

--
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

[V Z]

So, what's the solution, please? What do I need to do to be able to stop/start node again?

[Michael Klishin]

Restart the OS process, e.g. with Monit.

On Wed, May 4, 2016 at 5:33 AM, V Z <uvzu...@gmail.com> wrote:

So, what's the solution, please? What do I need to do to be able to stop/start node again?

--

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.

[V Z]

This is not running in Cloud Foundry. Shall I kill the process and then use 'rabbitmq-server' to start it?

[Michael Klishin]

You can do that or restart it e.g. using the `service` tool, depending on how RabbitMQ was installed.

The bottom line is: restart the Erlang VM.

On Wed, May 4, 2016 at 5:57 AM, V Z <uvzu...@gmail.com> wrote:

This is not running in Cloud Foundry. Shall I kill the process and then use 'rabbitmq-server' to start it?

--
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 an email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[V Z]

Ok. That worked. Thank you