[rabbitmq-discuss] Error: unable to connect to node 'rabbit at localhost': nodedown.

[Kayode Odeyemi]

On Sat, Sep 17, 2011 at 3:10 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> On 17/09/11 14:47, Kayode Odeyemi wrote:
>
>> =ERROR REPORT==== 14-Sep-2011::19:35:19 ===
>> ** Connection attempt from disallowed node
>> 'rabbitmqctl28817 at coasthost-pc**' **
>>
>
> That looks like an Erlang cookie mismatch problem.
>
> Did you follow the instructions at http://www.rabbitmq.com/man/**
> rabbitmq-service.man.html<http://www.rabbitmq.com/man/rabbitmq-service.man.html>
> <quote>
> By default the service will run in the authentication context of the local
> system account. It is therefore necessary to synchronise Erlang cookies
> between the local system account (typically C:\WINDOWS\.erlang.cookie and
> the account that will be used to run rabbitmqctl.
> </quote>
> ?
>

How do I synchronize the accounts? I am using the same account I used to
install Erlang to setup rabbitmq. Does this statement mean changing
rabbit at localhost to [local-system-account]@localhost when starting rabbitmq
with rabbitmqctl -n [account]@localhost start_app?

I checked Erlang cookie at C:\WINDOWS\.erlang.cookie and the one generated
by broker on startup. They are different. How do I synchronize them? There's
another .erlang.cookie at C:\Documents and Settings\<username>. What should
I do? Which one is the broker using when I start rabbitmq from services.msc?

>
> rabbitmqctl outputs some debug information when it fails to connect to the
> server. It is usually instructive to inspect that and compare it against the
> information logged by the broker on startup to its console log (see the
> aforementioned man page for locating that).
>

I did compare both information, and I try to start the broker with command:


rabbitmqctl -n rabbitmqctl15051 at coasthost-pc start_app

This doesn't seem to work either.

>
> As for...
>
>
>  =WARNING REPORT==== 15-Sep-2011::09:10:19 ===
>> Mnesia('rabbit at COASTHOST-PC'): ** WARNING ** Mnesia is overloaded:
>> {dump_log, time_threshold}
>>
>
> These warnings are generally harmless though they might suggest that your
> application is perhaps doing something weird, like creating and destroying a
> queue for every message.
>
>
> Regards,
>
> Matthias.
>



-- 
Odeyemi 'Kayode O.
http://www.sinati.com. t: @charyorde
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110917/4531ef54/attachment.htm>