Linux Agent memory leak | U02000258 ... '2 - No such file or directory'.

book

Article ID: 205902

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation CA Automic Operations Manager CA Automic Oracle

Issue/Introduction

Using AWA Unix or Linux agent on 12.3.4 and earlier, memory utilization for the agent continues to increase or stays at a certain amount and does not release memory.  It hogs memory to the point where jobs can no longer start.  The following error can be seen in the agent log file:

20201105/082946.521 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started. 
20201105/082946.535 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/082946.664 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started.
20201105/082946.678 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/082951.601 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started. 
20201105/082951.617 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/082951.727 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started. 
20201105/082951.741 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/082956.680 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started. 
20201105/082956.695 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/082956.790 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started. 
20201105/082956.804 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/083001.759 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started. 
20201105/083001.774 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/083001.858 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started. 
20201105/083001.874 - U02000258 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' completed with error, reason '2 - No such file or directory'. 
20201105/083006.898 - U02000256 Upload of file '[full path to agent directory]/temp/OAAYDZFX.TXT' started.

Cause

This is caused by a memory leak when the agent attempts to view a log file that is no longer in the agent's temp directory.
This can be caused by:
1) Using the "Show latest output" button in the Last Report of a task that has already finished
2) Having a job report save only to file, not to database, and then deleting the file and attempting to view the job report

There are three issues at play here that all revolve around one type of functionality which is attempting to view a log file from the OS where an agent resides when that file does not exist on the server.  

By default, jobs are set to store the job reports on the database (You can see this in the UNIX tab of a job under "Job Report" where "Database" is checked under Store to).  When the agent runs a job, it keeps the report on the server until the job is finished running all OS commands.  Then it transfers the report to the database and removes the file from the operating system.  What we've found through testing is the following:

1) Memory not released: Used memory is not released when the agent attempts to read a report file from the agent for a report that is not on the OS - this can be found by checking the "File" option under Job Report, unchecking "Database", running a job, deleting the file from the OS, and then attempting to view the report for the job.  This is the main issue here.
2) Show latest output continues to try to read reports that are not on the OS: When the report file is set to store on database only, if you go to the last report for a job while it is still running and click on "Show latest output", even when the job is finished running, it will continuously attempt to access the file on the OS even though it isn't there.  This causes the message in the agent log:
U02000258 Upload of file '<full path to agent>/temp/O<runnr in alpha format>.TXT' completed with error, reason '2 - No such file or directory'.
3) Show latest output is perpetually clicked when navigating away: If you click on the "Show latest output" in the last report for a job and then move to somewhere else in the same browser tab, for example, clicking on Process Monitoring perspective, the "Show last output" button never unclicks itself.  There is no way to unclick "Show latest output" from this point.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

Possible workarounds:

  1. There is a way to stop the memory from continuing to increase when this situation happens which is to go to the Administration perspective in the AWI, right-click on the agent, and choose "Disconnect Agent Connection" - this will disconnect the agent and reconnect it fairly quickly, and will stop the memory from increasing, but will not release the memory that was already used.
  2. To release the memory: restart the agent
  3. To prevent the issue:
    1. instruct users not to click on the "Show latest output" button for job reports
    2. do not delete O*.TXT files from the agent's /temp directory unless necessary

This will be fixed in a future release.