[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: slapadd: could not parse entry (line=13)

-There are no indents in the ldiff file. 
  -The ldiff file was created from the 2.2 version. I was able to import it to openldap 2.3.20 but not 2.3.24. 
  how can i remove the operational attributes ?

Mark Andrews <mandrews@magma.ca> wrote:
  Moe wrote:
> dn: dc=local,dc=gov
> objectClass: dcObject
> objectClass: organization
> o: TRPDD
> dc: local
> structuralObjectClass: organization
> entryUUID: a8b6c68a-afc1-1029-96b4-feb336e41fbf
> creatorsName: cn=admin,dc=local,dc=gov
> createTimestamp: 20050902055341Z
> entryCSN: 20050902055341Z#000001#00#000000
> modifiersName: cn=admin,dc=local,dc=gov
> modifyTimestamp: 20050902055341Z
> dn: cn=admin,dc=local,dc=gov
> objectClass: organizationalRole
> cn: admin
> structuralObjectClass: organizationalRole
> entryUUID: b70a3c8a-afc1-1029-96b5-feb336e41fbf
Why are your distinguished name attributes indented? Get rid of the 
leading space and read the ldif(5)
manual page.

It clearly states that leading spaces (or tabs) are used to indicate 
continuation from the previous
line, the same behavior as the email aliases file ... that's likely 
what's tripping up OpenLDAP ..

And before you ask "How come it works with older versions of the 
software", it was likely a
bug and the code has been cleaned up to better follow the RFCs ...

Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.