On Tue, Aug 3, 2010 at 4:07 AM, Marc Dequènes (Duck) <d...@duckcorp.org> wrote:
>
> I just installed ejabberd on Squeeze, and found the server initialization
> fail, leaving it unusuable. The message in the log was:
> =ERROR REPORT==== 2010-08-03 01:30:28 ===
> Error in process <0.258.0> on node 'ejabb...@thorfinn.duckcorp.org' with
> exit value:
> {badarg,[{erlang,register,[asn1_driver_owner,<0.258.0>]},{asn1rt_driver_handler,init,2}]}
> =ERROR REPORT==== 2010-08-03 01:30:28 ===
> Error in process <0.259.0> on node 'ejabb...@thorfinn.duckcorp.org' with
> exit value:
> {badarg,[{erlang,register,[asn1_driver_owner,<0.259.0>]},{asn1rt_driver_handler,init,2}]}
> =ERROR REPORT==== 2010-08-03 01:30:28 ===
> Error in process <0.260.0> on node 'ejabb...@thorfinn.duckcorp.org' with
> exit value:
> {badarg,[{erlang,register,[asn1_driver_owner,<0.260.0>]},{asn1rt_driver_handler,init,2}]}Please, check if ejabberd 2.1.4-1 from sid works with erlang 1:14.a-dfsg-2. > > I downgraded to 1:13.b.4-dfsg-6 and it solved the problem. I then saw > erlang-base still provides erlang-abi-13.a, but for sure something changed > in the API/ABI, and it may be the cause of the problem. erlang-abi-13.a means that binary interface to C programs is compatible with Erlang R13A, which is true. So, it isn'r the bug source. Cheers! -- Sergei Golovan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
