ejabberd - Comments for "Upgrade 2.0.5 to 2.1.x, can't start"

Thank you for that

sascha@kruszka.de — Sun, 17 Jan 2010 19:45:35 +0000

Thank you for that information. I'll try it in an free minute.

It was bug in ejabberd; try patch.

mfoss — Sat, 16 Jan 2010 12:36:00 +0000

Quote:

Is the bad arg "otp_release" in that case?

Right, it seems Erlang R10 and R11 didn't implement yet that argument. So it is a bug in ejabberd for expecting all versions to support it.

I've fixed in ejabberd SVN/Git, so the next ejabberd release (planned for the next weeks) will work correctly. Or you can apply the simple patch to your source code:
http://github.com/processone/ejabberd/commit/2de9eac1e305f4ad39d31d1be59...

unless I don't have a

sascha@kruszka.de — Fri, 15 Jan 2010 22:38:16 +0000

unless I don't have a something wrong im my syntax, something seems to be strange:

Eshell V5.5.2  (abort with ^G)
1> erlang:system_info(otp_release).
** exited: {badarg,[{erlang,system_info,[otp_release]},
                    {erl_eval,do_apply,5},
                    {shell,exprs,6},
                    {shell,eval_loop,3}]} **
=ERROR REPORT==== 15-Jan-2010::22:34:45 ===
Error in process <0.29.0> with exit value: {badarg,[{erlang,system_info,[otp_release]},{erl_eval,do_apply,5},{shell,exprs,6},{shell,eval_loop,3}]}

Is the bad arg "opt_release" in that case?

Should work. Test this

mfoss — Fri, 15 Jan 2010 20:29:18 +0000

Eshell V5.5.2 is included in Erlang R11B-2, as you can see. So this should be enough for running ejabberd 2.1.x.

I don't understand why you get that error message. Try this, and show what do you get:

This is what I get in R12B-5 and R13B-3 (the versions that I can try):

$ erl
Erlang (BEAM) emulator version 5.6.5 [source] [async-threads:0] [kernel-poll:false]

Eshell V5.6.5  (abort with ^G)
1> erlang:system_info(otp_release).
"R12B"
2> q().
ok
$

And:

$ erl
Erlang R13B03 (erts-5.7.4) [source] [smp:2:2] [rq:2] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V5.7.4  (abort with ^G)
1> erlang:system_info(otp_release).
"R13B03"
2> q().
ok
$

Thank you for your reply, but

sascha@kruszka.de — Fri, 15 Jan 2010 18:53:58 +0000

Thank you for your reply,

but I'm a little bit confused. You are talking about a Version R10B-9 or higher and I've got a version 5.5.2 installed (Debian etch package):

Erlang (BEAM) emulator version 5.5.2 [source] [async-threads:0] [kernel-poll:false]
Eshell V5.5.2  (abort with ^G)

Package Version:

Package: erlang
Priority: optional
Section: interpreters
Installed-Size: 68
Maintainer: Erlang Packagers <erlang-pkg-devel@lists.berlios.de>
Architecture: all
Version: 1:11.b.2-4

Doese anyone know if it is too old?

Maybe you have very old Erlang version?

mfoss — Mon, 11 Jan 2010 18:52:42 +0000

Quote:

My server don't have IPv6 support. I guess it could be the problem

If you mention lack of IPv6 because you saw this in the error: {ejabberd_listener,init_tcp,6}, don't worry: that 6 has nothing to do with IP version 6.

Maybe you are using a very old version of Erlang. ejabberd 2.1.1 (and also current SVN) requires Erlang/OTP R10B-9 or higher. The recommended version is R12B-5. Support for R13 is experimental.

If that is your case, you have at least three options:

If that old Erlang is the newest provided by your OS, you can try to get a more recent package from a more recent OS version. Problem: dependencies of that new package may not be available for you.
You can download, compile and install from source code Erlang/OTP. Problem: it will take one or two hours to compile, probably.
You can download and install ejabberd binary installer from ProcessOne, which includes a minimal Erlang inside, so you don't need to worry about Erlang dependency. Problem: it's a standalone package, so you would need to write the init.d script and logrotate.