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

[hyc@symas.com]

richton@nbcs.rutgers.edu wrote:
> Full_Name: Aaron Richton
> Version: 2.3.40
> OS: Solaris 9
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (128.6.31.135)
>
>
> $ ldapsearch -LLL '(cn=172.23.58.210)'
> dn:: Y249MbcyLjIzLjU4LjIxMCxjbj1DbGllbnRzLGNuPVJlc05ldCBTZXJ2aWNlIENvbmZpZyxvd
>   T1Ib3N0IENvbmZpZyxvPVJ1dGdlcnMgQ0NGLGM9VVM=
> objectClass: top
> objectClass: dhcpHost
> cn: 172.23.58.210
> dhcpStatements: fixed-address 172.23.58.210
> dhcpHWAddress: ethernet 00:17:3f:bf:c2:04
>
>
> Is it just me, or does my cn attribute not match the cn in the dn? Uhhh...now
> what?
> (and no, I wasn't using an editor on the bdb files, or whatever other conspiracy
> theory is out there.) Also, if it helps, you can see on openldap-software my
> other misadventures with 2.3.40...this is just one that's really easy to prove.

You didn't mention what backend you're using. I'd examine the dn2id.bdb file 
(use db_dump -p) and see if this DN is corrupted there. Also, was this entry 
created using 2.3.40, or using an earlier version? Interesting that the byte 
differs from the expected value by a single bit (it has its high bit set).

Personally I suspect the hardware is flaking out.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/