Hi everybody,
I have a (too much) successful jabber server with ~7700 registered users, and ~600 peak concurrent connections each day.
Result, jabberd1.4 is using up all the resources on my poor server. Hoping to get better performance and fault-tolerance, I'm trying ejabberd.
I'm trying to import .xml files from jabberd1.4, and -for some files- when I do ejabberdctl import-file file.xml, it goes on with no errors, but it doesn't create the new user.
Where could I have a look in order to solve this problem?
BTW, is there something I should need in order to run a server with such load?
Thanks,
Matteo
1) Which hardware do you
1) Which hardware do you have for your jabber server? Ejabberd requires more memory than jabberd1.4.
2) XML-files in jabberd1.4 spool may be corrupted. Try to repair them (e.g. using xmllint) before importing to ejabberd.
I've got 512 MB of RAM on a
I've got 512 MB of RAM on a server also running other services (mail and web server mostly), but a RAM update should be no big issue. The CPU is a P3 Coppermine@866 MHz.
At least some of the files I can't import are well formed, and give anyway the same result. As soon as I receive authorization from a user to publish his/her roster, I'll give you an example.
Thanks,
Matteo
Solved
I finally found the problem, after investigating a bit on the .xml files: it looks like some users are created with a <password xdbns="jabber:iq:auth"> in the password tag, and others with <password xdbns="jabber:iq:auth" xmlns="jabber:iq:auth">. Looks like ejabberd would import only the latter while silently ignoring the former. I'll write a bug report.
Matteo