Re: (ITS#5342) DN and naming attribute mismatch

[richton@nbcs.rutgers.edu]

> Have you got any servers running 2.3.39, or all 2.3.37?

Everything went from 2.3.37 -> 2.3.40. Since I get hosed w/err=80, 
the slaves don't have corrupt data. I'm thinking about moving the master 
down to 2.3.39 as a data point.

In the meantime, thanks for the db_dump idea; I can now show that the bad 
commits are definitely (a) 2.3.40 and (b) increasing. Consider:

# grep 172.23.93.232 dbdump*
dbdump.Jan291845: \80\10cn=172.23.93.232\00cn=172.23.93.232\00\00\00\00\00\00\01\d3\8d
dbdump.Jan291845: \00\10cn=172.23.93.232\00cn=172.23.93.232\00\00\00\00\00\00\00\01>
dbdump.Jan301043: \80\10cn=172.23.93.232\00cn=1\b72.23.93.232\00\00\00\00\00\00\01\d3\8d
dbdump.Jan301043: \00\10cn=172.23.93.232\00cn=172.23.93.232\00\00\00\00\00\00\00\01>