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

Re: ldapadd Naming Violation error 64

In researching this error, the general consensus was that it occurs when using a poorly written client that did not terminate correctly, but was nothing to worry about.

However, I am unable to import the ldif file that I included in my first post.

Any ideas what I should be looking for?

In response to one reply, yes  /usr/lib/ldap/back_hdb.la does exist.

On 8/2/2010 9:07 PM, Raymond Norton wrote:
 slapd[2929]: connection_read(13): no connection!

On 8/2/2010 5:37 AM, Buchan Milne wrote:
On Saturday, 31 July 2010 12:49:27 Raymond Norton wrote:
Ubuntu server 10.0.4, ldap 2.4.21

I am getting the following error when attempting to use the ldapadd

sudo ldapadd -Y EXTERNAL -H ldapi:/// -f db.ldif

adding new entry "cn=module{0},cn=config"
ldap_add: Naming violation (64)
Could you provide the matching log entries from slapd?

# Load modules for database type
dn: cn=module{0},cn=config
objectClass: olcModuleList
cn: module{0}
olcModulePath: /usr/lib/ldap
olcModuleLoad: {0}back_hdb
I don't think it is the cause, but shouldn't this be:

olcModuleLoad: {0}back_hdb.la

Or, does /usr/lib/ldap/back_hdb actually exist?