[Date Prev][Date Next]
Re: slapadd: could not parse entry (line=14112)
This error indicates the input to slapadd(8) is malformed.
Specifically, the entry ending at line 7 does not meet all
LDAP model restriction (including those controlled by schema).
By adding some debugging options slapadd(8), you likely can
obtain more detail on the precise problem with the input
to slapadd(8). I note that you might try adding the
entry using ldapadd(1). Aside from generally being a more
appropriate tool for adding initial entries to the directory,
common errors for ldapadd(1) are enumerated and discussed
in the FAQ <<http://www.openldap.org/faq/index.cgi?file=53>http://www.openldap.org/faq/index.cgi?file=53>
(and elsewhere in the OpenLDAP documentation).
I note that as this script is not OpenLDAP Software, so
discussions specific to these scripts should be directed
elsewhere (such as a PADL-hosted mailing list)
At 08:42 AM 4/28/2005, LOEWENTHAL Simon wrote:
>I am very new to LDAP and this is the first time I have tried to set-up
>a server. We intend to move from NIS+ to LDAP, which means I have to
>test that it will work OK.
>I initially ran this PADL supplied script to convert my NIS+ dumped
>tables into LDIF, but the first time I ran it /slapadd /errored on the
>first blank line that separated each entry.
>slapadd: could not parse entry (line=7)
>So I put sed into the script to strip off each line. (I used this: cat
>$DB.tmp | sed -e'/^$/d' > $DB), which does the job.
>Creating naming context entries...
>Importing into LDAP...
>Migrating netgroups (by user)...
>Migrating netgroups (by host)...
>Preparing LDAP database...
>*slapadd: could not parse entry (line=14112)*
>However, when slapadd came to the end of the .ldif file it still gives
>the same error message but there are no blank lines nor are there any
>control characters hidden in the file.
>slapadd: could not parse entry (line=14112)
>Has anyone found away around this? I am using OpenLDAP 2.1.30.