ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA Release Automation Clean up and Troubleshooting best practices

book

Article ID: 145909

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

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 : 6.5, 6.6, 6.7 or higher

Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER

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

Agent

Execution/Process

Additional Information

Some other related reference documents