Re: (ITS#5510) Does GSSAPI failure kill slapd?

[quanah@zimbra.com]

Send all response to the ITS, rather than me.  If you want them 
investigated, anyhow.

--Quanah

--On Wednesday, May 14, 2008 3:14 PM -0400 "Allan E. Johannesen" 
<aej@WPI.EDU> wrote:

>>>>>> "quanah" == Quanah Gibson-Mount <quanah@zimbra.com> writes:
>
> quanah> --On Wednesday, May 14, 2008 5:41 PM +0000 aej@wpi.edu wrote:
>>> Full_Name: Allan E. Johannesen Version: 2.4.9 OS: RHEL4 i686 URL:
>>> Submission from: (NULL) (130.215.24.208)
>>>
>>>
>>> slapd appeared to exit after this:
>>>
>>> May 14 13:05:42 ALUM slapd[28252]: SASL [conn=1] Failure: GSSAPI Error:
>>> The context has expired (No error) May 14 13:05:42 ALUM slapd[28252]:
>>> send_search_entry: conn 1 ber write failed.
>>>
>>> Is termination expected or should I look for something else?
>>>
>>> Thanks.
>>>
>>> If you want me to post anything about the environment, please let me
>>> know.
>
> quanah> Make sure you have debugging symbols enabled, gdb slapd, repeat,
> send quanah> in the backtrace.
>
> (gdb) r -d32768 -h ldap:/// ldaps:/// -f /var/openldap/slapd.conf
> Starting program:
> /tools/src/openldap/RHEL4-i686/openldap-2.4.9/servers/slapd/slapd -d32768
> -h ldap:/// ldaps:/// -f /var/openldap/slapd.conf [Thread debugging using
> libthread_db enabled]
> [New Thread -1209116992 (LWP 19050)]
> @(#) $OpenLDAP: slapd 2.4.9 (May  9 2008 08:02:12) $
> 	aej@CCC1.WPI.EDU:/tools/src/openldap/RHEL4-i686/openldap-2.4.9/servers/s
> lapd [New Thread -1728967776 (LWP 19053)]
> [Thread -1728967776 (LWP 19053) exited]
> [New Thread -1728967776 (LWP 19054)]
> [Thread -1728967776 (LWP 19054) exited]
> slapd starting
> [New Thread -1728967776 (LWP 19055)]
> [New Thread 2035399584 (LWP 19056)]
> [New Thread 2031201184 (LWP 19057)]
> [New Thread 2027002784 (LWP 19058)]
> SASL [conn=1] Error: unable to open Berkeley db /etc/sasldb2: No such
> file or directory SASL [conn=1] Error: unable to open Berkeley db
> /etc/sasldb2: No such file or directory SASL [conn=33] Error: unable to
> open Berkeley db /etc/sasldb2: No such file or directory SASL [conn=33]
> Error: unable to open Berkeley db /etc/sasldb2: No such file or directory
> [New Thread 1994468256 (LWP 19109)]
> [New Thread 1980824480 (LWP 19168)]
> [New Thread 1967180704 (LWP 19169)]
> [New Thread 1962982304 (LWP 19170)]
> connection_read(20): no connection!
>
> connection_read(20): no connection!
> SASL [conn=33] Failure: GSSAPI Error: The context has expired (No error)
> sb_sasl_write: failed to encode packet: generic failure
> send_search_entry: conn 33  ber write failed.
> slapd: rq.c:92: ldap_pvt_runqueue_remove: Assertion `e == entry' failed.
>
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 2027002784 (LWP 19058)]
> 0x00a977a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> (gdb) (gdb) where
># 0  0x00a977a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
># 1  0x00ad8815 in raise () from /lib/tls/libc.so.6
># 2  0x00ada279 in abort () from /lib/tls/libc.so.6
># 3  0x00ad1d91 in __assert_fail () from /lib/tls/libc.so.6
># 4  0x08114473 in ldap_pvt_runqueue_remove (rq=0x82c1820, entry=0x4a72)
># at rq.c:92 5  0x080ffd9f in syncprov_free_syncop (so=0x83fe198) at
># syncprov.c:744 6  0x0810011d in syncprov_qtask (ctx=0x78d19210,
># arg=0x84aa898) at syncprov.c:949 7  0x08113cfd in
># ldap_int_thread_pool_wrapper (xpool=0x82e6ab0) at tpool.c:663 8
># 0x00d123cc in start_thread () from /lib/tls/libpthread.so.0
># 9  0x00b7a1ae in clone () from /lib/tls/libc.so.6
> (gdb) quit
> The program is running.  Exit anyway? (y or n) y
> ALUM:/tools/src/openldap/RHEL4-i686/openldap-2.4.9/servers/slapd$



--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration