[rabbitmq-discuss] Error: unable to connect to node rabbit at dev: nodedown

[Marek Majkowski]

2011/8/4 平常心态 <214575002 at qq.com>:
> hi, all
>     some error come up when I want to get some status of my rabbitmq-server
>     the site http://www.rabbitmq.com/install.html#troubleshooting said that
> I should make sure the erlang cookies are the same, but I am new to erlang
> ,I don't know how to make sure.
> below is the output,
>     /------------------------------------rabbitmqctl
> status-------------------------------/
> dev at dev:~/source/rabbitmq/sbin$ ./rabbitmqctl status
> Status of node rabbit at dev ...
> Error: unable to connect to node rabbit at dev: nodedown
> =ERROR REPORT==== 4-Aug-2011::09:29:10 ===
> Error in process <0.36.0> on node 'rabbitmqctl14242 at dev' with exit value:
> {badarg,[{erlang,list_to_existing_atom,["rabbit at Fanqu-WorkStation"]},{dist_util,recv_challenge,1},{dist_util,handshake_we_started,1}]}
> diagnostics:
> - nodes and their ports on dev: [{rabbit,56129},{rabbitmqctl14242,38839}]
> - current node: rabbitmqctl14242 at dev
> - current node home dir: /home/dev
> - current node cookie hash: t6gCD5tZzOtYsVS32gQgwA==
>     /------------------------------------hostname
> -s-------------------------------/
> dev at dev:~/source/rabbitmq/sbin$ hostname -s
> dev
> dev at dev:~/source/rabbitmq/sbin$ cat /etc/hosts
> 127.0.0.1       localhost
> 127.0.1.1       dev
>     /------------------------------------ps aux | grep beam
> -------------------------------/
> dev at dev:~/source/rabbitmq/sbin$ ps aux | grep beam
> dev      21051  0.0  0.3  56980  8080 ?        Sl   Jul26   3:44
> /usr/lib/erlang/erts-5.7.4/bin/beam.smp -W w -K true -A30 -P 1048576 --
> -root /usr/lib/erlang -progname erl -- -home /home/dev -- -noshell -noinput
> -sname rabbit at Fanqu-WorkStation -boot
> /home/dev/rabbitmq/data/rabbit at Fanqu-WorkStation-plugins-expand/rabbit
> -kernel inet_default_listen_options [{nodelay,true}] -kernel
> inet_default_connect_options [{nodelay,true}] -sasl errlog_type error
> -kernel error_logger
> {file,"/home/dev/rabbitmq/log/rabbit at Fanqu-WorkStation.log"} -sasl
> sasl_error_logger
> {file,"/home/dev/rabbitmq/log/rabbit at Fanqu-WorkStation-sasl.log"} -os_mon
> start_cpu_sup true -os_mon start_disksup false -os_mon start_memsup false
> -mnesia dir "/home/dev/rabbitmq/data/rabbit at Fanqu-WorkStation" -noshell
> -noinput
> dev      30911  0.0  0.0   3552   916 pts/2    S+   09:40   0:00 grep
> --color=auto beam

You seem to have rabbit running as "rabbit at Fanqu-WorkStation" while your
rabbitmqctl asks for "rabbit at dev".

If "Fanqu-WorkStation" is a proper network name, you should be able to
do "rabbitmqctl -n rabbit at Fanqu-WorkStation status"

Cheers,
   Marek