Your message dated Wed, 25 May 2005 16:17:04 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#309526: fixed in ejabberd 0.9.1-1
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 May 2005 18:42:03 +0000
>From [EMAIL PROTECTED] Tue May 17 11:42:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from debianforum.de (mail.debianforum.de) [213.239.213.245]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DY710-0006mg-00; Tue, 17 May 2005 11:42:02 -0700
Received: from localhost (localhost [127.0.0.1])
by mail.debianforum.de (Postfix) with ESMTP id 7E4ADB1C046
for <[EMAIL PROTECTED]>; Tue, 17 May 2005 20:41:58 +0200 (CEST)
Received: from mail.debianforum.de ([127.0.0.1])
by localhost (mail.debianforum.de [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 23793-10 for <[EMAIL PROTECTED]>;
Tue, 17 May 2005 20:41:55 +0200 (CEST)
Received: by mail.debianforum.de (Postfix, from userid 1002)
id E4E77B1C08C; Tue, 17 May 2005 20:41:54 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Patrick Dreker <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: ejabberd: last update of erlang/erlang-base causes SSL to fail after
some
time
X-Mailer: reportbug 3.8
Date: Tue, 17 May 2005 20:41:54 +0200
X-Debbugs-Cc: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at debianforum.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: ejabberd
Version: 0.9-1
Severity: important
We are running the current version of ejabberd on Debian Sarge, using
pinning. Yesterday a dist-upgrade pulled in a new version of erlang and
erlang-base and since this time connecting to eJabberd via SSL fails
after some time. After restarting ejabberd SSL works again for some time
(a few hours) and then fails again.
On connection attempt the following is logged:
/var/log/ejabberd/ejabberd.log:
=INFO REPORT==== 2005-05-17 20:33:11 ===
I(<0.494.0>:ejabberd_listener:90): (#Port<0.698>) Accepted connection
{{<CLIENT_IP>},21863} -> {{<SERVER_IP>},5223}
No more entries in ejabberd.log (IPs obfuscated, checked, and they are
correct...)
/var/log/ejabberd/sasl.log show the following entries:
=CRASH REPORT==== 17-May-2005::20:32:51 ===
crasher:
pid: <0.483.0>
registered_name: []
error_info: {{badmatch,{error,"ssl_ctx_use_certificate_chain_file
failed"}},
[{ejabberd_c2s,init,1},
{gen_fsm,init_it,6},
{proc_lib,init_p,5}]}
initial_call: {gen,init_it,
[gen_fsm,
<0.213.0>,
<0.213.0>,
ejabberd_c2s,
[{gen_tcp,#Port<0.680>},
[{access,c2s},
tls,
{certfile,"/etc/ssl/certs/ejabberd.pem"},
{shaper,c2s_shaper}]],
[]]}
ancestors: [ejabberd_c2s_sup,ejabberd_sup,<0.36.0>]
messages: []
links: [<0.213.0>,#Port<0.681>]
dictionary: []
trap_exit: false
status: running
heap_size: 610
stack_size: 21
reductions: 326
neighbours:
=SUPERVISOR REPORT==== 17-May-2005::20:32:51 ===
Supervisor: {local,ejabberd_listeners}
Context: child_terminated
Reason: {{badmatch,{error,{{badmatch,
{error,
"ssl_ctx_use_certificate_chain_file
failed"}},
[{ejabberd_c2s,init,1},
{gen_fsm,init_it,6},
{proc_lib,init_p,5}]}}},
[{ejabberd_listener,accept,3},{proc_lib,init_p,5}]}
Offender: [{pid,<0.222.0>},
{name,5223},
{mfa,{ejabberd_listener,
start,
[5223,
ejabberd_c2s,
[{access,c2s},
tls,
{certfile,"/etc/ssl/certs/ejabberd.pem"},
{shaper,c2s_shaper}]]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]
these messages (at least the supervisor report) are repeated for every
login attempt via SSL.
I have recompiled ejabberd against the new erlang packages, but no
change. After a few minutes/hours SSL fails again...
regards,
Patrick
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (700, 'testing'), (650, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-amdk7-grsec
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages ejabberd depends on:
ii erlang 1:10.b.5-1 A real-time, concurrent and distri
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libexpat1 1.95.8-3 XML parsing C library - runtime li
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii openssl 0.9.7e-3 Secure Socket Layer (SSL) binary a
-- no debconf information
---------------------------------------
Received: (at 309526-close) by bugs.debian.org; 25 May 2005 20:24:29 +0000
>From [EMAIL PROTECTED] Wed May 25 13:24:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Db2QW-0004Bx-00; Wed, 25 May 2005 13:24:29 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1Db2JM-0002tO-00; Wed, 25 May 2005 16:17:04 -0400
From: Torsten Werner <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#309526: fixed in ejabberd 0.9.1-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 25 May 2005 16:17:04 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: ejabberd
Source-Version: 0.9.1-1
We believe that the bug you reported is fixed in the latest version of
ejabberd, which is due to be installed in the Debian FTP archive:
ejabberd_0.9.1-1.diff.gz
to pool/main/e/ejabberd/ejabberd_0.9.1-1.diff.gz
ejabberd_0.9.1-1.dsc
to pool/main/e/ejabberd/ejabberd_0.9.1-1.dsc
ejabberd_0.9.1-1_i386.deb
to pool/main/e/ejabberd/ejabberd_0.9.1-1_i386.deb
ejabberd_0.9.1.orig.tar.gz
to pool/main/e/ejabberd/ejabberd_0.9.1.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Torsten Werner <[EMAIL PROTECTED]> (supplier of updated ejabberd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 25 May 2005 23:55:28 +0200
Source: ejabberd
Binary: ejabberd
Architecture: source i386
Version: 0.9.1-1
Distribution: unstable
Urgency: low
Maintainer: Torsten Werner <[EMAIL PROTECTED]>
Changed-By: Torsten Werner <[EMAIL PROTECTED]>
Description:
ejabberd - Distributed, fault-tolerant Jabber/XMPP server written in Erlang
Closes: 309526
Changes:
ejabberd (0.9.1-1) unstable; urgency=low
.
* New upstream release, closes: #309526
* added --enable-odbc to configure
* small fix to init script
* thanks to Sergei Golovan <[EMAIL PROTECTED]> for helping
Files:
dbba6d5b01fed0f925b96e3bebaa6d08 637 net optional ejabberd_0.9.1-1.dsc
77b9d1a080b7ed2cf471e28d9cdcdf12 689516 net optional ejabberd_0.9.1.orig.tar.gz
76605104e8d82a0bee1d0c2637608a5e 10029 net optional ejabberd_0.9.1-1.diff.gz
01020b6e03d7f9fedae04674ddba2fd1 466142 net optional ejabberd_0.9.1-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFClPUZfY3dicTPjsMRAkrUAKCSu1mcCfXM38zdLCwxwg/HgmF/jgCfb26X
P2W2Ccj6W9+JDsY0Xs9rYLk=
=O8h3
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
