Unnecessary ftx-tracefiles written after agent upgrade to 12.2.4

book

Article ID: 143518

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

We upgraded an Automic agent from version V12.0.4 to 12.2.4. After the upgrade was finished the agent started to create some unknown files that are named like ucxjxxx_Agent_t00-ftx-RunID.txt,

e.g. ucxjxxx_GF0VSXAS064P_UC42P_t00-ftx-724257172.txt. These files won't be deleted by the normal period for logfiles. After a search in the internet and the broadcom community and knowledge base we found the following articles:

- https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=784772

- https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=84902

The last article says that the issue is known and it would be fixed with  versions 12.0.4 and 12.1.1 of the agent. Unfortunately it still exists or is rolled out again

Cause

This due to the wrong setting in max trace size to 0 in the old Java UI 

When this is set to 0 agent creates FTX and other trace files

Environment

Release : 12.2

Component : AUTOMATION ENGINE

Resolution

Set the max trace size to 128 and the agent stops creating trace files.