C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.4\sbin>rabbitmqctl status
Status of node rabbit@DESKTOP-7IAJK37 ... Error: unable to perform an operation on node 'rabbit@DESKTOP-7IAJK37'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
* Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues) * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
* Target node is not running
In addition to the diagnostics info below:
* See the CLI, clustering and networking guides on http://rabbitmq.com/documentation.html to learn more
* Consult server logs on node rabbit@DESKTOP-7IAJK37
DIAGNOSTICS
===========
attempted to contact: ['rabbit@DESKTOP-7IAJK37']
rabbit@DESKTOP-7IAJK37:
* connected to epmd (port 4369) on DESKTOP-7IAJK37
* epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic
* TCP connection succeeded but Erlang distribution failed
* Authentication failed (rejected by the remote node), please check the Erlang cookie
Current node details:
* node name: 'rabbitmqcli38@DESKTOP-7IAJK37'
* effective user's home directory: C:\Users\itsvse_pc
* Erlang cookie hash: RmzKErjVZUcsMU8wSgBGbA==
The cookie used by rabbitMQ is: C:\Users\itsvse_pc\.erlang.cookie This should be the same as the cookie section above
Cause of the problem:
My local administrator name is itsvse_pc, I log in to the server with itsvse_pc account and install rabbitmq, rabbitmq also automatically creates an .erlang.cookie file under C:\user\itsvse_pc, but when the RabbitMQ service starts, the executioner is the local system account, as shown in the figure below:
Solution:
Use the account installed on the machine to start the service, take the local machine as an example, that is, use the itsvse_pc account to start the service, as shown in the figure below:
Once the settings are complete, tap Apply and Save,Then restart the service!!!! Restart service!！
Execute rabbitmqctl status again, success!
|
Posted on 3/29/2018 10:29:39 AM
|
|
|
|
Landlord|
Posted on 3/29/2018 10:35:54 AM
|
