The Windows agent can't be started.
search cancel

The Windows agent can't be started.

book

Article ID: 418986

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine Automic SaaS

Issue/Introduction

The Windows agent starts, runs for a while, and then terminates with the following message:

U02000328 Unexpected error on listen port occurred, reason '2300', position 'java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:2300'.
U00045014 Exception 'java.io.IOException: "java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:2300"' at 'com.automic.agent.jetty.server.WebSocketServer.open():51'.
U00045015 The previous error was caused by 'java.io.IOException: "Failed to bind to 0.0.0.0/0.0.0.0:2300"' at 'org.eclipse.jetty.server.ServerConnector.openAcceptChannel():349'.
U00045015 The previous error was caused by 'java.net.BindException: "Address already in use: bind"' at 'sun.nio.ch.Net.bind0()'.
U02000041 Shutdown Agent 'Agent_Name'.
U02000010 Connection to Server 'AE_Server/<unresolved>:8443' terminated.
U02000002 Agent 'Agent_Name' version '24.4.2+hf.1.build.1759570320937' ended abnormally.

Environment

Automic Automation Engine 24.X

Cause

Configuration.

The port specified in the agent's INI file is already in use.

Resolution

 

 

To configure a different port, modify the PORT parameter within the agent's INI file.

PORT=

More information about the Windows agent INI file can be found at the following link.

Additional Information

All the ports in use can be found with the netstat command:

netstat -ano | findstr "2300 PID"

This delivers the following result:

 Proto  Local Address           Foreign Address        State           PID
  TCP    0.0.0.0:2300           0.0.0.0:0              LISTENING       2472
  TCP    [::]:2300              [::]:0                 LISTENING       2472

In this particular case, Port 2300 is already in use by another Windows agent.