I've installed ejabberd, it starts fine. I've changed the hostname in ejabberctl and upated the INET_DIST_INTERFACE address accordingly, I've rebuilt the mnesia records and added the proper hostname to /etc/hosts. ejabberdctl start, live, and stop function as expected.
On the node I'm currently working on I need to configure clustering, according to a few posts and documentation I need to drop into the live node and modify some mnesia tables. Whenever I attempt to run ejabberd debug I get the following error.
identifying information replaced with *s
Erlang (BEAM) emulator version 5.6.5 [source] [64-bit] [smp:4] [async-threads:0] [hipe] [kernel-poll:true]
*** ERROR: Shell process terminated! (^G to start new job) ***
the server is up and actively running, I can connect and message through it via BOSH and native TCP methods and I see it running on in the procs list
ports:
tcp 0 0 0.0.0.0:5280 0.0.0.0:* LISTEN 19797/beam.smp
tcp 0 0 0.0.0.0:5222 0.0.0.0:* LISTEN 19797/beam.smp
tcp 0 0 0.0.0.0:5269 0.0.0.0:* LISTEN 19797/beam.smproc:
# ps aux | grep erl
root 19797 0.9 1.2 178320 51976 ? Sl 21:17 0:01 /usr/lib64/erlang/erts-5.6.5/bin/beam.smp -K true -P 250000 -- -root /usr/lib64/erlang -progname erl -- -home /usr/var/lib/ejabberd -name ejabberd@********* -noshell -noinput -noshell -noinput -pa /usr/lib/ejabberd/ebin -mnesia dir "/usr/var/lib/ejabberd" -kernel inet_dist_use_interface {192,168,20,136} -s ejabberd -sasl sasl_error_logger {file,"/usr/var/log/ejabberd/erlang.log"} -smp auto start
root 20021 0.0 0.0 61184 740 pts/0 S+ 21:19 0:00 grep erl
root 24168 0.0 0.0 10512 260 ? S Nov16 0:00 /usr/lib64/erlang/erts-5.6.5/bin/epmd -daemonI'm at a loss, any suggestions are welcome.
disregard, I figured it
disregard, I figured it out.
for those curious I had set the hostname in the hosts file to point to 127.0.0.1 but in the ejabberdctl I had set the INET addy to use 192.168.* address. When ejabberdctl was trying to drop into debug mode it would look on 127 and while server was awaiting connections on 192.*
Also in my previous post I said 'ejabberdctl stop' was functioning, this was false, I am working on a cluster setup and this single server was mis-configured and stop was not functioning properly.
Anyways, sorry for the forum noise.