Example 5-3 Error log excerpt

[05/Aug/2009:02:27:22 -0500] slapi_ldap_bind - Error: could not send bind

request for id [cn=repl manager,cn=config] mech [SIMPLE]: error 91 (Can't connect to the LDAP server)

[06/Aug/2009:17:52:04 -0500] schemareload - Schema reload task starts (schema dir: default) ...

[06/Aug/2009:17:52:04 -0500] schemareload - Schema validation passed. [06/Aug/2009:17:52:04 -0500] schemareload - Schema reload task finished. [07/Aug/2009:15:54:08 -0500] - libdb: write: 0xb75646e5, 508: No space left on device

[07/Aug/2009:15:54:08 -0500] - libdb: txn_checkpoint: log failed at LSN [22 7649039] No space left on device

[07/Aug/2009:15:54:08 -0500] - Serious Error- - - Failed to checkpoint database, err=28 (No space left on device)

[07/Aug/2009:15:54:08 -0500] - *** DISK FULL ***

[07/Aug/2009:15:54:08 -0500] - Attempting to shut down gracefully. [07/Aug/2009:15:54:08 -0500] - slapd shutting down - signaling operation threads

[07/Aug/2009:15:54:08 -0500] - slapd shutting down - closing down intern\ al subsystems and plugins

[07/Aug/2009:15:54:11 -0500] - Waiting for 3 database threads to stop [07/Aug/2009:15:54:11 -0500] - All database threads now stopped [07/Aug/2009:15:54:12 -0500] - slapd stopped.

HP-UX Directory/8.1.0 B2009.181.2311 server.example.com:389 (/etc/opt/dirsrv/slapd-example)

[07/Aug/2009:22:18:41 -0500] - HP-UX Directory/8.1.0 B2009.181.2311 starting up

[07/Aug/2009:22:18:44 -0500] memory allocator - cannot calloc 0 elements; trying to allocate 0 or a negative number of elements is not portable and gives different results on different platforms.

[07/Aug/2009:22:18:44 -0500] - slapd started. Listening on All Inter\ faces port 389 for LDAP requests

5.2.3 Error log content for other log levels

The different log levels return not only different levels of detail, but also information about different types of server operations. Some of these are summarized here, but there are many more combinations of logging levels possible.

Replication logging is one of the most important diagnostic levels to implement. This logging level records all operations related to replication and Windows synchronization, including processing modifications on a supplier and writing them to the changelog, sending updates, and changing replication agreements.

Whenever a replication update is prepared or sent, the error log identifies the replication or synchronization agreement being specified, the consumer host and port, and the current replication task.

[timestamp] NSMMReplicationPlugin - agmt="name" (consumer_host:consumer_port): current_task

For example:

[09/Aug/2009:13:44:48 -0500] NSMMReplicationPlugin - agmt="cn=example2" (host2.example.com:389): {replicageneration} 4949df6e000000010000

{replicageneration} means that the new information is being sent, and 4949df6e000000010000 is the change sequence number of the entry being replicated.

Example 5-4 “Replication error log entry” shows the complete process of sending a single entry to a consumer, from adding the entry to the changelog to releasing the consumer after replication is complete.

5.2 Error log reference 183