[rabbitmq-discuss] segfault in beam.smp

Jose Jimenez Ortiz j-jimenez at finamex.com.mx
Thu Oct 31 16:47:58 GMT 2013

Guys, first of all, thanks for your prompt answers. I will start with Michael suggestion on upgrading Erlang relase.

And on Emile comments, well, will do the tests, initially it seems ok, no alerts/errors at any level. Yes right, no point to mention the three year idea. But anyway, kernel is the same on other stable nodes with HIPE as default, who knows. But still will try to increase the log level of the kernel.

Let you know if I have some other answers,

-----Mensaje original-----
De: Emile Joubert [mailto:emile at rabbitmq.com]
Enviado el: Jueves, 31 de Octubre de 2013 09:42
Para: Jose Jimenez Ortiz
CC: Discussions about RabbitMQ; Michael Klishin
Asunto: Re: [rabbitmq-discuss] segfault in beam.smp


On 31/10/13 15:24, Michael Klishin wrote:
> On 31 Oct 2013, at 19:11, Jose Jimenez Ortiz
>> Does anyone know how to fix this? Is it related to current version?
>> Is there a way to increase log level on rabbit to try to analyze the
>> problem?
> Segfaults is ultimately an Erlang runtime problem. Give Erlang 16B02 a
> try.

To add to what Michael says, there are a few more things you could do:

Check that you don't have HiPE turned on. HiPE can occasionally lead to problems.

Validate the hardware. Run a memory stress-test. Check whether the error can be repeated on different hardware.

That kernel is pretty recent. The 3 years of stable running could not have been on such a new kernel. Have you ruled out the admittedly unlikely possibility of a kernel issue?


Este correo electr?nico y sus anexos pueden contener informaci?n CONFIDENCIAL para uso exclusivo de su destinatario. Si ha recibido este correo por error, por favor, notif?quelo al remitente y b?rrelo de su sistema junto con los archivos que en su caso se anexen. Las opiniones expresadas en este correo son las de su autor y no son necesariamente compartidas o apoyadas por la compa??a. Cualquier opini?n, propuesta o recomendaci?n aqu? contenida est? sujeta a las condiciones regulatorias que resulten aplicables y a los acuerdos comerciales, contratos y dem?s documentos suscritos con el destinatario y/o con la empresa que representa. No se garantiza que la transmisi?n de este correo sea segura o libre de errores, podr?a haber sido viciada, perdida, destruida, haber llegado tarde, de forma incompleta o contener VIRUS.

This e-mail w/attachments is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. The opinions expressed in this e-mail are not necessarily shared or supported by the Company. Any opinion, suggestion or recommendation written in this e-mail will be subject to regulatory conditions, commercial agreements, copyright laws, contracts and any other agreement signed with the addressee and/or the Company that the addressee represents. The transmission of this e-mail cannot be guaranteed to be secure or virus free, the transmission could be vitiated, lost, destroyed, delayed, incomplete or may contain virus.

More information about the rabbitmq-discuss mailing list