#Ejabberd 2.0.5 password#

sbin/ejabberdctl register user host password I will now register the admin users that I have set in step 2, issuing the command. My node should be started, so I check the status by issuing. Ok, now I'm ready to launch my first ejabberd node.įrom $EJABBERD, I enter the following command. Remark: I could omit this step if I would use the default ejabberd and erlang packages.ĥ. Since I'm working in a sandbox, I also need to set my environment variable LD_LIBRARY_PATH to point to /opt/qbase3/lib. Remind that this host is not the same as host in the ejabberd.cfg file!Īt the last line of that section (' EJABBERD_DB=$ROOTDIR/var/lib/ejabberd/db/$NODE'), approximately line 18, I change $NODE to $ERLANG_NODE, to obtain a clearer name for the database.Ĥ. This is the name of the host of the ejabberd node name. I will still need to register the users to the ejabberd node however once the node is up and running, see later.Īt approximately line 12, I find the line ' HOST=localhost', where I can set the host name of my ejabberd node. If I want to create multiple admin users, I have to create a line for each admin user. tdewolf) and my domain (the one defined as served hostname). I remove the %-signs (which indicate comments) and then change 'aleksey' and 'localhost' by my username (e.g. In the section SERVED HOSTNAMES I have a line '. Create backups of some critical files (just in case.): * the erlang/otp package is installed in /opt/qbase3/apps/erlang-R12B-5, further noted as $ERLANGġ. * the ejabberd package is installed in /opt/qbase3/apps/ejabberd-2.0.5, further noted as $EJABBERD Possibly you have to change this in /etc/hosts * I can ping from one machine to the other by using the host name. * Both running the PyMonkey framework ( /opt/qbase3).

To save you a lot of time I decided to share my procedure in my blog.

Some mailings (6) pointed also to '.hosts.erlang' as cause for my issue, but in my test case I didn't need that file. This cookie must be identical on all nodes, otherwise the nodes won't be able to communicate with each other. The cookie is required to identify the different nodes in the cluster. The big issue was the location of the cookie (. Some more googling lead me to various blogs (3) and internet fora (4)(5), some of them more helpful than the other, but they all helped me a little further and I finally got my nodes into clustering, thanks to my colleague, who gave me the last hint. However, what is described in that chapter is far from accurate to get a cluster of ejabberd nodes. Looking further in the official guide I even got the documentation of clustering right in front of me (2). I soon found out that setting up one node is pretty straight-forward, setting up nodes in a cluster however is another piece of cake. Quickly I got to the official ejabberd guide, which is clear and a good starting point (1). So I started my journey in googling for information on the net about installing ejabberd nodes. Differences might be the location of the mnesia database. It's not that I'm working in a specific framework that this information is not valid for the default packages on Linux, Windows, or (Open)Solaris. R12B-5) packages in this framework (Solaris only, as we speak). To work on this framework I need to be root in ' /opt', in which the framework is installed. I use 2 servers, both running OpenSolaris on which I have installed a very nice framework, namely PyMonkey (see and used for building compute and storage clouds amongst others. I found this a nice challenge, which shouldn't take too much time. A while ago, I was asked if I could set up a cluster of 2 ejabberd nodes (a Jabber/XMPP instant messaging server), using the default internal mnesia database.