[rabbitmq-discuss] |Spam| broker going down, how to troubleshoot?

[Shane]

We have a one node broker in a dev env which goes down once a day. The
rabbit log doesn't appear to show any clues other than a
"connection_closed_abruptly" which I assume occurs as the broker goes
down. What steps can I take to troubleshoot why the broker is going
down? Running version 2.1.1 running on SuSe linux running. Here's the
relevant rabbit log entries:

=INFO REPORT==== 5-Nov-2010::10:58:28 ===
accepted TCP connection on 0.0.0.0:5672 from 10.164.45.176:4448

=INFO REPORT==== 5-Nov-2010::10:58:28 ===
starting TCP connection <0.4560.22> from 10.164.45.176:4448

=WARNING REPORT==== 5-Nov-2010::11:37:57 ===
exception on TCP connection <0.4560.22> from 10.164.45.176:4448
connection_closed_abruptly

=INFO REPORT==== 5-Nov-2010::11:37:57 ===
closing TCP connection <0.4560.22> from 10.164.45.176:4448


=INFO REPORT==== 5-Nov-2010::12:00:36 ===
Limiting to approx 1048475 file handles (943625 sockets)

=INFO REPORT==== 5-Nov-2010::12:00:36 ===
Memory limit set to 1542MB.

=INFO REPORT==== 5-Nov-2010::12:00:36 ===
Management plugin upgraded statistics to fine.

=INFO REPORT==== 5-Nov-2010::12:00:36 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 5-Nov-2010::12:00:36 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide
index

=WARNING REPORT==== 5-Nov-2010::12:00:36 ===
msg_store_persistent: rebuilding indices from scratch

=INFO REPORT==== 5-Nov-2010::12:00:36 ===
started TCP Listener on 0.0.0.0:5672

=INFO REPORT==== 5-Nov-2010::12:00:36 ===
Management plugin started.
HTTP API:       http://nyggmspgd73:55672/api/
Management UI:  http://nyggmspgd73:55672/mgmt/

=INFO REPORT==== 5-Nov-2010::12:00:42 ===
accepted TCP connection on 0.0.0.0:5672 from 10.152.117.173:42281

=INFO REPORT==== 5-Nov-2010::12:00:42 ===
starting TCP connection <0.290.0> from 10.152.117.173:42281