Previous Topic: shutdown CommandNext Topic: trace disable assoc Command


trace Command

The trace command displays details of service requests, confirmations, or errors. You need to specify the level of tracing you want to use.

trace full | none | trace-event-list ;

full

Traces everything. Full tracing degrades performance, so you should use it only during testing.

none

Turns off all tracing

trace-event-list

A comma-separated list of one or more of the following trace options:

alert

Displays authentication errors.

cert

Displays certificate operations.

connect

Displays connections.

diag

Traces local DXserver operations that were refused.

dsa

Similar to the x500 trace, but also includes tracing of the module flow inside the DSA.

error

Displays error messages of high severity. Compare with trace warn.

These events that may impact on the ability of DXserver to perform a requested operation. This is the default trace level.

We recommend that the error trace option is included in the set trace command during normal operation.

ldap

Traces detailed LDAP operations. The output can become quite large when searches return a large number of entries.

limit

Traces any violation of size or time limits.

query

Displays a one-line summary containing the server request and result.

stack

Displays detailed protocol tracing. The output can become quite large.

stats

Displays statistical information for each minute the DSA is not idle.

summary

Displays a one-line summary containing the service request and result.

time

Displays the time taken for successful operations.

To send this output to a separate file, use the set time-log command.

update

Displays update operations-add, delete, modify, and rename.

warn

Displays error messages of moderate severity. Compare with trace error.

Warn messages usually represent a user error, rather than a problem with DXserver.

x500

Displays the full details of the service request, confirmation, or error. This traces DAP, DSP, and LDAP operations. The output can become quite large when searches return a large number of entries.

More information:

Prevent Multiwrite Queues Being Lost When the DSA Stops

Change the Maximum Queue Size