Recently, erlang-15.2 became stable. Ejabberd 2.1.9 refuses to start and fails with errors like this: =ERROR REPORT==== 2012-05-23 09:56:12 === Error in process <0.175.0> on node 'ejabberd@it1' with exit value: {{case_clause,{error,driver_inc orrect_version}},[{ejabberd_app,init,0,[]}]} =INFO REPORT==== 2012-05-23 09:56:13 === application: ejabberd exited: {bad_return, {{ejabberd_app,start,[normal,[]]}, {'EXIT', {badarg, [{erlang,port_control, [stringprep_port,2,"localhost"], []}, {stringprep,control,2,[]}, {jlib,nodeprep,1,[]}, {ejabberd_config,normalize_hosts,2,[]}, {ejabberd_config,add_hosts_to_option,2,[]}, {lists,foldl,3,[{file,"lists.erl"},{line,1197}]}, {ejabberd_config,load_file,1,[]}, {ejabberd_config,start,0,[]}]}}}} type: temporary A bit of googling around found e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657759 which suggests that ejabberd-2.1.9 will not work with the newer erlang version - looks like this dependency slipped in the stabilization process. As a workaround, I updated to ejabberd-2.1.10 which worked for me. So I guess ejabberd-2.1.10 should be stabilized to prevent other users to fall into the same trap.
(In reply to comment #0) > Recently, erlang-15.2 became stable. Ejabberd 2.1.9 refuses to start and > fails with errors like this: Is ok here: amd64box ~ # /etc/init.d/ejabberd start ejabberd | * Starting ejabberd ... [ ok ] amd64box ~ # amd64box ~ # qlist -ICv | grep erlang dev-lang/erlang-15.2
I'm seeing what Dirk Olmes is seeing. net-im/ejabberd-2.1.9 doesn't work for me on an amd64 with dev-lang/erlang-15.2 (aka R15B), even after a rebuild of ejabberd-2.1.9. The init script looks like it worked, but the logs disagree. (Uname: Linux bain 2.6.39-hardened-r8 #4 SMP PREEMPT Sat Jan 21 16:40:55 EST 2012 x86_64 AMD Phenom(tm) II P960 Quad-Core Processor AuthenticAMD GNU/Linux)
(In reply to comment #0) > Recently, erlang-15.2 became stable. Ejabberd 2.1.9 refuses to start and > As a workaround, I updated to ejabberd-2.1.10 which worked for me. So I > guess ejabberd-2.1.10 should be stabilized to prevent other users to fall > into the same trap. Can confirm that. Works either ejabberd-2.1.9 with erlang-13.2.4 either ejabberd-2.1.10 with erlang-15.2. ejabberd-2.1.9 with erlang-15.2 does not work.
I confirm this on x86. You can also see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657759
I can confirm this bug on ~amd64.
Sounds like 2.1.9 should get marked that it doesn't work with 15.2 at minimum. The stabilization of 2.1.10 would be nice.
I just hit that one. Only reverting erlang back to previous stable (erlang-13.2.4) does not constitute a painless workaround, since it does not build with latest stable zlib (1.2.5.1-r2). See bug <a href="https://bugs.gentoo.org/show_bug.cgi?id=383697">383697</a>, comment 17. I had to unmask ejabberd-2.1.10, to make it work again.
Sounds like stabilization of ejabberd-2.1.10 would be a good thing. It's been working for me for several days without issue on an amd64.
*** Bug 418145 has been marked as a duplicate of this bug. ***
2.1.10 is being stabilized in bug #418313.
Closing since this shouldn't be an issue anymore with 2.1.10 now stabilized.
*** Bug 424037 has been marked as a duplicate of this bug. ***
