<div dir="ltr"><div><div>Yep, the VM is segfaulting (it exits with the message "Segmentation fault (core dumped)").<br><br></div><div>The message in the logs reads:<br><br>** Generic server rabbit_mgmt_external_stats terminating <br>
** Last message in was emit_update<br>** When Server state == {state,707130}<br>** Reason for termination == <br>** {function_clause,[{lists,nth,[1,[]],[{file,"lists.erl"},{line,168}]},<br>                     {rabbit_mgmt_external_stats,'-get_used_fd/1-fun-1-',2,[]},<br>
                     {lists,'-filter/2-lc$^0/1-0-',2,<br>                            [{file,"lists.erl"},{line,1271}]},<br>                     {lists,'-filter/2-lc$^0/1-0-',2,<br>                            [{file,"lists.erl"},{line,1271}]},<br>
                     {rabbit_mgmt_external_stats,get_used_fd,1,[]},<br>                     {rabbit_mgmt_external_stats,'-infos/2-lc$^0/1-0-',2,[]},<br>                     {rabbit_mgmt_external_stats,'-infos/2-lc$^0/1-0-',2,[]},<br>
                     {rabbit_mgmt_external_stats,emit_update,1,[]}]}<br></div><div><br></div>The only message on stdout/stderr is the one above.  We're running RabbitMQ 3.2.4 on Erlang R16B03-1, with HiPE compiled in (though we didn't specify hipe_compile in the RabbitMQ configuration).<br>
<br></div>-Brandon<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 15, 2014 at 1:58 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I assume you mean the Erlang VM is segfaulting (or at least terminating abruptly)?<br>
<br>
Is there anything in the logs? Does anything get printed to standard output / error just before the termination? Which versions of RabbitMQ / Erlang are you running? Have you enabled HiPE?<br>
<br>
Cheers, Simon<div><div class="h5"><br>
<br>
On 15/04/2014 00:27, Brandon Munroe wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
We're trying to run a RabbitMQ instance on FreeBSD 10.0 with 10k<br>
concurrent connections/queues, and we are experiencing a segmentation<br>
fault after letting the system idle for a little while (half an hour or<br>
so).  During this time, we just connect the 10k clients and pass no<br>
messages.  Does anyone have any ideas on where we could start looking to<br>
diagnose the problem, or has anyone encountered similar problems?<br>
<br>
Thanks in advance.<br>
<br>
-Brandon<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>