Some ideas

mfoss — Fri, 10 Apr 2009 22:35:57 +0000

brain2xml wrote:

We have host 'maminaeda.ru' on this panell

Just make sure your ejabberd.cfg has:

{hosts, ["maminaeda.ru"]}.

If you have several domains, and you want ejabberd to serve the virtual hosts, then you can put:

{hosts, ["maminaeda.ru", "example2.ru", "supercorp.com"]}.

brain2xml wrote:

ejabberdctl --node ejabberd@maminaeda.ru
RPC failed on the node 'ejabberd@help.ru': nodedown

The node name is not related with virtual host. No need to specify --node ...

brain2xml wrote:

server works but only on machine name host when I try to swith on other host

Do you want to use the database of ejabberd from machine1 in an ejabberd that you have installed in machine2? In this case, you copy ejabberd.cfg and the Mnesia spool files from machine1 to machine2. Then, try to start ejabberd in machine2.

If it doesn't start correctly and shows some error like this:

=ERROR REPORT==== 11-Apr-2009::00:29:53 ===
E(<0.38.0>:ejabberd_config:278) : Error reading Mnesia database spool files:
The Mnesia database couldn't read the spool file for the table 'config'.
ejabberd needs read and write access in the directory:
   /var/lib/ejabberd/db/ejabberd
Maybe the problem is a change in the computer hostname,
or a change in the Erlang node name, which is currently:
   ejabberd@machine2
Check the ejabberd guide for details about changing the
computer hostname or Erlang node name.

Then you must know the node name in machine1. It probably was 'ejabberd@machine1'.

Now in machine2 try to start ejabberd again, this time providing the node name:

$ ejabberdctl live --node ejabberd@machine1

In your case, machine1 and machine2 may be help.ru, or loft2239.serverloft.com or some other names.

ejabberd - Comments for "ejabberd can&#039;t see virtual host"

Some ideas

ejabberd - Comments for "ejabberd can't see virtual host"