Red Hat 8.1 - Manual (Page 171)

Plug-in logging records every the name of the plugin and all of the functions called by the plugin. This
has a simple format:
[timestamp] Plugin_name - message
[timestamp] - function - message
The information returned can be hundreds of lines long as every step is processed. The precise
information recorded depends on the plug-in itself. For example, the ACL Plug-in includes a connection
and operation number, as shown in
Example 5.5, “Example ACL Plug-in Error Log Entry with Plug-in
Logging” .
Example 5.5. Example ACL Plug-in Error Log Entry with Plug-in Logging
[09/Jan/2009:13:15:16 -0500] NSACLPlugin - conn=24826500108779577 op=10 (main):
Allow search on entry(cn=replication,cn=config): root user
[09/Jan/2009:13:15:16 -0500] - <= slapi_vattr_filter_test 0
[09/Jan/2009:13:15:16 -0500] NSACLPlugin - Root access (read) allowed on
entry(cn=replication,cn=config)
[09/Jan/2009:13:15:16 -0500] NSACLPlugin - Root access (read) allowed on
entry(cn=replication,cn=config)
[09/Jan/2009:13:15:16 -0500] NSACLPlugin - Root access (read) allowed on
entry(cn=replication,cn=config)
[09/Jan/2009:13:15:16 -0500] - slapi_filter_free type 0x87
[09/Jan/2009:13:15:16 -0500] - => get_filter_internal
[09/Jan/2009:13:15:16 -0500] - EQUALITY
[09/Jan/2009:13:15:16 -0500] - <= get_filter_internal 0
[09/Jan/2009:13:15:16 -0500] get_filter - before optimize:
[09/Jan/2009:13:15:16 -0500] get_filter - after optimize:
[09/Jan/2009:13:15:16 -0500] index_subsys_assign_filter_decoders - before:
(objectClass=nsBackendInstance)
[09/Jan/2009:13:15:16 -0500] index_subsys_assign_filter_decoders - after:
(objectClass=nsBackendInstance)
[09/Jan/2009:13:15:16 -0500] - => slapi_vattr_filter_test_ext
[09/Jan/2009:13:15:16 -0500] - => test_substring_filter
[09/Jan/2009:13:15:16 -0500] - EQUALITY
NOTE
Example 5.5, “Example ACL Plug-in Error Log Entry with Plug-in Logging” shows both plug-in
logging and search filter processing (log level 32).
Many other kinds of logging have similar output to the plug-in logging level, only for different kinds of
internal operations. Heavy trace output (4), access control list processing (128), schema parsing
(2048), and housekeeping (4096) all record the functions called by the different operations being
performed. In this case, the difference is not in the format of what is being recorded, but what operations
it is being recorded for.
The configuration file processing goes through any .conf file, printing every line, whenever the server
starts up. This can be used to debug any problems with files outside of the server's normal
configuration. By default, only slapd-collations.conf file, which contains configurations for
international language sets, is available.
Example 5.6. Config File Processing Log Entry
[09/Jan/2009:16:08:18 -0500] - reading config file /etc/dirsrv/slapd-
server/slapd-collations.conf
[09/Jan/2009:16:08:18 -0500] - line 46: collation "" "" "" 1 3
2.16.840.1.113730.3.3.2.0.1 default
[09/Jan/2009:16:08:18 -0500] - line 57: collation en "" "" 1 3
2.16.840.1.113730.3.3.2.11.1 en en-US
[09/Jan/2009:16:08:18 -0500] - line 58: collation en CA "" 1 3
2.16.840.1.113730.3.3.2.12.1 en-CA
[09/Jan/2009:16:08:18 -0500] - line 59: collation en GB "" 1 3
2.16.840.1.113730.3.3.2.13.1 en-GB
There are two levels of ACI logging, one for debug information and one for summary. Both of these ACI
logging levels records some extra information that is not included with other types of plug-ins or error
logging, including
connection and operation information. Show the name of the plug-in, the bind DN of the
user, the operation performed or attempted, and the ACI which was applied. The debug level shows the
series of functions called in the course of the bind and any other operations, as well.
Red Hat Directory Server 8.1 Configuration and Command Reference
171