This document outlines the logs, thread dump, etc. that are needed to analyze and identify the root cause of a problem.
It is advisable to collect these logs while opening a Support Case.
There are various logs generated by CA Release Automation, each having rolling up index and file size.
Among all logs, there are some important logs which are recommended to be retained using a large retention number (log retention no.) to prevent overwriting of events.
All Versions of CA Release Automation
The value for number of log files and their size is determined considering disk space available in an environment. A trade-off can be made between file-size and retention number.
Important Log files - Component Wise
Component | File Location | Important Log Files | Modification to increase log file number |
---|---|---|---|
Management Server | \webapps\datamanagement\WEB-INF\log4j.properties |
|
|
Execution Server | \webapps\execution\WEB-INF\log4j.properties |
|
|
Agent | \conf\log4j.properties |
|
|
Retrieval/Repository Agents ** | \conf\log4j.properties |
|
|
** Retrieval or Repository agents, in product terminology refer to agents which are responsible for fulfilling request to download and distribute artifacts.
When and how to collect log files?
Component | Good to have |
---|---|
Management Server | All logs |
Execution Server(If multiple Execution servers we need logs from all impacted) | All logs |
Agent (If multiple Agents we need logs from all impacted agents) | All logs |
UI | All logs |
Beside logs, sometimes we need additional information from the product JMX console listed below:
Component | JMX Location (localhost need to be replaced with NAC/NES/NAG IP/Hostname) | JMX Operations |
---|---|---|
Management Server | http://localhost:20203/mbean?objectname=noliocenter%3Atype%3Dinfo |
Execute below operation and capture the result of below operations a. requestStackTrace b. listActiveRuns c. memoryStatus |
Execution Server | http://localhost:20203/mbean?objectname=com.nolio.nimi.jmx%3Aname%3DnimiJMX%2Ctype%3DNimiJMX |
Execute below operation and capture the result of below operations a. memoryDump b. threadDump |
Agent | http://localhost:8282/mbean?objectname=Deployer%3Acommunication%3DnimiManager |
Execute below operation and capture the result of below operations a. threadDump b. retrieveEnginesStatus c. memoryDump |
Hibernate SQL Logging | http://localhost:20203/mbean?objectname=Logging%3Atype%3DLog4j |
Execute below operation to turn on/off hibernate SQL logging a. turnOnHibernateSQLLogging b. turnOffHibernateSQLLogging |
HTTP Request Logging | http://localhost:20203/mbean?objectname=Logging%3Atype%3DLog4j |