ejabberd - Comments for "fresh install - Failed RPC connection to the node: nodedown"

derobert wrote: fk_

fk_ — Thu, 20 Dec 2012 13:46:59 +0000

derobert wrote:

fk_ wrote:

ejabberd tells you - "duplicate_name" which could mean you have tcp port already opened by another instance or other daemon. Check twice ejabberd's process is not already running when you start it.

ps aux | grep ejabberd

ejabberd 1190 0.0 0.0 1956 476 ? S 13:12 0:00 /usr/lib/erlang/erts-5.6.5/bin/epmd -daemon
ejabberd 1222 1.9 1.3 98376 28028 ? Sl 13:12 0:00 /usr/lib/erlang/erts-5.6.5/bin/beam.smp -K true -P 250000 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/ejabberd/spool -sname ejabberd@mail -noshell -noinput -noshell -noinput -pa /usr/lib/ejabberd/ebin -mnesia dir "/var/lib/ejabberd/spool" -s ejabberd -sasl sasl_error_logger {file,"/var/log/ejabberd/erlang.log"} -smp auto start
ejabberd 1234 0.0 0.0 1952 400 ? Ss 13:12 0:00 inet_gethost 4
ejabberd 1235 0.0 0.0 2000 508 ? S 13:12 0:00 inet_gethost 4

when i kill all this processes and restart ejabberd it still gives me this error RPC connection failed to node, nodedown.

please use netstat -pln in order to determine if one of ejabberd's used ports is used by another process which might not be ejabberd itself but some other daemon

ok, AFAIR the other cause of this could be wrong ejabberd's node name (/etc/default/ejabberd IIRC in Ubuntu) or broken hostname record
refer to documentation for your distribution on how to correctly set these params

fk_ wrote: ejabberd tells you

derobert — Fri, 14 Dec 2012 12:18:26 +0000

fk_ wrote:

ejabberd tells you - "duplicate_name" which could mean you have tcp port already opened by another instance or other daemon. Check twice ejabberd's process is not already running when you start it.

ps aux | grep ejabberd

when i kill all this processes and restart ejabberd it still gives me this error RPC connection failed to node, nodedown.

ejabberd tells you -

fk_ — Wed, 12 Dec 2012 16:25:33 +0000

ejabberd tells you - "duplicate_name" which could mean you have tcp port already opened by another instance or other daemon. Check twice ejabberd's process is not already running when you start it.