Chapter 4 Server Instance File Reference

This chapter provides an overview of the files that are specific to an instance of Netscape Directory Server (Directory Server) -- the files stored under the serverRoot/slapd-serverID directory. Having an overview of the files and configuration information stored in each instance of Directory Server should help you understand the file changes or absence of file changes which occur in the course of directory activity. It should also help you to detect errors and intrusion by indicating what kind of changes to expect and, as a result, what changes are considered abnormal.

This chapter contains the following sections:

Overview of Directory Server Files

Directory Server files and command-line scripts are stored under this directory:

serverRoot/slapd-serverID

The only exception is the migrateInstance7 script, which is stored under this directory:

serverRoot/bin/slapd/admin/bin

Code Example 4-1 shows the contents of the serverRoot/slapd-serverID directory, where directories are marked with a / and scripts are marked with an * . See chapter 8, "Command-Line Scripts," for further information on command-line scripts.

Code Example 4-1 Contents of the serverRoot/slapd-serverID directory


./	db2ldif*	ns-inactivate.pl*
../	db2ldif.pl*	restart-slapd*
bak/	getpwenc*	restoreconfig*
bak2db*	ldif/	saveconfig*
bak2db.pl*	ldif2db*	start-slapd*
conf_bk/	ldif2db.pl*	stop-slapd*
confbak/	ldif2ldap*	suffix2instance*
config/	locks/	tmp/
db/	logs/	vlvindex*
db2bak*	monitor*
db2bak.pl*	ns-accountstatus.pl*
db2index.pl*	ns-activate.pl*

To reflect the directory structure under the serverRoot/slapd-serverID directory, this chapter is divided into the following sections:

Each section describes the file type and contents.

Backup Files

Each Directory Server instance contains the following three directories for storing backup-related files:

bak -- Contains a directory dated with the time and date of your database backup, such as 2001_02_13_174524/, which in turn holds your database backup copy.
confbak -- Is the default directory used by the restoreconfig script and the saveconfig scripts. See chapter 8, "Command-Line Scripts" for further information on command-line scripts.
conf_bk -- Contains a backup copy of the dse.ldif configuration file from the time of installation.

Configuration Files

Each Directory Server instance contains the following directory for storing configuration files:

config -- Contains the configuration files as explained in Server Configuration - Overview.

Database Files

Each Directory Server instance contains the db directory for storing all the database files. Code Example 4-2 shows a sample listing of the db directory contents.

Code Example 4-2 Contents of sample db directory


./	__db.002	__db.005	NetscapeRoot/
../	__db.003	DBVERSION	userRoot/
__db.001	__db.004	log.0000000017

db.00x files -- Used internally by the database and should not be moved, deleted, or modified in any way.
log.xxxxxxxxxx files -- Used to store the transaction logs per database.
DBVERSION -- Used for storing the version of the database.
NetscapeRoot -- Stores the o=NetscapeRoot database created by default at Typical installation.
userRoot -- Stores the user-defined suffix (user-defined databases) created at Typical installation time; for example, dc=example,dc=com.

Code Example 4-3 shows a sample listing of the NetscapeRoot directory contents.

Code Example 4-3 Contents of a sample NetscapeRoot subdirectory


./	entrydn.db4*	parentid.db4*
../	givenName.db4*	sn.db4*
DBVERSION*	id2entry.db4*	uid.db4*
aci.db4*	nsUniqueId.db4*	uniquemember.db4*
ancestorid.db4*	numsubordinates.db4*
cn.db4*	objectclass.db4*

The NetscapeRoot subdirectories contain an index_name.db4 file for every index currently defined in the database, where index_name is the name of the index. In addition to these index_name.db4 files, the Netscape and userRoot subdirectories contain the following files:

ancestorid.db4 -- Contains a list of IDs, allowing you to find the ID of the entry's ancestor.
entrydn.db4 -- Contains a list of full DNs, enabling you to find IDs.
id2entry.db4 -- Contains the actual directory database entries. All other database files can be recreated from this one, if necessary.
nsuniqueid.db4 -- Contains a list of Netscape unique IDs, enabling you to find IDs.
numsubordinates.db4-- Contains IDs that have child entries.
objectclass.db4 -- Contains a list of IDs which have a particular object class.
parentid.db4 -- Contains a list of IDs, allowing you to find the ID of the parent.

ldif Files

Each Directory Server instance contains the ldif directory for storing ldif-related files. Code Example 4-4 shows a sample listing of the ldif directory contents.

Code Example 4-4 Contents of a sample ldif directory


../	European.ldif	Example.ldif	Example-roles.ldif

The following list describes the content of each of the ldif files:

European.ldif -- Contains European character samples.
Example.ldif --Is a sample ldif file.
Example-roles.ldif -- Is a sample ldif file similar to Example.ldif, except that it uses roles and class of service instead of groups for setting access control and resource limits for Directory Administrators.

Lock Files

Each Directory Server instance contains a locks directory for storing lock-related files. Code Example 4-5 shows a sample listing of the locks directory contents.

Code Example 4-5 Contents of a sample locks directory


./	../	exports/	imports/	server/

The lock mechanisms stored under the locks subdirectories exports, imports, and server prevent multiple, simultaneous operations conflicting with each other. The lock mechanisms allow for one server instance to run at a time, with possible multiple export jobs. They also permit one ldif2db import operation at a time (not ldif2db.pl since you can run multiple ldif2db.pl operations at any time) to the exclusion of all export and slapd server operations.

If you get error messages indicating that the lock table is out of available locks ([26/Oct/2001:17:44:25 0200] - libdb: Lock table is out of available locks), set the value of the nsslapd-db-locks attribute in the cn=config,cn=ldbm database,cn=plugins,cn=config entry to twice its current number. For example, if the current number is 10000, set it to 20000. If the problem persists, double the number again. You can also monitor the current and maximum number of locks by doing a search on cn=database,cn=monitor,cn=ldbm database, cn=plugins,cn=config. An example of the command is given below.

ldapsearch -h hostname -p port -b"cn=database,cn=monitor,cn=ldbm database, cn=plugins,cn=config" -D "cn=directory manager" -w password objectclass=* | grep -- -locks: )

For more information on using LDAP utilities, see the Netscape Directory Server Administrator's Guide.

Log Files

Each Directory Server instance contains a logs directory for storing log-related files. Code Example 4-6 shows a sample listing of the logs directory contents.

Code Example 4-6 Contents of a sample logs directory


./	access.20010126-120123	audit	errors.rotationinfo
../	access.20010130-140221	audit.rotationinfo	pid
access	access.20010201-100122	errors	slapd.stats
access.20010124-180611	access.rotationinfo	errors.20010124-180607

The following list describes the content of the log-related files:

The content of the access, audit, and error log files is dependent on the log configuration.
The slapd.stats file is a memory-mapped file which cannot be read by an editor. It contains data collected by the Directory Server SNMP data collection component. This data is read by the SNMP subagent in response to SNMP attribute queries and is communicated to the SNMP master agent responsible for handling Directory Server SNMP requests.
The pid is the slapd process identifier.

Contents

Index

DocHome

© 2001 Sun Microsystems, Inc. Portions copyright 1999, 2002-2004 Netscape Communications Corporation. All rights reserved.
Read the Full Copyright and Third-Party Acknowledgments.

last updated November 26, 2004