[Date Prev][Date Next]
Re: failed assertion ... ?
> I'm using OpenLDAP 2.1.5 on AIX.
> I'm loading for test a LDAP repository with ~700,000 people and
> organizations. Partway (most of the way) through my load, I start
> getting output from slapadd like the following:
> tools.c:182: failed assertion `text->bv_val == '\0''
> After I got that, once Every other slapadd run for the same objectclass
> failed immediately with the same error.
> Then, when I moved on to loadfiles of a different objectclass, they
> worked for a few dozen records, and the error re-asserted itself.
> Since this is a failed assertion, it appears to be a bust in slapadd
> itself, so '-c' doesn't work, of course.
> I think that the data is not bad, because I have loaded this subset of
> data, separately, on a different pass already.
> Does this error ring any bells? My web search didn't turn up anything
> very close.
Should be fixed in HEAD; you may get a HEAD snapshot or simply
comment out the assertion in back-ldbm/tools.c (and in back-bdb/tools.c
as well because it was way overconservative). Note that the problem
shows up only if you use -c, which is DEFINITELY A BAD PRACTISE if
not used in conjunction with -u (dry run) because you're likely
to end up with a broken db. If you simply wish to check whether
the entries are fine, you should use -c -u (which doesn't trigger
the problem you noted).