<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt"><div>I ran the first command for 24 hours every 10 minutes, but the second command blew up rabbit most of the time:</div><div><br></div><div style="background-color: transparent;">Error: unable to connect to node rabbit@project2: nodedown</div><div style="background-color: transparent;"><br></div><div style="background-color: transparent;">DIAGNOSTICS</div><div style="background-color: transparent;">===========</div><div style="background-color: transparent;"><br></div><div style="background-color: transparent;">nodes in question: [rabbit@project2]</div><div style="background-color: transparent;"><br></div><div style="background-color: transparent;">hosts, their running nodes and ports:</div><div style="background-color: transparent;">- project2: [{rabbitmqctl2916,46327}]</div><div
style="background-color: transparent;"><br></div><div style="background-color: transparent;">current node details:</div><div style="background-color: transparent;">- node name: rabbitmqctl2916@project2</div><div style="background-color: transparent;">- home dir: /var/lib/rabbitmq</div><div style="background-color: transparent;">- cookie hash: g9gANsnT4AWb9xKsznR+nA==</div><div><br></div><div>I stopped the collection script after 11 iterations, but only have 5 files with anything in them. </div><div><br></div><div>They range in size from 109k to over 1gig. </div><div><br></div><div>Compressed they are like 280mb (https://www.dropbox.com/s/jvaaohg59cl6gn3/rabbit-memory-details.tgz), not sure if it is useful or not since it was for such a small, and irregular, time interval.</div><div><br></div><div>Additionally, a colleague pointed out an interesting failure case where we were out of memory with 4 messages in queues.</div></div></body></html>