[rabbitmq-discuss] RabbitMQ Crash in 3.0.1

Emile Joubert emile at rabbitmq.com
Tue Jan 29 17:33:09 GMT 2013

Hi Dave,

On 29/01/13 17:08, Dave Seltzer wrote:
> Jan 29 11:51:41 egressqueue01 kernel: beam.smp[9371]: segfault at
> fffffffffffffffe ip 00000000005419ba sp 00007f476bccad00 error 4 in
> beam.smp[400000+214000]
> Issuing a "/etc/init.d/rabbitmq start" brought the service back up, and
> after a little while it started passing messages again.

That should not be taken lightly. Segfaults in the VM should not happen
with a default installation. If you are running or developing a plugin
with code that runs in the VM then segfaults could occur as a result.
They are also more likely when you enable HiPE. If you have HiPE enabled
then turn it off and see if that makes a difference. In some cases
hardware errors can be to blame, so make sure the server hardware is in
good shape.

If the segfault produced a core file then it should be possible to work
out where the error occurred. It will most likely be produced in the
working directory of the account that runs the broker. The information
from the core file can be reported to the erlang-bugs mailing list, or
we can forward it on your behalf. If the Erlang VM was not compiled with
debugging information then there is probably little information to be
gleaned from the core file. If the error is reproducible then it may be
worth getting hold of an Erlang VM with debugging symbols.

In some cases a erl_crash.dump file will be produced when the VM
crashes. If you find one (probably also in the working directory of the
account that runs the broker) then please compress and send it to us.


More information about the rabbitmq-discuss mailing list