CA Release Automation Clean up and Troubleshooting best practices
Article ID: 145909
Updated On:
Products
Issue/Introduction
What are the best practices for maintaining CA Release Automation (CARA) components in terms of disk space optimization, basic troubleshooting etc.
Environment
Release Automation 6.7 or higher
Resolution
It will be difficult to have a single document covering various aspect of system maintenance activity, but we try our best to summarize most common scenarios and troubleshooting of same.
Before performing any maintenance or troubleshooting it is better to analyze the cause of the issue and henceforth it is important to review application logs. Please find document below listing various logs and information collected in them.
Some common folders which are important and required for cleanup are list below. Please note that some of the folders may not be present as it is determined by which version of CA Release Automation you are using and which components are installed and in what conjunction. Nolio RA services should be stopped, before the cleanup, on the system where the file/folder cleanup is taking place.
files_cache
files_registry
files_temp
persistency
temp
patchBackup
upgradeBackup
logs
webapps\log_collector (NAC)
logs\applicationLogs (Agent)
activemq-data\nac\LevelDB (NAC)
activemq-data\nes\LevelDB (NES)
Please find some common scenarios and respective troubleshooting steps
NAC and NES
- For Connectivity issue between NAC and NES
- Some scenarios that require clearing the ActiveMQ persistence store
Agent
- Not able to transfer file from RA agent to a remote RA agent
- Failed to download artifact to retrieval agent Artifact download task was cancelled, agent does not respond
- Safely deleting files from a CA Release Automation Agent install folder
Execution/Process
Additional Information
Some other related reference documents
Feedback
