Michael Menge
2014-09-17 12:35:02 UTC
Hi,
i have a Problem with Cyrus-Imapd 2.4.17 and libopenssl0_9_8-0.9.8j-0.62.1
openssl-0.9.8j-0.62.1 on a SLES 11 SP 3 (most recent versions for SLES 11)
We recently switched from a normal Cyrus to a Cluster Configuration
(aka Cyrus Murder). A frontend imapd will proxy the requests to the
backend where the mailbox is.
Some of these Frontend processes will trigger a SIGSEGV
I did run a bt on the core dump and it seems the SIGSEGV is in openssl.
I don't know if cyrus is not using openssl correct, of if it is only a
problem in openssl, but openssl should not trigger a SIGSEGV
#0 0x000000000080e130 in ?? ()
#1 0x00007fe5a839334f in ssl3_get_message (s=0x80e430, st1=8347825,
stn=-1470427072, mt=<optimized out>, max=102400, ok=0x7fffcc974d08)
at s3_both.c:522
#2 0x00007fe5a838ba0d in ssl3_get_key_exchange (s=0x0) at s3_clnt.c:1103
#3 0x00007fe5a838dff8 in ssl3_connect (s=0x80e430) at s3_clnt.c:316
#4 0x000000000046a177 in tls_start_clienttls (readfd=16, writefd=16,
layerbits=0x7fffcc975104, authid=0x7fffcc975108, ret=0x7e1fa0,
sess=0x7e1fa8) at tls.c:1311
#5 0x00000000004669f4 in do_starttls (s=0x7e16a0, tls_cmd=0x78a4d0
<imap_protocol+208>) at backend.c:201
#6 0x0000000000467217 in backend_authenticate (s=0x7e16a0,
prot=0x78a400 <imap_protocol>, mechlist=0x7fffcc976468,
userid=0x7f5c90 "REPLACED_LOGINID", cb=0x80de30,
status=0x7fffcc976460) at backend.c:378
#7 0x0000000000467a1a in backend_connect (ret_backend=0x7e16a0,
server=0x7a8960 <partition.17660> "ma03.mail.localhost",
prot=0x78a400 <imap_protocol>, userid=0x7f5c90
"REPLACED_LOGINID", cb=0x0, auth_status=0x0) at backend.c:552
#8 0x0000000000426603 in proxy_findserver (server=0x7a8960
<partition.17660> "ma03.mail.localhost", prot=0x78a400 <imap_protocol>,
userid=0x7f5c90 "REPLACED_LOGINID", cache=0x7a3010
<backend_cached>, current=0x7a3008 <backend_current>, inbox=0x7a3000
<backend_inbox>,
clientin=0x7be450) at proxy.c:179
#9 0x0000000000426beb in proxy_findinboxserver (userid=0x7f5b20
"REPLACED_LOGINID") at imap_proxy.c:145
#10 0x00000000004197c8 in cmd_list (tag=0x7f3720 "42.117",
listargs=0x7fffcc977510) at imapd.c:6036
#11 0x000000000040c9ee in cmdloop () at imapd.c:1574
#12 0x000000000040aea5 in service_main (argc=2, argv=0x7b9010,
envp=0x7fffcc97b650) at imapd.c:946
#13 0x0000000000409ba4 in main (argc=6, argv=0x7fffcc97b618,
envp=0x7fffcc97b650) at service.c:582
--------------------------------------------------------------------------------
M.Menge Tel.: (49) 7071/29-70316
UniversitÀt TÌbingen Fax.: (49) 7071/29-5912
Zentrum fÃŒr Datenverarbeitung mail:
michael.menge-***@public.gmane.org
WÀchterstraÃe 76
72074 TÃŒbingen
i have a Problem with Cyrus-Imapd 2.4.17 and libopenssl0_9_8-0.9.8j-0.62.1
openssl-0.9.8j-0.62.1 on a SLES 11 SP 3 (most recent versions for SLES 11)
We recently switched from a normal Cyrus to a Cluster Configuration
(aka Cyrus Murder). A frontend imapd will proxy the requests to the
backend where the mailbox is.
Some of these Frontend processes will trigger a SIGSEGV
I did run a bt on the core dump and it seems the SIGSEGV is in openssl.
I don't know if cyrus is not using openssl correct, of if it is only a
problem in openssl, but openssl should not trigger a SIGSEGV
#0 0x000000000080e130 in ?? ()
#1 0x00007fe5a839334f in ssl3_get_message (s=0x80e430, st1=8347825,
stn=-1470427072, mt=<optimized out>, max=102400, ok=0x7fffcc974d08)
at s3_both.c:522
#2 0x00007fe5a838ba0d in ssl3_get_key_exchange (s=0x0) at s3_clnt.c:1103
#3 0x00007fe5a838dff8 in ssl3_connect (s=0x80e430) at s3_clnt.c:316
#4 0x000000000046a177 in tls_start_clienttls (readfd=16, writefd=16,
layerbits=0x7fffcc975104, authid=0x7fffcc975108, ret=0x7e1fa0,
sess=0x7e1fa8) at tls.c:1311
#5 0x00000000004669f4 in do_starttls (s=0x7e16a0, tls_cmd=0x78a4d0
<imap_protocol+208>) at backend.c:201
#6 0x0000000000467217 in backend_authenticate (s=0x7e16a0,
prot=0x78a400 <imap_protocol>, mechlist=0x7fffcc976468,
userid=0x7f5c90 "REPLACED_LOGINID", cb=0x80de30,
status=0x7fffcc976460) at backend.c:378
#7 0x0000000000467a1a in backend_connect (ret_backend=0x7e16a0,
server=0x7a8960 <partition.17660> "ma03.mail.localhost",
prot=0x78a400 <imap_protocol>, userid=0x7f5c90
"REPLACED_LOGINID", cb=0x0, auth_status=0x0) at backend.c:552
#8 0x0000000000426603 in proxy_findserver (server=0x7a8960
<partition.17660> "ma03.mail.localhost", prot=0x78a400 <imap_protocol>,
userid=0x7f5c90 "REPLACED_LOGINID", cache=0x7a3010
<backend_cached>, current=0x7a3008 <backend_current>, inbox=0x7a3000
<backend_inbox>,
clientin=0x7be450) at proxy.c:179
#9 0x0000000000426beb in proxy_findinboxserver (userid=0x7f5b20
"REPLACED_LOGINID") at imap_proxy.c:145
#10 0x00000000004197c8 in cmd_list (tag=0x7f3720 "42.117",
listargs=0x7fffcc977510) at imapd.c:6036
#11 0x000000000040c9ee in cmdloop () at imapd.c:1574
#12 0x000000000040aea5 in service_main (argc=2, argv=0x7b9010,
envp=0x7fffcc97b650) at imapd.c:946
#13 0x0000000000409ba4 in main (argc=6, argv=0x7fffcc97b618,
envp=0x7fffcc97b650) at service.c:582
--------------------------------------------------------------------------------
M.Menge Tel.: (49) 7071/29-70316
UniversitÀt TÌbingen Fax.: (49) 7071/29-5912
Zentrum fÃŒr Datenverarbeitung mail:
michael.menge-***@public.gmane.org
WÀchterstraÃe 76
72074 TÃŒbingen