Ubuntu server 10.0.4, ldap 2.4.21
I am getting the following error when attempting to use the ldapadd command:
sudo ldapadd -Y EXTERNAL -H ldapi:/// -f db.ldif
(error) adding new entry "cn=module{0},cn=config" ldap_add: Naming violation (64)
db.ldif: # Load modules for database type dn: cn=module{0},cn=config objectClass: olcModuleList cn: module{0} olcModulePath: /usr/lib/ldap olcModuleLoad: {0}back_hdb
# Create directory database dn: olcDatabase={1}hdb,cn=config objectClass: olcDatabaseConfig objectClass: olcHdbConfig olcDatabase: {1}hdb olcDbDirectory: /var/lib/ldap olcSuffix: dc=2190-db,dc=org olcRootDN: cn=admin,dc=isd2190-db,dc=org olcRootPW: 1234 olcAccess: {0}to attrs=userPassword,shadowLastChange by dn="cn=admin,dc=isd2190-db,dc=org" write by anonymous auth by self write by * none olcAccess: {1}to dn.base="" by * read olcAccess: {2}to * by dn="cn=admin,dc=isd2190-db,dc=org" write by * read olcLastMod: TRUE olcDbCheckpoint: 512 30 olcDbConfig: {0}set_cachesize 0 2097152 0 olcDbConfig: {1}set_lk_max_objects 1500 olcDbConfig: {2}set_lk_max_locks 1500 olcDbConfig: {3}set_lk_max_lockers 1500 olcDbIndex: uid pres,eq olcDbIndex: cn,sn,mail pres,eq,approx,sub olcDbIndex: objectClass eq
################################################## ######### # DEFAULTS MODIFICATION ################################################## ######### # Some of the defaults need to be modified in order to allow # remote access to the LDAP config. Otherwise only root # will have administrative access. dn: cn=config changetype: modify delete: olcAuthzRegexp dn: olcDatabase={-1}frontend,cn=config changetype: modify delete: olcAccess dn: olcDatabase={0}config,cn=config changetype: modify add: olcRootPW olcRootPW: {CRYPT}7hzU8RaZxaGi2 dn: olcDatabase={0}config,cn=config changetype: modify delete: olcAccess
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 command:
sudo ldapadd -Y EXTERNAL -H ldapi:/// -f db.ldif
(error) adding new entry "cn=module{0},cn=config" ldap_add: Naming violation (64)
Could you provide the matching log entries from slapd?
db.ldif: # 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?
Regards, Buchan
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 command:
sudo ldapadd -Y EXTERNAL -H ldapi:/// -f db.ldif
(error) adding new entry "cn=module{0},cn=config" ldap_add: Naming violation (64)
Could you provide the matching log entries from slapd?
db.ldif: # 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?
Regards, Buchan
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 command:
sudo ldapadd -Y EXTERNAL -H ldapi:/// -f db.ldif
(error) adding new entry "cn=module{0},cn=config" ldap_add: Naming violation (64)
Could you provide the matching log entries from slapd?
db.ldif: # 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?
Regards, Buchan
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.
I haven't a build with backends built as modules handy; I have tried a modification like yours that loads another module and it works as intended, so I have no clue.
If you could successfully run any of the tests that actually load modules and use them (e.g. test022, test049, test050, test052, test053, test05-9 then you should check how they loaded the modules and find out yourself what the error is.
p.
openldap-technical@openldap.org
-
Buchan Milne -
masaratiļ¼ aero.polimi.it -
Raymond Norton