Error: U02000076 and U02000010 Disconnections - Automic NSK Agent
search cancel

Error: U02000076 and U02000010 Disconnections - Automic NSK Agent

book

Article ID: 438806

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Automic NSK (HP NonStop) agents experience frequent disconnections and reconnections from the Automation Engine, typically occurring every 15 minutes. This behavior is symptomatic of a product defect affecting heartbeat connection management.

 

ERROR MESSAGE:

"U02000076 Connection to CP Server '[system-id]' closed." "U02000010 Connection to Server '[hostname]:<CP_Port#>' terminated." "AWAITIO-Error: 4127 on [IP-address]:<CP_Port#>"

 

SYMPTOMS:

  • Agent logs show frequent connection terminations exactly every 11 minutes (660 seconds).

  • The agent closes the connection with "Server does not respond anymore, will be closed."

  • Network packet captures (PCAPs) show silence for approximately 5-6 minutes followed by a new SYN from the agent.

  • No TCP RST or FIN packets are observed during the silent drop.

  • The status changes to "ended_lost" after several days of failed reconnection attempts.

 

CONTEXT: Occurs specifically when no jobs are running for a prolonged period. Disconnects do not occur if a job runs at least every 3 minutes.

IMPACT: Automated processing on the HP NonStop platform is interrupted, requiring manual intervention to restore the agent connection.

 

Environment

OS: HP NonStop NSK L24.08.1

Agent: NSK Agent 24.4.0+build.1

AE Server Version: 24.4.1+build.1750690770737

AE Server OS: Windows Server 2022 

Network: Stateful routing boundary between Agent and AE

 

Cause

This behavior is caused by a product defect (DE183927) where the HP NonStop agent fails to maintain the connection heartbeat correctly, leading to periodic reconnections.

 

Resolution

Fixed in release Automic NSK Agent 24.4.5 and higher.

Additional Information

It is possible for intermediary network devices (firewalls or L3 switches) to silently drop idle TCP sessions from their state tables after a common 5-minute timeout threshold. Because the agent's default internal timeout/check interval is set higher (660 seconds), it remains unaware that the connection was severed at the 5-minute mark until its own 11-minute timer expires, at which point it logs the U02000076 and U02000010 errors.

RELATED RESOURCES: