Bug#402164: it isn't about ldap, just Cyrus 2.1/2.2 and GSSAPI
Dennis Vshivkov
walrus at amur.ru
Tue Oct 7 06:46:45 UTC 2008
tags 402164 - moreinfo
Hello all,
regarding the `moreinfo': to me, it isn't likely that NSS/LDAP
have anything to do here.
I've a Cyrus mailstore server, that does not use libnss-ldap,
and no LDAP at all is involved in its setup.
Up to today it was running Cyrus 2.1. GSSAPI worked on it with
no problems quite some time ago, but wasn't used for a long
while. When trying to make use of it again, the same breakage
as reported by others was observed.
A log excerpt (Cyrus 2.1):
Oct 7 17:48:21 s6 cyrus/imapd[12030]: accepted connection
Oct 7 17:48:21 s6 cyrus/imapd[12030]: TLS engine: No CA file specified. Client side certs may not work
Oct 7 17:48:21 s6 cyrus/imapd[12030]: mystore: starting txn 2147483672
Oct 7 17:48:21 s6 cyrus/imapd[12030]: mystore: committing txn 2147483672
Oct 7 17:48:21 s6 cyrus/imapd[12030]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits new) no authentication
Oct 7 17:48:22 s6 cyrus/master[12018]: process 12030 exited, signaled to death by 11
Oct 7 17:48:22 s6 cyrus/master[12018]: service imap pid 12030 in BUSY state: terminated abnormally
Thinking that could be a good reason to upgrade Cyrus to 2.2, I
did that, successfully, let alone that the GSSAPI problem didn't
change at all.
A log excerpt (Cyrus 2.2):
Oct 7 19:15:58 s6 cyrus/imap[14694]: accepted connection
Oct 7 19:15:59 s6 cyrus/imap[14694]: mydelete: starting txn 2147483825
Oct 7 19:15:59 s6 cyrus/imap[14694]: mydelete: committing txn 2147483825
Oct 7 19:15:59 s6 cyrus/imap[14694]: mystore: starting txn 2147483826
Oct 7 19:15:59 s6 cyrus/imap[14694]: mystore: committing txn 2147483826
Oct 7 19:15:59 s6 cyrus/imap[14694]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits new) no authentication
Oct 7 19:16:01 s6 master[14639]: process 14694 exited, signaled to death by 11
Oct 7 19:16:01 s6 master[14639]: service imap pid 14694 in BUSY state: terminated abnormally
Packages:
cyrus-imapd-2.2 2.2.13-10
libkrb53 1.4.4-7etch6
libsasl2-modules-gssapi-mit 2.1.22.dfsg1-8
Not much in GDB:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212221216 (LWP 16246)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0xb65ca1a8 in ?? () from /usr/lib/libgssapi_krb5.so.2
#2 0xb65e1e88 in ?? () from /usr/lib/libgssapi_krb5.so.2
#3 0xb65ca8f0 in ?? () from /usr/lib/libgssapi_krb5.so.2
#4 0x00000000 in ?? ()
(gdb) _
Maybe the whole problem belongs to the krb5 package instead?
Cheers,
--
/Dennis Vshivkov <walrus at amur.ru>
More information about the Pkg-cyrus-sasl2-debian-devel
mailing list