[rabbitmq-discuss] Error: unable to connect to node 'rabbit at localhost': nodedown.
Matthias Radestock
matthias at rabbitmq.com
Sat Sep 17 15:10:39 BST 2011
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
<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>
?
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).
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.
More information about the rabbitmq-discuss
mailing list