Plug-in logging records every the name of the plugin and all 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/Aug/2009:13:15:16 -0500] NSACLPlugin - conn=24826500108779577 op=10 (main): Allow search on entry(cn=replication,cn=config): root user [09/Aug/2009:13:15:16 -0500] - <= slapi_vattr_filter_test 0 [09/Aug/2009:13:15:16 -0500] NSACLPlugin - Root access (read) allowed on entry(cn=replication,cn=config)
[09/Aug/2009:13:15:16 -0500] NSACLPlugin - Root access (read) allowed on entry(cn=replication,cn=config)
[09/Aug/2009:13:15:16 -0500] NSACLPlugin - Root access (read) allowed on entry(cn=replication,cn=config)
[09/Aug/2009:13:15:16 -0500] - slapi_filter_free type 0x87 [09/Aug/2009:13:15:16 -0500] - => get_filter_internal [09/Aug/2009:13:15:16 -0500] - EQUALITY [09/Aug/2009:13:15:16 -0500] - <= get_filter_internal 0 [09/Aug/2009:13:15:16 -0500] get_filter - before optimize: [09/Aug/2009:13:15:16 -0500] get_filter - after optimize: [09/Aug/2009:13:15:16 -0500] index_subsys_assign_filter_decoders - be\ fore: (objectClass=nsBackendInstance)
[09/Aug/2009:13:15:16 -0500] index_subsys_assign_filter_decoders - after: (objectClass=nsBackendInstance)
[09/Aug/2009:13:15:16 -0500] - => slapi_vattr_filter_test_ext [09/Aug/2009:13:15:16 -0500] - => test_substring_filter
[09/Aug/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.conffile, which contains configurations for international language sets, is available.
