Migration from jabberd1+jit to ejabberd+jit

Several years jabberd1 was work.
Now we need some possibilites of ejabberd.
I'm install ejabberd and jabber-jit (+jabber package for xdb_file.so) from Debian/unstable
Successfully configure ejabberd and jabber-jit (work for my new account fine, including icq).

Try to migrate another users (ejabberdctl for jabber users and simply copy .xml for jit)

Jabber-only accounts has no problem.

Accounts with icq does not login to icq automatically, but need to enter icq password

Is it normal, or may be something wrong in config?

jabber-jit must use its own

jabber-jit must use its own xdb_file.so. In official Debian package jabber-jit is built without xdb_file.so and uses XDB service, provided by main jabber server.

ejabberd does not provide XDB, so jabber-jit can't store users' registration data.

One solution is to get jabber-jit package from http://sgolovan.nes.ru/jabber/ (this URL contains link to Debian repository), which is built with xdb_file.so.

You also will have to convert spool to jabber-jit format. The following script does this: http://sgolovan.nes.ru/tmp/j2jit.sh

Re: jabber-jit must use its own

teo wrote:

jabber-jit must use its own xdb_file.so. In official Debian package jabber-jit is built without xdb_file.so and uses XDB service, provided by main jabber server.

ejabberd does not provide XDB, so jabber-jit can't store users' registration data.

May be solution is install jabberd package with xdb_file.so?
Do not start jabberd1, only install it.

Quote:

One solution is to get jabber-jit package from http://sgolovan.nes.ru/jabber/ (this URL contains link to Debian repository), which is built with xdb_file.so.

I want to use distributive-only repository.

Quote:

You also will have to convert spool to jabber-jit format. The following script does this: http://sgolovan.nes.ru/tmp/j2jit.sh

403 Forbidden

I'm already use jit spool in this format on old server, so i think it does not need.

jabberd-jit can't use

jabberd-jit can't use jabber's xdb_file.so.

If you want to use only packages from debian.org then you have to file bugreport to jabber-jit package. In its current state it is unusable without installed and running jabberd.

As a workaround you may let jabberd14 run without port listening and link jabber-jit to it. But I think that its an ugly solution.

Re: jabberd-jit can't use

teo wrote:

If you want to use only packages from debian.org then you have to file bugreport to jabber-jit package. In its current state it is unusable without installed and running jabberd.

I already tried this in the past, but the author of all these transport packages didn't saw a need to fix this -- easy to fix -- issue in his packages. If it would be fixed, the transports would be usable with any Jabber server.

So what can you do:

  • File bug reports for all transport packages that depend on Jabberd 1.4.3.1
  • Use the pytransport (they are maintained very well, whilst the C-based transports aren't)
  • File a request for pytransport packages in Debian.
  • Compile JIT yourself (difficult, but if you like to do it; ask me in the ejabberd room)
  • Stop using proprietary networks (the best solution ;-) )
Syndicate content