enterprise-support team mailing list archive

[Jacobsallan <question183862@xxxxxxxxxxxxxxxxxxxxx>]

Question #183862 on openldap in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/openldap/+question/183862

Jacobsallan requested more information:
More to the point is an entry
http://ubuntuforums.org/archive/index.php/t-1594138.html.  I seem to
have recommended a fix the ldif file in 2010.  The line "olcModuleload:
back_hdb" should read "olcModuleload: back_hdb.la".

Got it. Adding an extension to the filename value fixes the LDIF file
used to load database modules (backend.example.com.ldif).

% cat backend.dlinkddns.com.ldif
# Load dynamic backend modules
dn: cn=module,cn=config
objectClass: olcModuleList
cn: module
olcModulepath: /usr/lib/ldap
olcModuleload: back_hdb.la
...

There is still a problem with frontend.example.com.ldif; it seems to be
either attempting to reload an entry for 'dc=example,dc=com' or to be
invalid. The existence of the node is confirmed by using the ldapsearch
utility to list nodes.

% ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: namingContexts
#
#
dn:
namingContexts: dc=dlinkddns,dc=com
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1

My guess is that the front end LDIF should start with something like

# Create top-level object in domain
dn: ou=orgs,dc=example,dc=com
objectClass: top
objectClass: dcObject
objectclass: organizationalUnit
ou: orgs

dn: o=Example Organization,ou=orgs,dc=example,dc=com
objectClass: organization
o: Example Organization

o: Example Organization
description: LDAP Example

Does this help?

In 2010, I seem to have found other mistakes in the documentation that
you will hit in later steps.  I wish I had a memory...

-- 
You received this question notification because you are a member of
Ubuntu Server/Client Support Team, which is an answer contact for
openldap in Ubuntu.