ERROR: ejabberd node 'ejabberd @localhost' is already running

Question

• I install ejabberd, but when I start this terminal through the ./start command. This gave an error that ejabberd node ejabberd@localhost already running.

• I uninstalled ejabberd and installed it again through the installer, but ... it gave the same error.

Answer 1

I tested the new installation using the OSX ejabberd installer on OSX 10.10.4, and after installation I can start the ejabberd just fine.

So it looks like you already have something working in your environment that does not work well with the ejabberd / ejabberd installer.

Here is what you need to check:

• Check if ejabberd really works with the following ejabberdctl command:

  $ bin / ejabberdctl status

  You can also try to start / stop ejabberd directly with ejabberdctl stop and ejabberdctl start

• Check Erlang running processes with ps aux | grep beam ps aux | grep beam . Here is what I get when starting ejabberd:

  $ ps aux | beam grep mremond 53977 0.0 0.2 2526548 41872 ?? S 7:47 PM 0: 01.73 / Applications / ejabberd-15.06 / bin / beam.smp -K true -P 250000 - -root / Applications / ejabberd-15.06 -progname / Applications / ejabberd-15.06 / bin / erl - - home / Users / mremond - -sname ejabberd @localhost -noshell -noinput -noshell -noinput -pa / Applications / ejabberd-15.06 / lib / ejabberd-15.06 / ebin -mnesia dir "/Applications/ejabberd-15.06/database/ejabberd @localhost "-ejabberd log_rate_limit 100 log_rotate_size 10485760 log_rotate_count 1 log_rotate_date" "-s ejabberd -sasl sasl_error_logger {file," /Applications/ejabberd-15.06/logs/erlang.log "} -smp autostart

• Check what you see in the /Applications/ejabberd-15.06/logs files. Pay particular attention to error.log and install.log

Answer 2

I am facing a similar problem using ubuntu as the operating system.

I just use the ps -aux command | grep -i 'ejabberd' listing ejabberd processes. Than I will kill all these processes (by collecting the process identifier from the command higher than the use command, for example "kill 98167 87654").

This fixed problem is for me.