WA Agent Hangs During Startup
Article ID: 106065
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
Workload Automation Agent
CA Workload Automation AE - System Agent (AutoSys)
CA Workload Automation DE - Business Agents (dSeries)
CA Workload Automation DE - System Agent (dSeries)
Issue/Introduction
After starting the WA Agent on Linux, it never completes the startup process and becomes available for connections from a manager. The defaultlog_agent.log only contains a single line...
07/10/XXX 00:00:20.350-0400 2 main.MainThread.CybAgentDriver.runApplication[:243] - CA Workload Automation Agent 11.4, Build 1609, Service Pack 00, Maintenance Level 0 starting
07/10/XXX 00:00:20.350-0400 2 main.MainThread.CybAgentDriver.runApplication[:243] - CA Workload Automation Agent 11.4, Build 1609, Service Pack 00, Maintenance Level 0 starting
Environment
WA Agent 11.x/12.x
Linux
Cause
The level of available entropy on the server may be extremely low. This is common on VMs that are not heavily utilized. Low entropy can cause the agent to hang during startup while trying to initialize encryption routines.
Resolution
Run the following command to monitor the available entropy on the server.
watch -n 1 cat /proc/sys/kernel/random/entropy_avail
In addition, a kill -3 can be issued against the hung cybAgent.bin process which will cause it to dump thread info to <AGENT_HOME>/nohup.stdout. In that file, search for the following...
MainThread" prio=10 tid=0xf6908c00 nid=0x3153 runnable [0xf740e000]
java.lang.Thread.State: RUNNABLE
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at sun.security.provider.SeedGenerator$URLSeedGenerator.getSeedBytes(Unknown Source)
If the above is in the nohup.stdout file after the thread info dump, it confirms that the agent is hanging while trying to initialize encryption routines.
Ideally, the available entropy on the server should be at a minimum of 300 to avoid issues with the agent initializing the encryption routines.
watch -n 1 cat /proc/sys/kernel/random/entropy_avail
In addition, a kill -3 can be issued against the hung cybAgent.bin process which will cause it to dump thread info to <AGENT_HOME>/nohup.stdout. In that file, search for the following...
MainThread" prio=10 tid=0xf6908c00 nid=0x3153 runnable [0xf740e000]
java.lang.Thread.State: RUNNABLE
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at sun.security.provider.SeedGenerator$URLSeedGenerator.getSeedBytes(Unknown Source)
If the above is in the nohup.stdout file after the thread info dump, it confirms that the agent is hanging while trying to initialize encryption routines.
Ideally, the available entropy on the server should be at a minimum of 300 to avoid issues with the agent initializing the encryption routines.
Consult System Administrator to enable 'rngd' service to increase the entropy.
E.g.
systemctl enable rngd.service
Additional Information
See this Red Hat link for more details on entropy.
Feedback
Yes
No
Powered by
