I've seen this problem with RabbitMQ on an EC2 instance before - the solution here is to adjust the hostname of the machine to something that will resolve across reboots of your EC2 instance.<br><br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Matt,<br>
<br>
Matt Long wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
after I reboot the EC2 instance and ssh back in, I get this when trying to check the status:<br>
<br>
$ sudo rabbitmqctl status<div class="im"><br>
Status of node 'rabbit@ip-10-100-100-200' ...<br>
Error: unable to connect to node 'rabbit@ip-10-100-100-200': nodedown<br>
diagnostics:<br>
- unable to connect to epmd on ip-10-100-100-200: address<br>
</div></blockquote>
<br>
That last line indicates that rabbitmqctl was unable to resolve ip-10-100-100-200 to an IP address.<br>
<br>
<br>
Matthias.<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>