<div dir="ltr">What does /etc/hosts look like? Can 'localhost' resolve?</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 27, 2013 at 12:51 PM, Travis Jensen <span dir="ltr"><<a href="mailto:travis.jensen@gmail.com" target="_blank">travis.jensen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>So I had rabbitmq working fine on my laptop, then had to reboot somewhere else where my hostname wouldn't resolve and it failed to start. As annoying as that was, I figured I would just wait until I got back to my DNS and then restart it. Wrong.<br>
<br>So, after searching and futzing for an hour, I decided I needed to upgrade anyway, so I uninstalled 3.0.4, cleaned up all the old configuration files, db directories and such, and installed 3.1.0 (note: Using OS X 10.7.5, Erlang R15B03 and Homebrew). <br>
<br>Now, I continue to see the same behavior:<br><br><span style="font-family:courier new,monospace">$ rabbitmqctl add_user test test_pass<br>Creating user "test" ...<br>Error: unable to connect to node rabbit@localhost: nodedown<br>
<br>DIAGNOSTICS<br>===========<br><br>nodes in question: [rabbit@localhost]<br><br>hosts, their running nodes and ports:<br>- localhost: []<br><br>current node details:<br>- node name: nonode@nohost<br>- home dir: /Users/travis<br>
- cookie hash: 92vmrXD/iLl+OKWxh4sEhQ==<br></span><br><font face="arial,sans-serif">This is how things looked on startup:<br><span style="font-family:courier new,monospace"><br>$ rabbitmq-server<br><br> RabbitMQ 3.1.0. Copyright (C) 2007-2013 VMware, Inc.<br>
## ## Licensed under the MPL. See <a href="http://www.rabbitmq.com/" target="_blank">http://www.rabbitmq.com/</a><br> ## ##<br> ########## Logs: /usr/local/var/log/rabbitmq/rabbit@localhost.log<br> ###### ## /usr/local/var/log/rabbitmq/rabbit@localhost-sasl.log<br>
##########<br> Starting broker... completed with 7 plugins.<br></span><br>And the logs seem pretty nominal. Note that the <i>rabbitmqctl</i> connection never shows up, but I can telnet in to port 5672 and see a failed connection show up. Unsurprisingly, the issue seems to revolve around the <i>node: nonode@nohost</i> that I've highlighted in the logs below. This behavior persists even if I explicitly set <i>RABBITMQ_NODENAME=rabbit@localhost</i> when I run rabbitmq-server.<br>
<br><span style="font-family:courier new,monospace">=INFO REPORT==== 27-Jun-2013::10:32:02 ===<br>Starting RabbitMQ 3.1.0 on Erlang R15B03<br>Copyright (C) 2007-2013 VMware, Inc.<br>Licensed under the MPL. See <a href="http://www.rabbitmq.com/" target="_blank">http://www.rabbitmq.com/</a><br>
<br>=INFO REPORT==== 27-Jun-2013::10:32:02 ===<br><b><span style="color:rgb(255,0,0)">node : nonode@nohost</span></b><br>home dir : /Users/travis<br>cookie hash : 92vmrXD/iLl+OKWxh4sEhQ==<br>log : /usr/local/var/log/rabbitmq/rabbit@localhost.log<br>
sasl log : /usr/local/var/log/rabbitmq/rabbit@localhost-sasl.log<br>database dir : /usr/local/var/lib/rabbitmq/mnesia/rabbit@localhost<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Limiting to approx 156 file handles (138 sockets)<br>
<br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Memory limit set to 1439MB of 3597MB total.<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Disk free limit set to 1000MB<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>
msg_store_transient: using rabbit_msg_store_ets_index to provide index<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>msg_store_persistent: using rabbit_msg_store_ets_index to provide index<br><br>=WARNING REPORT==== 27-Jun-2013::10:32:03 ===<br>
msg_store_persistent: rebuilding indices from scratch<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Adding vhost '/'<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Creating user 'guest'<br><br>
=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Setting user tags for user 'guest' to [administrator]<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Setting permissions for 'guest' in '/' to '.*', '.*', '.*'<br>
<br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>started TCP Listener on <a href="http://127.0.0.1:5672" target="_blank">127.0.0.1:5672</a><br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Management plugin started. Port: 15672<br>
<br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Statistics database started.<br><br>=INFO REPORT==== 27-Jun-2013::10:32:03 ===<br>Server startup complete; 7 plugins started.<br> * amqp_client<br> * mochiweb<br> * rabbitmq_management<br>
* rabbitmq_management_agent<br> * rabbitmq_management_visualiser<br> * rabbitmq_web_dispatch<br> * webmachine<br></span><br>My rabbitmq-env.conf file is pretty simple (the Homebrew default, in fact):<br><br><span style="font-family:courier new,monospace">CONFIG_FILE=/usr/local/etc/rabbitmq/rabbitmq<br>
NODE_IP_ADDRESS=127.0.0.1<br>NODENAME=rabbit@localhost<br></span><br>And, after going through my previous rabbitmq.config file to remove everything that either was a default or no longer existed as a configuration option, my configuration file looks like:<br>
<br><span style="font-family:courier new,monospace">[].<br></span><br>Just to make sure I don't have any weird environment variables I didn't remember persisting, I ran a <i>set | grep -i rabbit</i> and got an empty set. I also removed <i>~/.erlang.cookie</i>, to make sure it wasn't messing things up.<br>
<br>So I've reached the end of what Google and the docs have been able to tell me. Help is most graciously appreciated.<span class="HOEnZb"><font color="#888888"><br><br>tj<br></font></span></font><br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">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>
<br></blockquote></div><br></div>