Red-hat 8.1 Manual do Utilizador descarregar pdf (Página 168)

A timestamp, such as [05/Jan/2009:02:27:22 -0500], although the format varies depending

on the platform. The ending four digits, -0500, indicate the time difference in relation to GMT.

The plug-in being called, for internal operations.

Functions called by the plug-in, for internal operations.

Messages returned by the plug-in or operation, which may include LDAP error codes, connection

information, or entry information.

Frequently, the messages for an operation appear on multiple lines of the log, but these are not

identified with a connection number or operation number.

Example 5.3, “Error Log Excerpt” shows excerpts from an error log at the default logging level, which

includes some task information, critical errors, and server startup messages.

Exa mple 5.3. Error Log Excerpt

[05/Jan/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/Jan/2009:17:52:04 -0500] schem areload - Schema reload task starts (schema

dir: default) ...

[06/Jan/2009:17:52:04 -0500] schem areload - Schema validation passed.

[06/Jan/2009:17:52:04 -0500] schem areload - Schema reload task finished.

[07/Jan/2009:15:54:08 -0500] - libdb: write: 0xb75646e5, 508: No space left on

device

[07/Jan/2009:15:54:08 -0500] - libdb: txn_checkpoint: log failed at LSN [22

7649039] No space left on device

[07/Jan/2009:15:54:08 -0500] - Serious Error- - - Failed to checkpoint database,

err=28 (No space left on device)

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

[07/Jan/2009:15:54:08 -0500] - Attempting to shut down gracefully.

[07/Jan/2009:15:54:08 -0500] - slapd shutting down - signaling operation threads

[07/Jan/2009:15:54:08 -0500] - slapd shutting down - closing down internal

subsystems and plugins

[07/Jan/2009:15:54:11 -0500] - Waiting for 3 database threads to stop

[07/Jan/2009:15:54:11 -0500] - All database threads now stopped

[07/Jan/2009:15:54:12 -0500] - slapd stopped.

Red Hat-Directory/8.1.4 B2008.310.1012

server.example.com :389 (/etc/dirsrv/slapd-example)

[07/Jan/2009:22:18:41 -0500] - Red Hat-Directory/8.1.4 B2008.310.1012 starting up

[07/Jan/2009:22:18:44 -0500] mem ory allocator - cannot calloc 0 elem ents;

trying to allocate 0 or a negative number of elem ents is not portable and

gives different results on different platforms.

[07/Jan/2009:22:18:44 -0500] - slapd started. Listening on All Interfaces port

389 for LDAP requests

5.2.3. Error Log Cont ent 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. T his 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 - agm t="name" (consumer_host:consumer_port):

current_task

For example:

[09/Jan/2009:13:44:48 -0500] NSMMReplicationPlugin - agmt="cn=example2"

(alt:13864): {replicageneration} 4949df6e000000010000

{replicageneration} means that the new information is being sent, and

4 94 9df6e000000010000 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.

168 Chapter 5. Log File Reference

1 2 ... 163 164 165 166 167 168 169 170 171 172 173 ... 291 292

Comentários a estes Manuais

Sem comentários

Red-hat 8.1 Manual do Utilizador Página 168

Comentários a estes Manuais