[ejabberd] Problem restoring ejabberd on a new server

Shaun Kruger shaun.kruger at gmail.com
Thu May 5 08:51:57 MSD 2011


Are there any supervisor report messages telling you whether or not
ejabberd_iq_sup is starting and is healthy?  I would also look for
some crash reports for ejabberd_iq_sup.  I expect erlang.log to be
very educational.

Shaun

On Wed, May 4, 2011 at 9:26 PM, Eric Chamberlain <eric at rf.com> wrote:
> I also tried moving the contents of /etc/ejabberd and /var/lib/ejabberd/spool to the new server and launched with:
>
> ejabberdctl --node $OLDNODE start
>
> That also generates the following error:
>
> =ERROR REPORT==== 2011-05-04 23:19:54 ===
> E(<0.36.0>:gen_mod:73) : Problem starting the module mod_adhoc for host "rf.com" with options:
>  []
>  exit: {noproc,
>            {gen_server,call,
>                [ejabberd_iq_sup,
>                 {start_child,["rf.com",mod_adhoc,process_local_iq]},
>                 infinity]}}
>
> =INFO REPORT==== 2011-05-04 23:19:54 ===
>    application: ejabberd
>    exited: {bad_return,
>                {{ejabberd_app,start,[normal,[]]},
>                 {'EXIT',
>                     {noproc,
>                         {gen_server,call,
>                             [ejabberd_iq_sup,
>                              {start_child,
>                                  ["rf.com",mod_adhoc,process_local_iq]},
>                              infinity]}}}}}
>    type: temporary
>
>
>
>
> On May 4, 2011, at 7:55 PM, Eric Chamberlain wrote:
>
>> Hello,
>>
>> I am trying to move ejabberd to a new server and we are running into an error in the log.
>>
>> To migrate to the new server, I did the following steps outlined in the documentation:
>>
>>       1.  On the old server:
>>               a.  OLDFILE=/tmp/old.backup
>>               b. ejabberdctl backup $OLDFILE
>>               c. Copy $OLDFILE and the contents of /etc/ejabberd to the new server.
>>       2.  On the new server:
>>               a.  OLDNODE=ejabberd at domU-12-31-39-00-5C-08
>>               b.  NEWNODE=ejabberd at ip-10-46-63-56
>>               c.  OLDFILE=/tmp/old.backup
>>               d.  NEWFILE=/tmp/new.backup
>>               e.  rm -rf  /var/lib/ejabberd/spool
>>               f.  ejabberdctl start
>>               g.  ejabberdctl mnesia_change_nodename $OLDNODE $NEWNODE $OLDFILE $NEWFILE
>>               h.  ejabberdctl install_fallback $NEWFILE
>>               i.  ejabberdctl stop
>>               j.  ejabberdctl start
>>
>> The following error then appears in the log:
>>
>> =ERROR REPORT==== 2011-05-04 22:40:51 ===
>> E(<0.36.0>:gen_mod:73) : Problem starting the module mod_adhoc for host "rf.com" with options:
>>  []
>>  exit: {noproc,
>>            {gen_server,call,
>>                [ejabberd_iq_sup,
>>                 {start_child,["rf.com",mod_adhoc,process_local_iq]},
>>                 infinity]}}
>>
>> =INFO REPORT==== 2011-05-04 22:40:51 ===
>>    application: ejabberd
>>    exited: {bad_return,
>>                {{ejabberd_app,start,[normal,[]]},
>>                 {'EXIT',
>>                     {noproc,
>>                         {gen_server,call,
>>                             [ejabberd_iq_sup,
>>                              {start_child,
>>                                  ["rf.com",mod_adhoc,process_local_iq]},
>>                              infinity]}}}}}
>>    type: temporary
>>
>>
>> If I comment out the mod_adhoc, then we get the same error with the next module in the list, mod_announce.
>>
>> If I leave ejabberd.cfg with the original configuration file, ejabberd will start, but without our configuration settings.
>>
>> What am I doing wrong?  How do we migrate from one server to another?
>>
>> --
>> Eric Chamberlain, Founder
>> RF.com - http://RF.com/
>>
>>
>>
>>
>>
>>
>>
>
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>


More information about the ejabberd mailing list