registration watching and erlang nodes

I just have some basic questions. I set my registration watchers for 2 accounts, though when a new user is registered it doesn't send any message. Is it sending something other then for an xmpp message, or are there other settings I have to set (like change from all to something else)? Also I was reading about erlang nodes but am still a little confused about this. If I wanted to set up 2 servers to talk with each other, allow them to talk to each other (users from server1 talk to users from server2) yet they would still have different names, is this possible and is this where the erlang nodes come in? Also just as a side note, does anyone know where a list of examples are for the adhoc commands that can be used for server administration (Something like a list/list all command would be great for starters).

Check config; use virtual hosts, not nodes

groovydude wrote:

I set my registration watchers for 2 accounts, though when a new user is registered it doesn't send any message.
Is it sending something other then for an xmpp message, or are there other settings I have to set (like change from all to something else)?

You didn't show how you configured this in ejabberd.cfg. You didn't say what ejabberd version you are using, and how you installed it.

Also, check ejabberd log files, maybe they show some error message, either when starting ejabberd or when a new account is registered.

groovydude wrote:

Also I was reading about erlang nodes but am still a little confused about this.
If I wanted to set up 2 servers to talk with each other, allow them to talk to each other (users from server1 talk to users from server2) yet they would still have different names, is this possible and is this where the erlang nodes come in?

Let's rethink the problem: you want to install the Jabber server on a machine, and serve two Jabber domains: example1.org and example2.com, right?

Then you simply need this in ejabberd.cfg:

{hosts, ["example1.org", "example2.com"]}.

Restart ejabberd, and configure DNS so that Jabber clients and other Jabber servers go to your machine. ejabberd will serve both hosts.

You don't need ejabberd node clustering for this.

groovydude wrote:

Also just as a side note, does anyone know where a list of examples are for the adhoc commands that can be used for server administration (Something like a list/list all command would be great for starters).

Jabber clients will show you a list of the available commands. I tested with Psi, Gajim and Tkabber. Check this screenshot with Tkabber.

Syndicate content