[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
export directory in LDIF format
- To: OpenLDAP Technical Discussion list <openldap-technical@openldap.org>
- Subject: export directory in LDIF format
- From: Jerry <jerry@seibercom.net>
- Date: Mon, 10 Nov 2014 07:00:58 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seibercom.net; s=google; h=date:from:to:subject:message-id:reply-to:organization:mime-version :content-type:content-transfer-encoding; bh=z+SLMmxLh/E6TiMj4F8WYiup0s1b0suBMwNS0ksk2/M=; b=jI0yZLU40Sf4ML4EioEPRS63OIVjEJrKXBVWeIlPbTK6KrEqLZPGPWsxfvoaANgudC Ki86hyTvGislLW2y+BtIa7byvBeSqmgJkSs1MvgrYFwxPXPyTrscUu4+TY+Ndqjvnf0P Qh2LfdIptGdHx5g9vaShNPgI+wg6ajgsQTL9Y=
- Organization: seibercom NET
I have a strange problem exporting my directory into LDIF format. I am using
the "mdb" format with openldap.
/usr/local/sbin/slapcat -l MyDomain.net.ldif -b "dc=MyDomain,dc=net"
If I run this command after starting "slapd", it works fine. However, I have
this configured to run from a CRON job at midnight. It fails with this
message:
5460a615 mdb_db_open: database "dc=MyDomain,dc=net" cannot be opened: No such
file or directory (2). Restore from backup! 5460a615 backend_startup_one
(type=mdb, suffix="dc=MyDomain,dc=net"): bi_db_open failed! (2) slap_startup
failed
This also occurs from the command line if the database has not been accessed
for several hours, usually on a weekend. Restarting "slapd" immediately
corrects the problem.
I have checked and "slapd" is running when the failure occurs. I tried
accessing the database and then using the backup command; however, the
failure still continues. That is assuming that it failed to begin with
obviously.
Is there some sort of a "sleep" mode or something like that, that I am not
aware of, or some really hard to debug "bug" somewhere?
--
Jerry