This post was originally published on 13 Oct 2016 at http://blogs.microsoft.co.il/iblogger/2016/10/13/could-not-contact-node-rabbitmachine_name-after-upgrading-to-rabbitmq-3-6-5/
This error kept me busy for almost two days, so i thought it would be best to describe the steps i took to fix it
- Make sure that the erlang cookie file (.erlang.cookie) is configured correctly in all places. i.e. %HOMEDRIVE%%HOMEPATH% and %SYSTEMROOT%. it should contain the same value in all places
- Open the RabbitMQ command prompt with Administrator privileges
- Remove the RabbitMQ service by using the command: rabbitmq-service remove
- Navigate to %APPDATA%\RabbitMQ\db
- Delete everything (make sure you have a backup just in case)
- Go back to the command promp and install the service with the command: rabbitmq-service install
- Check that the node is connected by running the command: rabbitmqctl status
- Hope you’ll have a smoother upgrade process than mine
1. Sometimes this phenomena happen when workstation is inserted into domain after installation of RabbitMQ is completed.
2. In case when RabbitMQ command prompt is not available from the Start menu, please open “C:\Program Files (x86)\RabbitMQ Server\rabbitmq_server-3.5.2\sbin” in the command line