Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What other log files useful, and why are they not generated with the CiscoWorks MDCSupport utility?

April 26, 2017CiscoWorks files log mdcsupport useful utility

0

Posted

What other log files useful, and why are they not generated with the CiscoWorks MDCSupport utility?

1 Answer

0

Posted

A. When troubleshooting your system, you can use additional information that is not collected by the CiscoWorks MDCSupport utility. This information includes the following: –Any log file of the form hs_err_pid*.log located in the CSCOpx/MDC/Tomcat directory. For example hs_err_pid1396.log. These log files are normally the result of hard crashes to the tomcat process and are not common. –The CoreTib.log file, located in the CSCOpx/logs. This log file provides information about the Core tibco process. –The CiscoWorks Desktop also provides a diagnostic tool to gather additional information that can be useful. This tool is located under the Server Configuration drawer in the Diagnostics folder. The folder contains a link titled Collect Server Info. Click this link to generate an HTML page that links and formats several pieces of information into one file for easy access. –The log file for the JRun servlet engine. This file is located at CSCOpx/lib/jrun/finish log pathMMF.