03-27-2013
Quote:
Originally Posted by
jlliagre
What are these 50m files created every minute (do you really mean 50 million files created every minute or 50 MB of new logs every minute ?)
In any case, why don't you post a sample of these logs ?
Are you doing snapshots of the file system containing the logs ?
Thanks for the reply.
These are log files created automatically for the purpose of auto-recovering the LDAP from a failure. In most systems I have, there are just 2 - 6 files (50mb each) in the logs dir. These files are 50mb due to the "Transaction Log Settings" in the DB_CONFIG. Increasing / decreasing the configured size has no affect on the problem. These files normally "track" changes made to LDAP DB via the Berkeley DB (BDB). The problem is, these files are not human readable, and it is on an isolated system not connected to the internet (IE: we are not allowed to post files). These log files are "usually" automatically cleaned up by a statement in the conf file:
set_flags DB_LOG_AUTOREMOVE
This setting works on every other system we have, with the exception of this T4-1.
No, there are no snapshots being done. It is on a raidz2 zfs file-system, but that shouldn't matter..
It has been suggested by some folks @ OpenLDAP that the older version of BDB -v4.7 is the issue. I have to claim partial ignorance to that statement since we don't use BDB for anything, but to support OpenLDAP.
9 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
When I try to log in as root I get the following message
realloccg /: file system full sendmail :NO Queue:low on space (have 0,SMTP-DAEMON needs 101 in /var/spool/mqueue) What should I do? (1 Reply)
Discussion started by: hopeless
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
There was a background process running on a Solaris 2.8 machine, and appeared to have filled all available disk-space. I done a killall, and upon re-booting found that the file system had filled up, and will not boot as normal as a result. For example, I'm getting
/usr/adm/messages: No... (8 Replies)
Discussion started by: Breen
8 Replies
3. UNIX for Advanced & Expert Users
Hi all!
Working on Oracle v8i/9i on Unix Sun Solaris v8.0.
I am experiencing excessive paging & Swapping.Would like to know the cause.
I guess:could be due to inappropriate setting of Unix Kernel Parameters...
Please correct me if I am wrong!
Thanks&Regards,
Amit. (5 Replies)
Discussion started by: Amitstora
5 Replies
4. Solaris
Hi, I just started working with UNIX on an old semi-fossilized Sun workstation which I use to process LOTS of images,however, I just started to get an error message that the file system is full and then my shell tool or/and text editor freeze up. Help? (8 Replies)
Discussion started by: Bend
8 Replies
5. Solaris
I read the sticky and thought of a script I use on a regular basis. Since unless you patch/upgrade the df command on solaris you have a very tought time teling how full the system truly is.
Output looks like
$ biggest.sh /tmp
Filesystem kbytes used avail capacity Mounted... (0 Replies)
Discussion started by: meyerder
0 Replies
6. Solaris
what is the difference b/w sol9 and sol10 booting procedure?? Recently faced this question with HP...
Thiru (2 Replies)
Discussion started by: tirupathiraju_t
2 Replies
7. Solaris
Hi,
im new to Solaris (10) and need some help please.
Situation: Actually is there a Linux (SLES11) OpenLDAP-Server and authentification of Linux-Maschines works pretty sweet. Now i want to put the SOL10 (Sparc) boxes in....
Problem: User Authentification via OpenLDAP on Sol10 doesn´t work... (3 Replies)
Discussion started by: Panzerkampfwagn
3 Replies
8. UNIX and Linux Applications
Hi All,
The MySQL & OpenLDAP database on my Debian are very lightly updated.
Usually I tar everything on / including the databases.
The restore works OK on another machine.
I want to know whether its safe to do file level backup of databases like this ?
Do the MySQL & OpenLDAP databases... (0 Replies)
Discussion started by: coolatt
0 Replies
9. Solaris
Hello everyone,
There is a problem with hardware installation.
Probably someone faced with something similar.
Sun Blade 1500 with OS Solaris 10 installed, CDE workspace.
I can not add new graphics accelerator instead of older one.
I think I installed all needed packages related the new card,... (2 Replies)
Discussion started by: wolfgang
2 Replies
LEARN ABOUT OPENDARWIN
slapd-bdb
SLAPD-BDB(5) File Formats Manual SLAPD-BDB(5)
NAME
slapd-bdb - BDB backend to slapd
SYNOPSIS
/etc/openldap/slapd.conf
DESCRIPTION
The BDB backend to slapd(8) is the recommended backend for a normal slapd database. It uses the Sleepycat BerkelyDB package to store data.
It makes extensive use of indexing and caching to speed data access.
CONFIGURATION
These slapd.conf options apply to the BDB backend database. That is, they must follow a "database bdb" line and come before any subsequent
"backend" or "database" lines. Other database options are described in the slapd.conf(5) manual page.
cachesize <integer>
Specify the size in entries of the in-memory cache maintained by the BDB backend database instance. The default is 1000 entries.
checkpoint <kbyte> <min>
Specify the frequency for checkpointing the database transaction log. A checkpoint operation flushes the database buffers to disk
and writes a checkpoint record in the log. The checkpoint will occur if either <kbyte> data has been written or <min> minutes have
passed since the last checkpoint. Both arguments default to zero, in which case they are ignored. See the Berkeley DB reference
guide for more details.
dbnosync
Specify that on-disk database contents should not be immediately synchronized with in memory changes. Enabling this option may
improve performance at the expense of data security.
directory <directory>
Specify the directory where the BDB files containing this database and associated indexes live. A separate directory must be speci-
fied for each database. The default is /var/db/openldap/openldap-data.
dirtyread
Allow reads of modified but not yet committed data. Usually transactions are isolated to prevent other operations from accessing
uncommitted data. This option may improve performance, but may also return inconsistent results if the data comes from a transac-
tion that is later aborted. In this case, the modified data is discarded and a subsequent search will return a different result.
index {<attrlist>|default} [pres,eq,approx,sub,<special>]
Specify the indexes to maintain for the given attribute (or list of attributes). Some attributes only support a subset of indexes.
If only an <attr> is given, the indices specified for default are maintained. Note that setting a default does not imply that all
attributes will be indexed.
A number of special index parameters may be specified. The index type sub can be decomposed into subinitial, subany, and subfinal
indices. The special type nolang may be specified to disallow use of this index by language subtypes. The special type nosubtypes
may be specified to disallow use of this index by named subtypes. Note: changing index settings requires rebuilding indices, see
slapindex(8).
lockdetect {oldest|youngest|fewest|random|default}
Specify which transaction to abort when a deadlock is detected. The default is the same as random.
mode <integer>
Specify the file protection mode that newly created database index files should have. The default is 0600.
searchstack <depth>
Specify the depth of the stack used for search filter evaluation. Search filters are evaluated on a stack to accomodate nested AND
/ OR clauses. An individual stack is assigned to each server thread. The depth of the stack determines how complex a filter can be
evaluated without requiring any additional memory allocation. Filters that are nested deeper than the search stack depth will cause
a separate stack to be allocated for that particular search operation. These allocations can have a major negative impact on server
performance, but specifying too much stack will also consume a great deal of memory. Each search stack uses 512K bytes per level.
The default stack depth is 16, thus 8MB per thread is used.
FILES
/etc/openldap/slapd.conf
default slapd configuration file
SEE ALSO
slapd.conf(5), slapd(8), slapadd(8), slapcat(8), slapindex(8).
OpenLDAP 2.1.X RELEASEDATE SLAPD-BDB(5)