Determine the problematic files, and don't import them

mfoss — Mon, 01 Jun 2009 11:50:00 +0000

vila wrote:

We have a Jabberd Version: 1.4.3-3 installed in Ubuntu 8.04 box and we are migrating to ejabberd Version: 2.0.1-2~hardy1 over a similar box.

The issues appears when importing the two thousands users to the new ejabberd server.

after installing the server, using dpkg-reconfigure, the node and admin user are created succefully such that we can access the admin web interface without problems.

Following the instructions found on
http://www.ejabberd.im/jabberd1-to-ejabberd

we exectute ejabberdctl --node ejabberd@server import-dir PATH_TO_SPOOL_directory_of_the_jabberd_server

after that, things start ok but when reaching 600 aprox users imported, the server crashes saying: RPC failed: nodedown

So you have around 2000 XML files generated by jabberd-1.4.3 over the last years of life of your server. ejabberd successfully imports 612 of them, but when reaching the 613th, which may be of account marianela or of howard_em, ejabberd crashes.

Maybe some of your XML files are not XML correct, or they contain something that ejabberd is not able to read and crashes.

One solution is to determine which files are problematic and move them away of the automatic import. Let's imagine 1997 files can be imported successfully, and other 3 are problematic. If you could know which ones are those three files, and you know they are of people that nowadays does not use their accounts, then you can delete those files and don't care about importing them.

To determine what are the problematic files, if you find no elegant solution you can try the tricky way: split your jabberd spool dir in several subdirs with subsets of your xml files. jab1 contains from 1 to 500, jab2 contains from 501 to 1000, ...

ejabberd - Comments for "Importing users from jabberd "

Determine the problematic files, and don't import them