I've managed to reproduce this behavior by the following: 1) Installed ejabberd; 2) stopped it; 3) changed hostname to localhost; 4) started ejabberd.
So, ejabberd database is tied to the old hostname and can't be used with new localhost hostname. A solution could be to restore old hostname (and make sure that erlang understood the change - the easiest way to check is to run 'erl -sname temp' and look at the shell prompt. Or you could migrate database to a new hostname (see http://www.ejabberd.im/migrate-host for details). If it's your case, I'd downgrade the bug severity to 'minor' and retitle it to something like "ejabberd: Needs to document connection between DB and hostname" -- Sergei Golovan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
