time out in samba4.ldap.dirsync.python(dc) test

[Alexander Bokovoy]

Hi Andrew,

On Tue, Jul 10, 2012 at 10:38 AM, Andrew Bartlett <abartlet at samba.org> wrote:
> On Thu, 2012-04-12 at 17:09 +0300, Alexander Bokovoy wrote:
>> Hi,
>>
>> I'm seeing a time out while running samba4.ldap.dirsync.python(dc)
>> test in master (even before our kerberos refactoring work landed). It
>> all seems started with
>> https://git.samba.org/?p=samba.git;a=commitdiff;h=438971e214e6f55f19148ed2afc03ec1c7066f65
>> which landed in master on March 25th. I'm not sure why autobuild
>> didn't catch the time out.
>>
>> All I see in the output is neverending
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>> ldap: no matching message id for 23
>>
>> attaching strace shows that indeed there is a loop:
>
> Did you ever get anywhere on this?  This has re-appeared, and likewise I
> suspected changes in my tree, until I reproduced it with unmodified
> master.
No, I didn't.

> The attached patch helps, but I suspect it just masks the problem.
>
> It might be an issue in our SSL wrapped sockets client library.
I'll look at it soon, I haven't thought about this vector...
-- 
/ Alexander Bokovoy