On 13/03/12 22:22, Derek Greer wrote:
> =ERROR REPORT==== 13-Mar-2012::15:00:15 ===
> 110 ** Connection attempt from disallowed node rabbitmqctl32476@[machine
> name] **
>
> Everything I've read about this says this is due to the erlang cookie of
> the user executing the rabbitmqctl.bat command not matching the global
> erlang cookie in C:\Windows, so I've had the admin check these values
> and he claims they are the exact same. The RabbitMQ service is running
> as the default system account which doesn't have a home directory, so I
> assume the service runs the process with the cookie from C:\Windows.
Yes, this error is due to mismatched cookie files between the running
service and the user running the rabbitmqctl.bat command.
If the service runs in an environment with a HOMEDRIVE and HOMEPATH
variable then the GetWindowsDirectory Windows API function is used to
locate the Erlang cookie file. The cookie file in the Windows directory
must match the cookie file in the home directory of the user running the
rabbitmqctl command, as explained here:
http://www.rabbitmq.com/install-windows-manual.html#find-rabbitmq-on-windows
You can obtain the hash of the cookie by turning on console logging (set
RABBITMQ_CONSOLE_LOG to new or reuse) and checking the line starting
with "cookie hash :".
There are some Erlang configuration parameters that are able override
the cookie value. Ensure that the startup scripts and rabbitmq.config
files have not been customised in this way.
If the Erlang VM does not find a cookie file then one will be created
with random contents. Make sure that the contents of the cookie files
were not auto-filled when starting up.
-Emile
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq...@lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
On 14/03/12 11:32, Emile Joubert wrote:
> You can obtain the hash of the cookie by turning on console logging (set
> RABBITMQ_CONSOLE_LOG to new or reuse) and checking the line starting
> with "cookie hash :".
On 14/03/12 11:51, Derek Greer wrote:
> The cookie files are the same between the user and the Windows
> directory cookie. I'm assuming this means the service process somehow
> couldn't locate the windows cookie file? How do I see the logs for
> the installed service?
See the instructions at these links
http://www.rabbitmq.com/install-windows-manual.html
http://www.rabbitmq.com/man/rabbitmq-service.man.html
for how to set RABBITMQ_CONSOLE_LOG and obtain the startup banner. This
will provide the cookie hash of the running broker. You can compare this
value with the error messages from rabbitmqctl.bat to confirm whether
the cookie values are indeed the same.
Hi Derek,
On 14/03/12 11:32, Emile Joubert wrote:
> You can obtain the hash of the cookie by turning on console logging (set
> RABBITMQ_CONSOLE_LOG to new or reuse) and checking the line starting
> with "cookie hash :".
On 14/03/12 11:51, Derek Greer wrote:See the instructions at these links
> The cookie files are the same between the user and the Windows
> directory cookie. I'm assuming this means the service process somehow
> couldn't locate the windows cookie file? How do I see the logs for
> the installed service?
http://www.rabbitmq.com/install-windows-manual.html
http://www.rabbitmq.com/man/rabbitmq-service.man.html
for how to set RABBITMQ_CONSOLE_LOG and obtain the startup banner. This
will provide the cookie hash of the running broker. You can compare this
value with the error messages from rabbitmqctl.bat to confirm whether
the cookie values are indeed the same.
-Emile