Here are the remainder of messages in the rabbit.log.� These are the last messages until I manually restarted the process after noting that it had crashed.<br><br>=ERROR REPORT==== 13-Mar-2010::18:00:08 ===<br>{mochiweb_socket_server,235,<br>
��� {child_error,<br>������� {{{case_clause,[]},<br>��������� [{httpd_util,rfc1123_date,1},<br>���������� {rabbit_status_web,internal_update,1},<br>���������� {rabbit_status_web,handle_call,3},<br>���������� {gen_server,handle_msg,5},<br>
���������� {proc_lib,init_p_do_apply,3}]},<br>�������� {gen_server2,call,[rabbit_status_web,get_context]}}}}<br><br>=ERROR REPORT==== 13-Mar-2010::18:00:08 ===<br>{mochiweb_socket_server,235,<br>��� {child_error,<br>������� {{{case_clause,[]},<br>
��������� [{httpd_util,rfc1123_date,1},<br>���������� {rabbit_status_web,internal_update,1},<br>���������� {rabbit_status_web,init,1},<br>���������� {gen_server,init_it,6},<br>���������� {proc_lib,init_p_do_apply,3}]},<br>
�������� {gen_server2,call,[rabbit_status_web,get_context]}}}}<br><br>=INFO REPORT==== 13-Mar-2010::18:00:08 ===<br>��� application: rabbit_status<br>��� exited: shutdown<br>��� type: permanent<br><br>=INFO REPORT==== 13-Mar-2010::18:00:08 ===<br>
stopped TCP Listener on <a href="http://0.0.0.0:5672">0.0.0.0:5672</a><br><br>=INFO REPORT==== 13-Mar-2010::18:00:08 ===<br>closing TCP connection <0.1242.0> from <a href="http://10.8.25.1:59325">10.8.25.1:59325</a><br>
<br>=INFO REPORT==== 13-Mar-2010::18:00:08 ===<br>closing TCP connection <0.30625.41> from <a href="http://10.8.26.2:58929">10.8.26.2:58929</a><br><br>=INFO REPORT==== 13-Mar-2010::18:00:08 ===<br>closing TCP connection <0.24377.64> from <a href="http://192.168.5.50:3316">192.168.5.50:3316</a><br>
<br>=INFO REPORT==== 13-Mar-2010::18:00:08 ===<br>closing TCP connection <0.27424.60> from <a href="http://10.8.24.1:34061">10.8.24.1:34061</a><br><br>=INFO REPORT==== 13-Mar-2010::18:00:08 ===<br>closing TCP connection <0.30634.41> from <a href="http://10.8.26.1:53751">10.8.26.1:53751</a><br>
<br><br><br><div class="gmail_quote">On Mon, Mar 15, 2010 at 9:29 AM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Greg,<br>
<div class="im"><br>
On Sun, Mar 14, 2010 at 07:45:35PM -0700, Greg Campbell wrote:<br>
> ** Generic server rabbit_status_web terminating<br>
> ** Last message in was get_context<br>
> ** When Server state == {state,1268531993140,"Sun, 14 Mar 2010 09:59:53<br>
> GMT",<br>
><br>
> ... a bunch of queue status data...<br>
><br>
> ** Reason for termination ==<br>
> ** {{case_clause,[]},<br>
> � � [{httpd_util,rfc1123_date,1},<br>
> � � �{rabbit_status_web,internal_update,1},<br>
> � � �{rabbit_status_web,handle_call,3},<br>
> � � �{gen_server,handle_msg,5},<br>
> � � �{proc_lib,init_p_do_apply,3}]}<br>
<br>
</div>This doesn't indicate that Rabbit itself crashed, only that the<br>
rabbit_status_web process crashed. That process is under a supervisor<br>
hierarchy and should have been automatically restarted.<br>
<br>
I have reproduced this (in that I can get a very similar crash to happen,<br>
though without messing with my clock), and whilst similar entries in the<br>
logs appear, the rabbit_status_web process restarts correctly, and<br>
Rabbit itself continues on, perfectly happily.<br>
<div class="im"><br>
> The underlying issue in httpd_util:rfc1123_date appears to be an Erlang bug,<br>
> which I believe has been fixed in R13B04 (we're still running R13B03 on the<br>
> server, though):<br>
> <a href="http://www.erlang.org/cgi-bin/ezmlm-cgi?2:mss:1681:201001:jffdfifdokimdicjnpcp" target="_blank">http://www.erlang.org/cgi-bin/ezmlm-cgi?2:mss:1681:201001:jffdfifdokimdicjnpcp</a><br>
> .<br>
<br>
</div>Interesting bug, and I'm glad it's now been fixed.<br>
<div class="im"><br>
> However, it might be worth ensuring that a crash in a plugin doesn't cause<br>
> the entire system to shut down.<br>
<br>
</div>We don't think it did ;) Are there any more entries in the logs that you<br>
have that indicate anything else went wrong? It's possible the same bug<br>
affected more than just the plugin, but certainly the entry you showed<br>
us just shows a process within the status plugin going down which should<br>
have been immediately restarted.<br>
<br>
Matthew<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>