Changed node name in ejabberd backup but still can't restore it

So, I've tried to use this: http://www.ejabberd.im/migrate-host and successfully converted nodes. My old node was "ejabberd@server" and current node maybe "ejabberd@VPS7074.saverabbits.com". Here is my hostname:

[root@VPS7074 tmp]# hostname
VPS7074.saverabbits.com
Here is my hosts:

[root@VPS7074 tmp]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
127.0.0.1 server
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
78.47.76.4 vps7074.saverabbits.com
# Auto-generated hostname. Please do not remove this comment.
111.90.147.148 VPS7074.saverabbits.com VPS7074
And the error is:

=ERROR REPORT==== 2012-01-10 08:35:09 ===
E(<0.39.0>:ejabberd_config:551) : 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/spool
Maybe the problem is a change in the computer hostname,
or a change in the Erlang node name, which is currently:
'ejabberd@VPS7074.saverabbits.com'
Check the ejabberd guide for details about changing the
computer hostname or Erlang node name.

=INFO REPORT==== 2012-01-10 08:35:09 ===
application: ejabberd
exited: {bad_return,{{ejabberd_app,start,[normal,[]]},
{'EXIT',"Error reading Mnesia database"}}}
type: temporary

But spool dir is readable and writable to ejabberd. Hostname as I think are ok too, so can you explain me please what is the problem?

And after this manipulations I found that ejabberd starting but not works (port 5280 not binded and ejabberd status say that ejabberd isn't started), and there are logs:

[root@VPS7074 ejabberd]# cat /var/log/ejabberd/ejabberd.log

=ERROR REPORT==== 2012-01-10 21:55:18 ===
E(<0.36.0>:ejabberd_config:551) : 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/spool
Maybe the problem is a change in the computer hostname,
or a change in the Erlang node name, which is currently:
ejabberd@VPS7074
Check the ejabberd guide for details about changing the
computer hostname or Erlang node name.

=INFO REPORT==== 2012-01-10 21:55:18 ===
application: ejabberd
exited: {bad_return,{{ejabberd_app,start,[normal,[]]},
{'EXIT',"Error reading Mnesia database"}}}
type: temporary

AND in erlang.log:

=CRASH REPORT==== 10-Jan-2012::21:55:18 ===
crasher:
initial call: application_master:init/4
pid: <0.35.0>
registered_name: []
exception exit: {bad_return,{{ejabberd_app,start,[normal,[]]},
{'EXIT',"Error reading Mnesia database"}}}
in function application_master:init/4
ancestors: [<0.34.0>]
messages: []
links: [<0.34.0>,<0.36.0>,<0.6.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 987
stack_size: 24
reductions: 151
neighbours:

Johnny Kravitz wrote: So,

Johnny Kravitz wrote:

So, I've tried to use this: http://www.ejabberd.im/migrate-host and successfully converted nodes. My old node was "ejabberd@server" and current node maybe "ejabberd@VPS7074.saverabbits.com".

If you don't plan to use ejabberd clustering now, you can try another trick: edit ejabberdctl.cfg to force ejabberd to use the old node name.

Syndicate content