--On Wednesday, October 21, 2009 4:30 PM +0000 [email protected] wrote:
> Investigating the server side, running slapd at -d -1, things always work > correctly. Running slapd -d 0, things do not. So it is not related to > forking vs no-forking. But it is related in some way to debug level. There's definitely something involved with the size of the request. For example, mixing things up and using: suaffiliation suprivilegegroup uid instead of: suaffiliation suprivilegegroup mail also freezes. But with a different read value error: sasl_read: want=4, got=4 0000: 00 00 00 52 ...R sasl_read: want=82, got=53 0000: 05 04 07 ff 00 00 00 1c 00 00 00 00 36 cc 15 1d ............6... 0010: 99 41 1e 21 3f dd ac 8d 03 eb 2d 76 b8 5b 08 de .A.!?.....-v.[.. 0020: b5 23 41 69 66 9e 62 8f cf cc 42 35 c7 a7 b2 57 .#Aif.b...B5...W 0030: c3 07 7e 59 f3 ..~Y. Where mail is always: sasl_read: want=82, got=39 Switching out for displayname, we get: sasl_read: want=82, got=41 Changing to uid suprivilegegroup displayname we get: sasl_read: want=82, got=57 Changing to uid suprivilegegroup displayname suaffiliation cn the query works. There's obviously some flaw in length generation somewhere. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
