--On Friday, October 21, 2011 6:34 PM +0000 michael@stroeder.com wrote:

hyc@symas.com wrote:

...

There's no evidence of an OpenLDAP bug here. All we can see from the testrun/slapd.1.log is that it took 15 seconds for slap_sasl_init to complete, which was long enough for the initial startup check to time out. You need to check your system to see why SASL took so long to initialize, most likely a DNS failure or some other transient issue.

Hmm, this was with a local build of cyrus-sasl 2.1.25 which seg faulted on GSSAPI in another test. I will retry with cyrus-sasl package shipped with openSUSE 11.4.

There was a patch posted to the cyrus-sasl list the other day for issues with the gssapi plugin in 2.1.25. It's working fine for me once it is fixed up.

quanah@zre-ldap001:~/p4/main/ThirdParty/cyrus-sasl/patches$ cat gssapi.patch --- cyrus-sasl-2.1.25/plugins/gssapi.c.orig 2011-10-07 14:47:07.461866240 -0700 +++ cyrus-sasl-2.1.25/plugins/gssapi.c 2011-10-07 14:47:45.891872589 -0700 @@ -370,7 +370,7 @@ }

if (output_token->value && output) { - unsigned char * p = (unsigned char *) text->encode_buf; + unsigned char * p;

ret = _plug_buf_alloc(text->utils, &(text->encode_buf), @@ -384,6 +384,8 @@ return ret; }

+ p = (unsigned char *) text->encode_buf; + p[0] = (output_token->length>>24) & 0xFF; p[1] = (output_token->length>>16) & 0xFF; p[2] = (output_token->length>>8) & 0xFF;

--Quanah

--

Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration