ejabberd - Comments for "Confused about nodes and hostnames"

Import user problem solved

redhat — Sat, 24 Sep 2005 14:52:52 +0000

Solved my own problem. The directory name for the jabberd 1.4 user directory must be the actual host name. My mistake was that I wanted to work with a copy of the original directory for safety, and I renamed it when copying.

Import users into proper node/host

redhat — Sat, 24 Sep 2005 13:15:43 +0000

Thank you, this has solved some problems for me.

On my machine when I enter hostname -s I get back 'arthur' so I changed my startup script to:

#!/bin/bash

erl -pa /var/lib/ejabberd/ebin \
-sname arthur \
-s ejabberd \
-ejabberd config \"/etc/ejabberd/ejabberd.cfg\" \
log_path \"/var/log/ejabberd/ejabberd.log\" \
-sasl sasl_error_logger \{file,\"/var/log/ejabberd/sasl.log\"\} \
-mnesia dir \"/var/lib/ejabberd/spool\" \
-detached

And now the control script works properly like this:

ejabberdctl arthur@arthur status

Node arthur@arthur is started. Status: started

However, I still have at least one problem somewhere. I have to import users from our old jabberd 1.4 installation. It worked, but they did not get added to the proper node, or hostname. I execute a command like this:

ejabberdctl arthur@arthur import-dir /home/ejabberd/oldspool

There are no errors and the users are imported, but the users seem to be added to the wrong place so I get this:

ejabberdctl arthur@arthur registered-users

ejabberd@jabber.mydomain.com
michael@spool
andy@spool

The ejabberd user is one I created with a normal jabber client. That user works and I can use that password for the web admin interface. Michael and Andy users were imported.

Why are the imported users added to spool? Does that indicate a configuration or startup script problem? How do I get them into jabber.mydomain.com?

Thanks again for the help.

I guess there is a problem

sander — Sat, 24 Sep 2005 08:12:45 +0000

I guess there is a problem in your startup script. Instead of using the full hostname to start ejabberd (jabber.mydomain.com), you should put there what you get when you do "hostname -s". Then the error about the illegal hostname should disappear.

You also should use this smaller hostname in the ejabberdctl command of course. If ejabberdctl still gives problems, it is probably because you try to run that script as a different user than the user who started ejabberd (different Erlang cookies).

--
sander