What information is found in the AppManager component log files? (NETIQKB73010)

  • 7773010
  • 03-Jun-2011
  • 25-Jan-2012

Environment

NetIQ AppManager 7.0.x
NetIQ AppManager 8.x

Situation

How do I configure and use AppManager log files?
What information is found in the AppManager component log files?

Resolution

Overview/Scope

This discussion will cover the basic logs for the AppManager components.  Logs specific to particular monitored applications (Oracle, notes, etc.) will not be covered here.  Please refer to the Configuration notes or other documentation related to the specific Management Object.

AppManager Log configuration

First we will discuss the general settings for the logging functions of AppManager, including where the logs are located, how to make sure the logs are capturing the correct information, and how the logs behave with respect to rolling-over or discarding old information.

Log locations

All AppManager logs are stored in a location defined in the following value in the registry:

HKEY_LOCAL_MACHINE\Software\NetIQ\Generic\Tracing:

TraceLogPath: c:\program files\netiq\Temp\NetIQ_Debug

 

Log sizes

The default maximum log size for the AppManager logs is defined in the following value in the registry:

HKEY_LOCAL_MACHINE\Software\NetIQ\Generic\Tracing:

TraceLogMaxSize: 0x200000

Logging levels

Client Resource Monitor (NetIQmc) Service

The AppManager agent can be configured to provide more detail in the mctrace.log and the mo.log when desired.  In addition, knowledge script tracing can be enabled, to allow for line-by-line debugging of a scripts execution on the agent.

HKEY_Local_Machine\Software\NetIQ\AppManager\4.0\NetIQmc\Tracing

TraceKS

Set this registry value to 1 to enable knowledge script tracing.  This feature will create an ASCII copy of the compiled KS complete with line numbers in the %TraceLogPath%\mc subdirectory.  A separate file will be created for each job and action executed on the agent.  The name of each file will include the related JobID and the SiteID.This feature will also provide additional logging in the mctrace.log, displaying each line from each job as it executes on the agent.  This allows you to step through the KS as it was executed, in order to locate the point of failure.

TraceMC

Set this value to 1 (default) to enable the mctrace.log.

Client Communication Manager (NetIQccm) service 

HKEY_Local_Machine\Software\NetIQ\AppManager\4.0\NetIQmc\Tracing

TraceCCM

Set this value to 1 (default) to enable logging to the ccmtrace.log.

Management Server (NetIQms) Service

The Management Server has several different types of logging that can be enabled, depending on the type of problem being analyzed. 

Action Log

Set to 1 to enable enhanced details on action processing errors by the management server.  Errors are written to msaction.log.

QDB log

Set to 1 to enable enhanced details on repository connection errors from the management server.  Errors are written to msqdb.log.

RPC Log

Set to 1 to enable enhanced details on RPC communication between the management server and the agents

TraceCache

Set to 1 to enable enhanced details on IOC cache processing by the management server

TraceData

Set to 1 to enable enhanced details on data point processing by the management server. 

TraceEvent

Set to 1 to enable enhanced details on event processing by the management server

TraceJob

Set to 1 to enable enhanced details on job status processing by the management server

TraceRPC

Set to 1 to enable enhanced details on RPC on the management server

Management Objects (MO)

By default all Management Object tracing (which is directed to the mo.log) flags are set to 0x10, which provides a minimal level of tracing. To enable full tracing for a desired MO, set the appropriate registry value to 0xFF.

TraceMOactiveds

TraceMOcim

TraceMOexch

TraceMOiis

TraceMOmscs

TraceMOmsmq

TraceMOmts

TraceMOnote

TraceMOnt

TraceMOproxy

TraceMOsms

TraceMOsnmp

TraceMOsql

TraceMOwbem

TraceMOweb

TraceMOwmi

Reading AppManager Logs

Each of the AppManager components has one or more logs which capture information regarding that component?s operation.  Here we will discuss which logs contain which information, and how to interpret some of the information contained within these logs.

 

Agent Logs

Mctrace.log

Displays all activity within the NetIQmc process, including the reception, creation, compilation, and execution of jobs.  If KS Tracing is enabled, this log will also include line-by-line traces of each job running on the agent.

Ccmtrace.log

