[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: problem with slapadd in migrating LDAP servers
--On Monday, February 01, 2016 9:13 PM +0000 k j <kj37075@yahoo.com> wrote:
# slapadd -l /tmp/nis.ldif.ldapDump
56afc9ed The first database does not allow slapadd; using the first
available one (2)
56afc9ed bdb_db_open: warning - no DB_CONFIG file found in directory
/var/lib/ldap: (2).
Expect poor performance for suffix "dc=my-domain,dc=com".
slapadd: line 1: database #2 (dc=my-domain,dc=com) not configured to hold
"ou=Hosts,dc=company,dc=com"; no database configured for that naming
context
That seems pretty clear. You're trying to import
"ou=hosts,dc=company,dc=com" into a database that's configured to hold data
for "dc=my-domain,dc=com". Clearly those are not even remotely the same.
It also seems like you're purely importing host data, which may be
problematic if this is an empty database.
Your ldapadd is also clearly invalid, because you're trying to do it as
"dc=mydomain,dc=com" where the DB is clearly configured as
"dc=my-domain,dc=com". Again, clearly not the same thing at all.
--Quanah
--
Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
A division of Synacor, Inc