<div dir="ltr">Thanks Emile,<div><br></div><div>I'm not sure what HiPE is, and I haven't been running any unusual plugins. There was an erl_crash.dump file, but it's dated from the early this month, so it may be from a previous crash.</div>
<div><br></div><div style>The server is running Centos 6.3 on XenServer. I think I need to look at the Linux VM itself and see if there's something which could be causing it to be unstable.</div><div style><br></div><div style>
Thanks for your advice!</div><div style><br></div><div style>-D</div><div style><br></div><div style><br></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jan 29, 2013 at 12:33 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi Dave,<br>
<br>
On 29/01/13 17:08, Dave Seltzer wrote:<br>
> Jan 29 11:51:41 egressqueue01 kernel: beam.smp[9371]: segfault at<br>
> fffffffffffffffe ip 00000000005419ba sp 00007f476bccad00 error 4 in<br>
> beam.smp[400000+214000]<br>
><br>
> Issuing a "/etc/init.d/rabbitmq start" brought the service back up, and<br>
> after a little while it started passing messages again.<br>
<br>
That should not be taken lightly. Segfaults in the VM should not happen<br>
with a default installation. If you are running or developing a plugin<br>
with code that runs in the VM then segfaults could occur as a result.<br>
They are also more likely when you enable HiPE. If you have HiPE enabled<br>
then turn it off and see if that makes a difference. In some cases<br>
hardware errors can be to blame, so make sure the server hardware is in<br>
good shape.<br>
<br>
If the segfault produced a core file then it should be possible to work<br>
out where the error occurred. It will most likely be produced in the<br>
working directory of the account that runs the broker. The information<br>
from the core file can be reported to the erlang-bugs mailing list, or<br>
we can forward it on your behalf. If the Erlang VM was not compiled with<br>
debugging information then there is probably little information to be<br>
gleaned from the core file. If the error is reproducible then it may be<br>
worth getting hold of an Erlang VM with debugging symbols.<br>
<br>
In some cases a erl_crash.dump file will be produced when the VM<br>
crashes. If you find one (probably also in the working directory of the<br>
account that runs the broker) then please compress and send it to us.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
-Emile<br>
<br>
<br><br></font></span></blockquote></div>
</div></div></div>