AAKE log files missing or mismatch

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Some of the WPs do not write logs or there is a mismatch between WP name and log file name.

Two examples of the issues:

WP003: Does not create log, log is not available in the AWI, creates trace file once it's enabled.
WP004: Does not create log, log is available in the AWI, creates trace file once it's enabled - it seems its log is in WPsrv_log_002_00.txt looking at the hostname

Environment

AAKE

Cause

This issue only happens in AAKE. It occurs when multiple pods start at the same time (in the same second) and all logs are stored in a central directory.

Upon process start, a temporary logfile is created  with the name syntax: *P_srv_<YYYY_MM_DD_HHMMSS>_<PID>,

Because in  AAKE all processes start with PID=1, processes that start in the same second will have the same name.

 

Resolution

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:

Component(s): Automation Engine

Automation.Engine 24.4.1 - Available

Additional Information

The reference for this fix is DE156521