Rabbitmq server does not start, saying it's already running:
$: rabbitmq-server Activating RabbitMQ plugins ... 0 plugins activated: node with name "rabbit" already running on "android-d1af002161676bee" diagnostics: - nodes and their ports on android-d1af002161676bee: [{rabbit,52176}, {rabbitmqprelaunch2254, 59205}] - current node: 'rabbitmqprelaunch2254@android-d1af002161676bee' - current node home dir: /Users/Jordan - current node cookie hash: ZSx3slRJURGK/nHXDTBRqQ==
But, rabbitmqctl seems to think otherwise:
rabbitmqctl -n rabbit status Status of node 'rabbit@android-d1af002161676bee' ... Error: unable to connect to node 'rabbit@android-d1af002161676bee': nodedown diagnostics: - nodes and their ports on android-d1af002161676bee: [{rabbit,52176}, {rabbitmqctl2462,59256}] - current node: 'rabbitmqctl2462@android-d1af002161676bee' - current node home dir: /Users/Jordan - current node cookie hash: ZSx3slRJURGK/nHXDTBRqQ==
Any takers?
Verify Server Configuration Here are the recommended steps: Make sure the node is running using rabbitmq-diagnostics status. Verify config file is correctly placed and has correct syntax/structure. Inspect listeners using rabbitmq-diagnostics listeners or the listeners section in rabbitmq-diagnostics status.
RabbitMQ nodes are identified by node names. A node name consists of two parts, a prefix (usually rabbit) and hostname. For example, [email protected] is a node name with the prefix of rabbit and hostname of node1.
The rabbitmq server was running somewhere but it just couldn't be connected to.
One of the following will mention something about rabbits:
$: ps aux | grep epmd $: ps aux | grep erl
Kill the process with kill -9 {pid of rabbitmq process}
i was having the same problem then I realized I was not issuing the right command.
./rabbitmqctl stop
this works everytime, although it does take down erlang runtime too. also mind where your config file.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With