The schemaUpdateNow_fix_and_test bug

[Nadezhda Ivanova]

Hi Andrew,

Thanks for taking the time to try this again. I have been working on that and it seems that the hanging is muuuuch worse if we send the request via LDAP instead of using ldbmodify directly. What I have tried so far is to add a flag so that the addition of INTEGER and CASE_SENSITIVE are only added at bootstrapping, that is, that is not done if the indexes are generated because a schemaUpdateNow is invoked. I did this because you mentioned, and it is written in several places in the code, that we only need this at startup while we do not yet have a schema. It speeded up things, but not too much, besides it does not work - if I restart Samba afterwards, I get a message that the schema head is missing...
So what I plan to do now is to remove the fix, then make a profile using google tools. I know valgrind is mostly used, but I have more experience with google tools and I did not find how to make a cpu profile with valgrind. This will hopefully point out where we get the delay. Then I will make a python script to execute whjat we are doing via ldap, so that you can try it this way. If you still have no problem, we can start comparing system configurations. What do you think?

Regards,
Nadezhda Ivanova

----- Original Message -----
> From: Andrew Bartlett <abartlet at samba.org>
> To: Anatoliy Atanasov <anatoliy.atanasov at postpath.com>
> Cc: samba-technical at lists.samba.org <samba-technical at lists.samba.org>
> Sent: 11 November 2008 02:12:19 o'clock GMT+0200 Europe;Athens
> Subject: Re: The schemaUpdateNow_fix_and_test bug

> > On Tue, 2008-10-28 at 14:18 +1100, Andrew Bartlett wrote:
> > I've fixed one bug in your schemaUpdateNow_fix_and_test branch from
> > git://repo.or.cz/Samba/aatanasov.git, and uploaded it to
> > 
> >  git://git.samba.org/abartlet/samba.git schemaUpdateNow_fix_and_test
> > 
> > However, I can't reproduce the 'extended busy loop' you describe - 
> only
> > the hang in the client (fixed), and failure to add some schema 
> elements.
> > Can you dobule-check that your branch contains the exact version in
> > which you saw the issue?
> 
> I've again updated to the latest in this branch, but I still fail to 
> see
> anything like the behaviour you describe.  Certainly, the schema fails
> to load - but is that the error you are asking me to debug?
> 
> Could you perhaps check out this branch in a fresh tree yourself, and
> give me the exact command that fails, and a description of how it 
> fails?
> 
> Thanks,
> 
> Andrew Bartlett
> 
> -- 
> Andrew Bartlett                                
> http://samba.org/~abartlet/
> Authentication Developer, Samba Team           http://samba.org
> Samba Developer, Red Hat Inc.                  http://redhat.com