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
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
