[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: openldap logs

Those are the SleepyCat database transaction logfiles. See the documentation on oracle.com for details. The db_* tools make use of them.

As an aside, the fact that they're in the same directory is sub-optimal unless you're backed by some fancy storage array. They should ideally be on a separate spindle from the data files for performance.

On Wed, 9 May 2007, Marcum, Bob wrote:

There is also a "log.xxxxxxxxxx" created in the directory with all of
the other directory files, in each instance of a database directory.
How does one read that data file?  Is there a slap utility to read that
file?  Otherwise, of what use is it?  And what kinds of information can
one get from that log?

-----Original Message-----
From: openldap-software-bounces+bob.marcum=telecheck.com@OpenLDAP.org
On Behalf Of Hallvard B Furuseth
Sent: Wednesday, May 09, 2007 10:04 AM
To: Raffaele Viola
Cc: openldap-software@openldap.org
Subject: Re: openldap logs

Raffaele Viola writes:
how can I activate the openldap logs and where I can see the logs?

Tell slapd to log to syslog with e.g. "loglevel 256" in slapd.conf, see man 'slapd.conf'. Restart slapd.

Tell syslog to output the slapd logs: How this is done varies, but
typically you append something like
local4.*   /var/log/openldap.log
to /etc/syslog.conf, and kill -HUP <the syslog pid> to tell syslogd to
re-read the config file.  (slapd uses the local4 syslog level by

On some systems you can put '-' in front of the filename to tell syslogd
to write log lines in batches instead of one by one.  This can remove a
significant I/O bottleneck if you have a lot of traffic.  See man
syslogd or man syslog.conf.

The information in this message may be proprietary and/or
confidential, and protected from disclosure.  If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your