System Agent stopped without having performed manual shutdown

Products

• Autosys Workload Automation

Issue/Introduction

System Agent suddenly ended. No manual stop command was performed.

Environment

System Agent 12.x , 24.x on Linux

Cause

When a manual shutdown is performed, the following lines are show in in the runner_os_component log file.

The following is shown in the messages log file

01/05/2026 15:54:43.203+0000: Caught signal 15; shutting down
01/05/2026 15:54:43.203+0000: NamedPipeServer starting shutdown thread on CONTROL SHUTDOWN_AGENT
01/05/2026 15:54:43.203+0000: Initiating shutdown sequence...
01/05/2026 15:54:43.203+0000: Named pipe server is about to stop
01/05/2026 15:54:43.203+0000: NamedPipeServer exiting on CONTROL SHUTDOWN_INTERNAL
01/05/2026 15:54:44.204+0000: Named pipe server stopped
01/05/2026 15:54:44.204+0000: Transmitter is about to stop
01/05/2026 15:54:44.204+0000: Transmitter: Sending AFM: . . . . . CONTROL INACTIVE
01/05/2026 15:54:44.204+0000: shutdownVM: Attaching JVM thread
01/05/2026 15:54:44.204+0000: shutdownVM: invoking cybAgentDriver.shutdown()
01/05/2026 15:54:44.205+0000: Transmitter wait for completion is over
01/05/2026 15:54:44.205+0000: JVM is shutting down... . Maximum grace period - 300 seconds
01/05/2026 15:54:44.205+0000: JVM shutting down. 0 sec. has elapsed
01/05/2026 15:54:44.226+0000: Receiver: exiting on SHUTDOWN request
01/05/2026 15:54:44.272+0000: Exited receive loop
01/05/2026 15:54:44.272+0000: Receiver stopped
01/05/2026 15:54:44.287+0000: Transmitter stopped
01/05/2026 15:54:44.351+0000: CybAgentDriver has exited
01/05/2026 15:54:45.205+0000: Receiver is about to stop
01/05/2026 15:54:45.205+0000: Shutdown sequence complete

In the runner_os_component, this line "Caught signal 15; shutting down" wasn't produced.

In the Linux /var/log/messages file, the following was found back

Jan  3 05:54:18 server.example.com kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=system.slice,mems_allowed=0,global_oom,task_memcg=/system.slice/waae_agent-WA_AGENT.service,task=java,pid=3292022,uid=671171797

Jan  3 05:54:18 server.example.com systemd[1]: waae_agent-WA_AGENT.service: A process of this unit has been killed by the OOM killer.

Jan  3 05:54:20 server.example.com waae_agent-WA[357770]: CA-System Agent WA_AGENT

Jan  3 05:54:20 server.example.com waae_agent-WA_AGENT[357787]: Agent service is stopping...

Jan  3 05:54:20 server.example.com waae_agent-WA_AGENT[357787]: Agent service has been stopped

Jan  3 05:54:20 server.example.com waae_agent-WA_AGENT[357770]: stopped.

 

 

 

Resolution

OOM Killer is a process that the linux kernel employs when the system is critically low on memory. This situation occurs because the linux kernel has over allocated memory to its processes.
Linux Admin team to verify the OOM rules that are implemented.