CA WA ESP Agent failure
search cancel

CA WA ESP Agent failure

book

Article ID: 94871

calendar_today

Updated On:

Products

Workload Automation Agent

Issue/Introduction

The CA WA ESP Agent failed. Please let me know what the root cause was. Is there a fix for this issue? 
I found the following message in the defaultlog_agent.archive.log after the agent was brought back up: 
04/25/2018 23:49:29.339 CDT-0500 1 main.Thread-6.CybSimpleHealthMonitor$ShutdownHook.run[:399] - JVM shutting down 

I also found this message in receiver.archive.log: 
04/25/2018 23:49:09.714 CDT-0500 2 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverChannel.receive[:252] - Exiting conversation 

This message was found in the runner_os_component.archive.log: 
Wed Apr 25 23:49:20 2018: ServiceControl called with SERVICE_CONTROL_INTERROGATE 
Wed Apr 25 23:49:29 2018: System.exit(143) has been invoked 

Environment

OS: Win2012 
CAWA : 11.3 SP6 
ESP:11.4 

Cause

OS maintenance was applied on Win2012 box.
After maintenance was applied application was not bounced properly.

Resolution

 Collected Agent log files which showed no indication of the problem.
As a next step collected system log files.

Solution:
I found following message in event viewer log file The CA WA Agent service depends on the Netlogon service which failed to start because of the following error: The operation completed successfully.

RCA:
Seems all the services were not up once OS maintenance was applied. So when system was restarted that brought all services up and hence Autosys agent is up since that needed step was taken.