[rabbitmq-discuss] unable to connect to node

[John Cartwright - NOAA Federal]

Thanks Tim.  There seem to be a couple of problems re: the RPM
install, but the "unable to connect to node" appears to be related to
relocating the SYS_PREFIX outside the install directory.  In other
words:

1) I stopped the server started by the init.d script and killed the
epmd process manually to get a clean start
2) install the rabbitmq-server-generic-unix-3.0.0.tar.gz, modifying
rabbitmq-defaults to set SYS_PREFIX to a directory other than the
install directory.
3) started the server
4) same problem with the status reporting "unable to connect to node".
Also found that I was unable to install a plugin getting the error:
           Error: {cannot_read_enabled_plugins_file,
           "/data/rabbitmq/etc/rabbitmq/enabled_plugins",eisdir}

5) stopped the server with "rabbitmqctl stop"
6) unset the custom SYS_PREFIX in rabbitmq-defaults and restarted the server
7) started the server and not status reports normally

The init.d script packaged in the RPM is removing the
/var/run/rabbitmq directory on stopping and not re-creating it on
startup, but that's a different issue...

So, do you know of any reason why relocating the data (log, mnesia,
enabled_plugins) should be any different that simply changing the
SYS_PREFIX in rabbitmq-defaults?

--john

On Wed, Nov 28, 2012 at 11:21 AM, Tim Watson <tim at rabbitmq.com> wrote:
> I seem to remember having problems when using the init.d script directly rather than `/sbin/service rabbitmq-server start` although that may have been to do with the account from which I ran it the first time. Anyway, are you sure that the rabbitmq-server process is running? You should see an instance of 'beam.smp' when running `ps` if it is, or alternatively you can run `epmd -names` as any user to see which erlang nodes are up and running.
>
> Cheers,
> Tim
>
> On 28 Nov 2012, at 16:55, John Cartwright - NOAA Federal wrote:
>
>> Hello All,
>>
>> I've installed the RPM ( from
>> http://www.rabbitmq.com/install-rpm.html) on a RHEL6 server and used
>> the init.d script "rabbitmq-server" to start the server.  However,
>> when I  run "rabbitmqctl status", I get the following suggesting
>> there's a problem:
>>
>> [rabbitmq at squall rabbitmq]$ ./bin/rabbitmqctl status
>> Status of node rabbit at squall ...
>> Error: unable to connect to node rabbit at squall: nodedown
>>
>> DIAGNOSTICS
>> ===========
>>
>> nodes in question: [rabbit at squall]
>>
>> hosts, their running nodes and ports:
>> - squall: [{rabbitmqctl23373,52427}]
>>
>> current node details:
>> - node name: rabbitmqctl23373 at squall
>> - home dir: /home/rabbitmq
>> - cookie hash: 0W8f6ODD6SgYDvLAojR/Zw==
>>
>>
>> I've confirmed there's a .erlang.cookie in the home directory of the
>> process owner.  Can someone please help me understand what the problem
>> might be?
>>
>> Thanks!
>>
>> --john
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss