Bug#380059: marked as done (ejabberd: Ejabberd trows an error when trying to log in)

[Debian Bug Tracking System]

Your message dated Thu, 27 Jul 2006 22:59:27 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380059: ejabberd: Ejabberd trows an error when trying to 
log in
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---

Package: ejabberd
Version: 1.1.1-4
Severity: grave
Justification: renders package unusable

After upgrading to ejabberd 1.1.1-4 I can't login anymore. The log message is 
listed below.

Hylke

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.2
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: 
LC_ALL set to [EMAIL PROTECTED])

Versions of packages ejabberd depends on:
ii  adduser                       3.95       Add and remove users and groups
ii  erlang-base                   1:11.b.0-3 Concurrent, real-time, distributed
ii  erlang-nox                    1:11.b.0-3 Concurrent, real-time, distributed
ii  libc6                         2.3.6-16   GNU C Library: Shared libraries
ii  libexpat1                     1.95.8-3.2 XML parsing C library - runtime li
ii  libssl0.9.8                   0.9.8b-2   SSL shared libraries
ii  openssl                       0.9.8b-2   Secure Socket Layer (SSL) binary a
ii  zlib1g                        1:1.2.3-13 compression library - runtime

ejabberd recommends no packages.

-- no debconf information

-- Log messages 

=INFO REPORT==== 2006-07-27 10:17:45 ===
I(<0.230.0>:ejabberd_listener:90): (#Port<0.393>) Accepted connection 
{{137,224,32,204},55157} -> {{145,99,196,98},5222}

=ERROR REPORT==== 2006-07-27 10:17:45 ===
** Generic server <0.354.0> terminating
** Last message in was {tcp,#Port<0.393>,
                            <<"<?xml version='1.0'?><stream:stream 
xmlns=\"jabber:client\" to=\"noid.homelinux.org\" version=\"1.0\" 
xmlns:stream=\"http://etherx.jabber.org/streams\"; >">>}
** When Server state == {state,#Port<0.393>,
                               gen_tcp,
                               none,
                               <0.353.0>,
                               infinity,
                               {xml_stream_state,
                                   <0.353.0>,
                                   #Port<0.394>,
                                   [],
                                   0,
                                   infinity},
                               infinity}
** Reason for termination ==
** {badarg,[{erlang,binary_to_term,
                    
[<<0,0,0,0,131,108,0,0,0,1,104,2,97,0,104,2,107,0,13,115,116,114,101,97,109,58,115,116,114,101,97,109,108,0,0,0,4,104,2,107,0,5,120,109,108,110,115,107,0,13,106,97,98,98,101,114,58,99,108,105,101,110,116,104,2,107,0,2,116,111,107,0,18,110,111,105,100,46,104,111,109,101,108,105,110,117,120,46,111,114,103,104,2,107,0,7,118,101,114,115,105,111,110,107,0,3,49,46,48,104,2,107,0,12,120,109,108,110,115,58,115,116,114,101,97,109,107,0,32,104,116,116,112,58,47,47,101,116,104,101,114,120,46,106,97,98,98,101,114,46,111,114,103,47,115,116,114,101,97>>]},
            {xml_stream,parse,2},
            {ejabberd_receiver,process_data,2},
            {ejabberd_receiver,handle_info,2},
            {gen_server,handle_msg,6},
            {proc_lib,init_p,5}]}

-- end log messages

--- End Message ---

--- Begin Message ---

On 7/27/06, Sergei Golovan <[EMAIL PROTECTED]> wrote:

It's because erlang got upgraded to version 11.b.0. After a few days a
new ejabberd version will be uploaded to unstable. It will be compiled
using new erlang and the bug will be gone.

It is fixed in 1.1.1-5 which will hit the archive pretty soon.

Regards,
Torsten


--
http://www.twerner42.de/

--- End Message ---