Cisco Headend System Release 2.5
1-12
Why Choose System Release 4.0?
4001703 Rev B
Logging: New Logging Utility Makes Troubleshooting Even Easier
Overview
A new button has been added to the Utilities tab that allows you to configure and display
information that the DNCS records about some critical processes and their libraries.
The new Logging utility makes it easier than ever to capture key information for
The new Logging utility makes it easier than ever to capture key information for
troubleshooting. Historically, many of the messages in the dncsLog file were simply
statuses and did not indicate any error conditions. Operators had to filter through a
lot of status information to find specific error conditions. The new Logging utility
allows you to fine-tune log levels for processes and their libraries. The fine-tuning
ensures that the dncsLog file contains more of the information you need to
troubleshoot issues. The dncsLog file contains information for all processes. Each
process also has its own log file, providing access to focused troubleshooting
information.
During normal operation, you may choose to log information at the Error Condition
During normal operation, you may choose to log information at the Error Condition
level only. If a problem occurs, you can turn on several additional log levels, such as
the Alert and Debug levels, to capture more information in the dncsLog file and the
individual process log files.
A key benefit of the logging utility is that logging level changes are now allowed
A key benefit of the logging utility is that logging level changes are now allowed
without the need to restart processes, potentially correcting a problem before data
can be found to explain the problem.
Note: The dncsLog file is a very large file; a full day could easily reach 10 MB or
Note: The dncsLog file is a very large file; a full day could easily reach 10 MB or
more. Use care when Logging to avoid the risk of filling the disk. Logging can
impact system performance.
For more information on all of the available log levels and for step-by-step
For more information on all of the available log levels and for step-by-step
procedures for adjusting log levels, see the DNCS Online Help.
Does the Logging Utility Eliminate the Need for EMCDEBUG Flags?
Not yet. While one long-term goal of the Logging utility is to obsolete the need for
Enhanced Machine Control Debug (EMCDEBUG) flags, most of the processes still
require setting of the EMCDEBUG flags in the .profile file.
At the present time, the eventManager, logManager, ocdlMgr, and oxaitMgr
At the present time, the eventManager, logManager, ocdlMgr, and oxaitMgr
processes do not require the EMCDEBUG flags to be set. You must continue to
maintain your current EMCDEBUG flags in the .profile file on the DNCS to control
the output of various processes that still use the old logging scheme.
Note: As a general rule, the only processes that should always be set to debug are
Note: As a general rule, the only processes that should always be set to debug are
bossServer, camPsm, dsm, qamManager, and siManager. Cisco Services may instruct
you to temporarily set additional processes to debug for troubleshooting purposes.
In these cases, Cisco Services will tell you whether to use the Logging utility or
EMCDEBUG flags.