Re: (ITS#3841) alock throws assertion with slapo-glue

[hyc@symas.com]

Thanks for the report. Tracing the run shows that bdb_db_close is being 
called on an instance that was never opened. alock is asserting here 
because it was expecting to release a valid lock but there was no lock 
at that point. Still working on the fix...

richton@nbcs.rutgers.edu wrote:
> Full_Name: Aaron Richton
> Version: 2.3.4
> OS: Solaris 9
> URL: 
> Submission from: (NULL) (128.6.31.135)
>
>
> While investigating ITS#3817 I found a number of:
>
> Assertion failed: info->al_slot > 0, file alock.c, line 207
>
> I've finally narrowed that down to a reasonable reproduction case. At a glance,
> it appears to occur with slapo-glue and disparate suffixes, that is dc=a and
> dc=b but not dc=x,dc=a and dc=y,dc=a.
>
> To play along at home:
>
> 1. ./run -b hdb test011 should succeed.
>
> 2. Edit the slapd.1.conf; we'll move "Groups" to be far away. For instance:
>
> 49c49
> < suffix                "dc=breakme,dc=org"
> ---
>   
>> suffix                "ou=Groups,dc=example,dc=com"
>>     
> 51c51
> < rootdn                "cn=Manager, dc=breakme,dc=org"
> ---
>   
>> rootdn                "cn=Manager, dc=example,dc=com"
>>     
> 76c76
> < #glue-sub             "ou=Groups,dc=example,dc=com"
> ---
>   
>> glue-sub              "ou=Groups,dc=example,dc=com"
>>     
>
> 3. Clean up the databases thoroughly:
> rm testrun/db*/*
>
> 4. slapadd again:
> slapadd -b "dc=example,dc=com" -l testrun/ldif.flt -f testrun/slapd.1.conf
>
>
> On my system, this returns:
>
> Assertion failed: info->al_slot > 0, file alock.c, line 207
> Abort
>
>
> Since example.com is hosted as a hdb, I'd expect that slapadd to work.
>
>
>   


-- 
  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support