Displays all activity within the NetIQccm process.  Primarily displays connection status with the Management server, and processing of events and data points within the local repository.

Mo.log

Displays selected activity of the installed Management Objects on the agent machines (NT, Exchange, SQL, etc.).  This includes all function calls made from each Management Object during job execution.  Additional detail within the log can be obtained by increasing the relevant TraceMO flag.

Ck*.log

Displays preinstallation information for each managed object.  Helps to determine why a particular object cannot be installed or discovered.

  • CkExch2k.log
  • Cksql.log
  • CkBlackberry.log
  • Ckorcl.log
  • ckNetworkDevice.log

Discovery_ReportAgent.log

Provides details on the Discovery process for the Report Agent.

Ioc.log

Traces internal pipe communication between the NetIQ Client Resource Monitor and NetIQ Client Communication Manager services.

Nqioc_err.log

Displays error information generated by the IO Completion port on the agent, which verifies delivery of information back to the Management Server.

KS traces

ASCII copy of the compiled KS complete with line numbers in the %TraceLogPath%\mc subdirectory.  A separate file will be created for each job and action executed on the agent.  The name of each file will include the related JobID and the SiteID.

Management Server logs

Ms.log

Displays all activity within the NetIQms process, including the delivery of jobs to agents, reception of events and data, and Job and machine status changes.

Rplib.log

Displays errors pertaining to the connection and activity between the NetIQms process and the repository database.  Displays any ODBC errors encountered.

Msqdb.log

Displays errors encountered by the NetIQms process when connecting to the repository.

Msaction.log

Displays details on MS or proxy actions. 

Repository Logs

SQL Server error logs

KSCheckin.log

Displays a record of all attempts to check in knowledge scripts to the repository, either from the local operator console, the KSCHECKIN.EXE utility, or installation/upgrade.

QDBInstall.log

Displays a complete record of the repository installation process.

QDBUpgrade.log

Displays a complete record of the repository upgrade process.

Operator Console Logs

Rplib.log

Displays errors pertaining to the connection and activity between the Operator Console and the repository database, including all fetch requests, updates, refreshes, etc.  Displays any ODBC errors encountered.

KSCheckin.log

Displays a record of all attempts to check in knowledge scripts to the repository, either from the local operator console or the KSCHECKIN.EXE utility.

AMChartCon.log

Displays details on the AppManager Chart Console 

Connector logs

Msadapt.log

Adapter-specific logs, such as the following:

  • msadpt_ars.log -- Remedy
  • amnc.log -- Netcool

Displays all activity processed through the AppManager Connectors.

Installation & Upgrade Logs

QDBInstall.log

Displays a complete record of the repository installation process.

QDBUpgrade.log

Displays a complete record of the repository upgrade process.

KSCustom.LOG

Lists Knowledge Scripts that have had properties customized and records whether the customized version of the Knowledge Script has been successfully checked into the AppManager repository:

KS*DIFF.LOG

Various log files created during Repository upgrade process to report code or property differences between existing Knowledge scripts and new versions.

appmgr.log

How do I debug an AppManager agent installation related problem? 

For AppManager version 6.x and lower, the following method can be used:

On the machine that the agent is to be installed:

    1. Create a text file named AppManagerDebugInstall.log 
    2. Open the file just created and enter the following text:  AppManagerDebugInstall 
    3. Save the file in the WINNT directory 
    4. Re-run the AppManager installation 
    5. After the install has completed or failed, please review the following file:  \WINNT\appmgr.log

For AppManager version 7 and higher, an installation log file is generated for each component and module installed on a machine.  these files follow a naming structure similar to the following: AM70-WinOS-7.0.172.0.msi.log.

MAINT.LOG

Reports any patches or hotfixes installed to an AppManager Component

ResponseTime Module Installation logs

Report installation process of the Response Time modules on an AppManager agent.  For example, AD-RT_Install.log, SQL-RT_Install.log, Web-RT_Install.log

.


Cause

Overview/Scope

This discussion will cover the basic logs for the AppManager components.  Logs specific to particular monitored applications (Oracle, notes, etc.) will not be covered here.  Please refer to the Configuration notes or other documentation related to the specific Management Object.

Additional Information

Formerly known as NETIQKB73010