Hi everybody.

Can anybody tell me if there is any kind of "magic trick" to import accounts from jabberd14 but in a way in which i can preserve users passwords and individual authorisation settings?
I observed that after importing, each user has to re-authorise each contact from his/her roster.

I migrated one french jabber server (jabber-fr.net) (from jabberd1.4 to ejabberd) with the MySQL support and i met a problem with the script to import users account. The script is OK when ejabberd run with mnesia database but with MySQL, the script didn't imported any rosters ! So, i wrote a script in PHP to migrate all rosters of all XML files (form jabberd1.4). The script import only rosterusers and rostergroups because it was only these informations which didn't import in MySQL tables (Username, messages... import well). This script is under GNU GPL v2 licence. You can donwload and use it here: http://bchomel.free.fr/loisirs/info/script_migration_rosters_ejabberd_my...

JID: nanard51@jabber-fr.net

A copy of the script is also available here: script_migration_rosters_ejabberd_mysql.tar.gz

Hi to all,

I have jabberd 1.4 running on a linux server. I'm currently testing ejabberd on my windows machine. I've been trying to import some users from jabberd into ejabberd,following the instruction given above, but to no avail.

Would someone kindly advice me how to run the above procedure in a windows environment?
Please help.

thx in advance

cheers,
sylver

p/s: I've tried including 'erl5.4.13\bin' in my PATH variable. It still won't work.

With the command: "./bin/ejabberdctl import-dir /home/karlox/ejabberd-1.1.1/jabberd14/spool/tegra-sc.it/"
I cant import jabber-1.4 accounts with this error:

=ERROR REPORT==== 12-Sep-2006::13:24:01 ===
E(<3891.290.0>:jd2ejd:39): Error while processing file "/home/karlox/ejabberd-1.1.1/jabberd14/spool/jabber.integra-sc.it/ruscello_0346.xml": {undef,
[{ejabberd_auth_undefined,
set_password,
["ruscello_0346",
"tegra-sc.it",
"ruscello_0346"]},
{lists,
foldl,
3},
{jd2ejd,
xdb_data,
3},
{lists,
foreach,
2},
{jd2ejd,
import_file,
1},
{jd2ejd,
'-import_dir/1-fun-1-',
3},
{lists,
foldl,
3},
{ejabberd_ctl,
process,
1}]}

** at node k4m_ejabberd@atena **

I don't undestand the problem!!!

I'm using ejabberd 1.1.1 with native postgres-backend and everything is working fine. However, as I migrated from jabberd2 to ejabberd, I had to use the given scripts (convert to xml and import afterwards). The users are correctly imported whereas the roster items won't get imported at all.

So it can't be a problem of file permissions. As the roster items which I add to my roster in my jabber client show up in the table, it isn't a problem of misconfiguration neither.

I even tried to import some native xml files of a jabberd1.4 test installation, same behaviour. Users are imported, roster items are not.

Does anyone have an idea on what the problem could be?

Hi,

I have a problem to import xml file xdb (jabber 1.4) to ejabberd 1.0, in version 0.9 of ejabberd this was possible.

I paste the error:

# su ejabberd /usr/local/bin/ejabberdctl ejabberd@vs2 import-dir /home/network/import/*
Can't import jabberd 1.4 spool dir "/home/network/import/jpmattos.xml" at node ejabberd@vs2: 
{'EXIT', {{badmatch, {error, enotdir}},
[{jd2ejd, import_dir, 1}, {rpc, '-handle_call/3-fun-0-', 5}]}}

Thanks

There is problem with jabberdctl import-dir on debian. You can get messages that import script could not read find the file. Problem is in permissions.

You have to change all permissions on path to file that you're importing. Ejabberd user must have access permissions. E.g. if you were using Jabber 1.4 default permission belongs only to jabber, so user ejabberd couldn't read the file.

If you're importing by import-file it's also very useful to use full path specification to xml file from j1.4.

I imported a great number of users from a jabberd1.4 installation. Looks like jabberd1.4 created - I don't know why - password tags in XML files in two different formats: one expliciting the namespace, the other one not doing it.

Maybe the ones that don't get imported were created from older jabberd versions.

Ejabberd will import the former, and silently ignore the latter.

For reference, the two tags are:

not working: <password xdbns="jabber:iq:auth">
working: <password xdbns="jabber:iq:auth" xmlns="jabber:iq:auth">

It can get configuration files without plain text passwords? with only SHA-1 stored passwords from jabber1.4?

thanks.