Sponsored Content
Operating Systems Solaris Sol10 + OpenLDAP = excessive logging & full file system??!! Post 302786489 by Wraith_G2IC on Wednesday 27th of March 2013 02:20:19 PM
Old 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

file system full

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

Full File System

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

Excessive Paging&Swapping!

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

File system full?

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

Full file system?

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

difference b/w sol9 & sol10

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

Sol10 - OpenLDAP Auth

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

MySQL & OpenLDAP - file level backup

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

Sol10 booting freezes just before CDE logging in.

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
db_recover(1)						    BSD General Commands Manual 					     db_recover(1)

NAME
db_recover SYNOPSIS
db_recover [-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]] DESCRIPTION
The db_recover utility must be run after an unexpected application, Berkeley DB, or system failure to restore the database to a consistent state. All committed transactions are guaranteed to appear after db_recover has run, and all uncommitted transactions will be completely undone. The options are as follows: -c Perform catastrophic recovery instead of normal recovery. -e Retain the environment after running recovery. This option will rarely be used unless a DB_CONFIG file is present in the home directory. If a DB_CONFIG file is not present, then the regions will be created with default parameter values. -h Specify a home directory for the database environment; by default, the current working directory is used. -P Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. -t Recover to the time specified rather than to the most current possible date. The timestamp argument should be in the form [[CC]YY]MMD- Dhhmm[.SS] where each pair of letters represents the following: CC The first two digits of the year (the century). YY The second two digits of the year. If "YY" is specified, but "CC" is not, a value for "YY" between 69 and 99 results in a "YY" value of 19. Otherwise, a "YY" value of 20 is used. MM The month of the year, from 1 to 12. DD The day of the month, from 1 to 31. hh The hour of the day, from 0 to 23. mm The minute of the hour, from 0 to 59. SS The second of the minute, from 0 to 61. If the "CC" and "YY" letter pairs are not specified, the values default to the current year. If the "SS" letter pair is not specified, the value defaults to 0. -V Write the library version number to the standard output, and exit. -v Run in verbose mode. In the case of catastrophic recovery, an archival copy -- or snapshot -- of all database files must be restored along with all of the log files written since the database file snapshot was made. (If disk space is a problem, log files may be referenced by symbolic links). For further information on creating a database snapshot, see Archival Procedures. For further information on performing recovery, see Recovery Procedures. If the failure was not catastrophic, the files present on the system at the time of failure are sufficient to perform recovery. If log files are missing, db_recover will identify the missing log file(s) and fail, in which case the missing log files need to be restored and recovery performed again. The db_recover utility uses a Berkeley DB environment (as described for the -h option, the environment variable DB_HOME, or because the util- ity was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environ- ment, db_recover should always be given the chance to detach from the environment and exit gracefully. To cause db_recover to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). The db_recover utility exits 0 on success, and >0 if an error occurs. ENVIRONMENT
DB_HOME If the -h option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. SEE ALSO
db_archive(1), db_checkpoint(1), db_deadlock(1), db_dump(1), db_load(1), db_printlog(1), db_stat(1), db_upgrade(1), db_verify(1) Darwin December 3, 2003 Darwin
All times are GMT -4. The time now is 12:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy