[Date Prev][Date Next]
Re: Delete everything in a LDAP Server
I would suggest shutting down the server, deleting the db files
yourself and then running slapadd.
You'll have to shut down the 2nd OpenLDAP server anyways to use
We do something similar where in we get a daily batch of data that
needs to be in OpenLDAP and we erase the previous days data.
Quoting Kevin Fries <firstname.lastname@example.org>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> I was going to try to use syncrepl to create a mirror of my LDAP
> on a second machine. I figured that it not only backs up my
> user data, but also gives me a local cache that I can use to
> authenticate local services against so that a failure of one
> does not bring down the other.
> However, there seems to be too many problems with it right now to
> seriously considered in a production environment. So, I am on to
> B (C?). What I would like to do until that feature is fully
> is use create a script that does a slapcat on the main server,
> store that file in a central location. I would then like to come
> along with the second server and completely dump, then reload the
> from the backup using slapadd.
> I tried to do a ldapdelete on the top level object, but it just
> me "Unwilling to perform" and gave no further details. The exact
> error is:
> # ldapdelete -x -D "cn=admin,dc=example,dc=com" -w netge3k -h
> 127.0.0.1 "dc=example,dc=com"
> Delete Result: Server is unwilling to perform (53)
> Additional info: shadow context; no update referral
> any hints on what I am doing wrong? I have my suspicions, but
> think I
> will hear what you guys have to say first without polluting your
> thinking with my screwup.
> Kevin Fries
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird -
> -----END PGP SIGNATURE-----