

Most of you will be fine with default config file (or light changes). ejabberd is extremely powerful and can be configured in many ways with many options. mnesia dir "/var/spool/jabber" -noshell -noshell -noinputħ228 ? Ss 0:00 /usr/lib/erlang/lib/ssl-3.1.1.1/priv/bin/ssl_esockīut the ejabberd-server is NOT working :-( The Sasl.log-file look like this: jabber jabber # cat sasl. Here are the main entry points to learn more about ejabberd configuration. kernel inetrc "/etc/jabber/inetrc" -sasl sasl_error_logger ejabberd config "/etc/jabber/ejabberd.cfg" log_path "/var/log/jabber/ejabberd.log" home /var/run/jabber -pa /usr/lib/erlang/lib/ejabberd-1.1.3/ebin -sname ejabberd -s ejabberd Click on the Connection tab, then click to check the Manually Specify Server Host/Port: checkbox, and then enter the server IP or FQDN and change the port to. Every start crashes and gives me a huge (15KB) sasl.log.Īfter I started /etc/init.d/ejabberd start following processes are running: 7212 ? S 0:00 /usr/lib/erlang/erts-5.5.5/bin/epmd -daemonħ214 ? Sl 0:07 /usr/lib/erlang/erts-5.5.5/bin/beam -root /usr/lib/erlang -progname erl. But since then I even cannont start the ejabberd-server anymore :-(. I tried to reinstall ejabberd to be sure to have clean binaries. When I try to connect to my server, the indicator states " connecting", but nothing happens. But still no contact to other jabber-servers. Hi I built xabber myself from the latest develop branch (05c196a). I already started the ejabber manually with the -kernel. So Miranda tries to connect to senders local IP address that is terribly annoying of. I(:ejabberd_s2s_out:662): terminated: normal The admin ACL grants administrative privileges to XMPP accounts. The ejabber-log shows following: =INFO REPORT= 2::18:28:54 = Translated: the message could not be sent - reason: " ". MeOtherJabber: Ihre Nachricht kann nicht zugestellt werden: "hallohallohallo", Grund: "" User window: meAtEjabber: hallohallohallo

Since few week I my ejabberd-server cannot connect to other servers.
