Did you not follow the RabbitMQ - Installing on Windows guide?
Either way, if you don’t have a node up or you have not explicitly started epmd, then it won’t be up and running and thus you won’t be able to connect to it.
Here’s a few examples (not on windows, but works the same regardless) :
$ epmd -names
epmd: Cannot connect to local epmd
Now, I start up a node via erl
, which implicitly will start epmd if it’s not already running :
$ erl -sname foo
Erlang/OTP 24 [erts-12.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [dtrace]
Eshell V12.2 (abort with ^G)
(foo@myhost)1>
Going into another terminal, I can now run epmd -names
successfully :
$ epmd -names
epmd: up and running on port 4369 with data:
name foo at port 58958
Now, when I stop this node, epmd will still be running :
$ epmd -names
epmd: up and running on port 4369 with data:
Likewise I can kill epmd and start it up explicitly via epmd
which will run in the foreground or epmd -daemon
so that it runs in the background and run epmd -names
, getting the same result above (unless I start up a node again).
Finally, I suppose if you’re trying to run rabbitmq and you’re running epmd.exe -names
but getting that message, that would indicate that rabbitmq is not running.
More information on epmd can be found here here