Most AppManager components include registry keys for fine-tuning trace logging. By default, most components are set to do little or no logging for performance reasons. If you are troubleshooting your AppManager environment, however, it may be useful to change the tracing level to provide more detailed information in log files.
NOTE:NetIQ Corporation recommends you use the Diagnostics utility to set the tracing level rather than edit registry keys directly because using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. In general, you should only edit the registry directly if instructed to do so by NetIQ Technical Support or if you have a thorough understanding of the key values and the implications of making changes. NetIQ cannot guarantee that problems resulting from the incorrect use of the Registry Editor can be resolved.
All AppManager log files for the components installed on a computer are stored in the location defined in the HKEY_LOCAL_MACHINE registry under \Software\NetIQ\Generic\Tracing. For example, the default path is typically:
TraceLogPath: c:\program files\netiq\Temp\NetIQ_Debug
For information about the specific registry keys that enable or configure logging for each component, see Registry Keys. The following table provides a summary of the information recorded in the log files and how you can use this information to troubleshoot your AppManager environment.
|
Log |
Information Recorded |
|---|---|
|
ccmtrace.log |
If you enable TraceCCM, the AppManager Client Communication Manager (NetIQccm) records information about its activity in the ccmtrace.log file. The information recorded in this file includes the connection status for communication with the management server, and the processing status for events and data stored in the local repository. |
|
mctrace.log |
If you enable TraceMC, the AppManager Client Resource Monitor (NetIQmc) records information about its activity in the mctrace.log file. The information recorded in this file includes the status of polling threads, job requests, and job execution. If you also enable Knowledge Script tracing with TraceKS, this log also includes line-by-line trace entries for each job running on the agent. This allows you to step through the Knowledge Script as it is executed to locate the point of failure. NOTE:Knowledge Script tracing creates an ASCII copy of the compiled Knowledge Script with debugging line numbers in the TraceLogPath\mc subdirectory. A separate file is created for each job and action executed on the agent and the name of each file includes the JobID and the SiteID. |
|
mo.log |
If you enable tracing for any managed object, the mo.log records information about monitoring activity for that managed object. The information recorded includes all function calls made from the managed object during job execution. By default all managed object tracing flags are set to 0x10, which provides a minimal level of tracing. You can log additional detail by increasing the value for the relevant TraceMOcomponent registry key. To enable full tracing for a desired MO, set the appropriate registry value to 0xFF. |
|
Ckcomponent.log |
Pre-installation information for each managed object selected during a pre-installation check is recorded in a separate log file. For example, if you run the pre-installation check for Exchange 2000, the setup program records information about the checks performed in the CkExch2.log. These log files can help you determine why a particular managed object cannot be installed or discovered on a computer. |
|
loc.log |
The loc.log traces internal pipe communication between the Client Resource Monitor and Client Communication Manager services. |
|
Nqioc_err.log |
The Nqioc_err.log records information about errors generated by the IO Completion port on the agent. The IO Completion port is used to verify the delivery of information to the management server. If errors are generated on this port, it may suggest delivery failures. |
|
ms.log |
The AppManager Management Service (NetIQms) records information about all of its activity in the ms.log. For example, the service writes information in the ms.log when it delivers jobs to agents, receives events and data, or detects changes to job or machine status. |
|
msaction.log |
If you enable Action Log tracing, the AppManager Management Service (NetIQms) records detailed information about management server or proxy action processing errors. |
|
msqdb.log |
If you enable QDB Log tracing, the AppManager Management Service (NetIQms) records detailed information about errors encountered when the management server connects to the repository. |
|
msrplib.log |
The msrplib.log records information about activity between the AppManager Management Service (NetIQms) and the QDB. |
|
rplib.log |
The rplib.log records information about the connection and activity between the Operator Console and the QDB. This file logs any ODBC errors encountered in the connection between the Operator Console and the QDB. The file also includes information about all requests to fetch, update, refresh, or delete information in the QDB. |
|
KSCheckin.log |
The kscheckin.log records information about all attempts to check Knowledge Scripts into the repository, including attempts to check in scripts from a local Operator Console, using the Kscheckin.exe utility, or through an installation or upgrade of the repository. |
|
QDBInstall.log |
The QDBInstall.log stores a complete record of the repository installation process. |
|
QDBUpgradenn.log |
The QDBUpgradenn.log stores a complete record of the repository upgrade process. The log filename indicates the version of AppManager to which you upgraded. For example, if you are upgrading to AppManager 6.7, the log filename is QDBUpgrade67.log. |
|
KSCustomnn.log |
The KSCustomnn.log stores information about Knowledge Scripts that have had properties customized and records whether the customized version of the Knowledge Script has been successfully checked into the QDB. The log filename indicates the version of AppManager to which you upgraded. For example, if you are upgrading to AppManager 6.7, the log filename is KSCustom67.log. |
|
appmgr.log |
The appmgr.log records debugging information for an AppManager agent installation. Unlike other log files, this file is located in the Windows system folder. For example: %SYSTEMROOT%\appmgr.log |
|
maint.log |
The maint.log records information about any patches or hot-fixes installed for any AppManager component on a local computer. |
|
msadapt.log |
The msadapt.log records information about all activity processed by an AppManager Connector. |