Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot connect to RabbitMQ #95

Open
cwidisgroup opened this issue May 26, 2023 · 0 comments
Open

Cannot connect to RabbitMQ #95

cwidisgroup opened this issue May 26, 2023 · 0 comments

Comments

@cwidisgroup
Copy link

Installed everything according to the instructions. Attempting to start VolCap on the central machine (which is called topinambur): it crashes straight away without any message.

Opened a RabbitMQ command prompt. It seems there is a problem with connecting to the rabbitMQ server:

C:\Program Files\RabbitMQ Server\rabbitmq_server-3.11.16\sbin>rabbitmqctl.bat status
Error: unable to perform an operation on node 'rabbit@topinambur'. 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 https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@topinambur
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools

DIAGNOSTICS
===========

attempted to contact: [rabbit@topinambur]

rabbit@topinambur:
  * connected to epmd (port 4369) on topinambur
  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic
  * TCP connection succeeded but Erlang distribution failed
  * suggestion: check if the Erlang cookie is identical for all server nodes and CLI tools
  * suggestion: check if all server nodes and CLI tools use consistent hostnames when addressing each other
  * suggestion: check if inter-node connections may be configured to use TLS. If so, all nodes and CLI tools must do that
   * suggestion: see the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more


Current node details:
 * node name: 'rabbitmqcli-870-rabbit@topinambur'
 * effective user's home directory: c:/Users/dis
 * Erlang cookie hash: bezvwVB7D8f7RbNZ/T5bSg==


C:\Program Files\RabbitMQ Server\rabbitmq_server-3.11.16\sbin>

Double-checked that the firewall settings are correct, and they seem to be (port 5672 and 15672 are open).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant