search cancel

Aggregator fails to start error 1101


Article ID: 171570


Updated On:


Data Loss Prevention Endpoint Prevent


When starting the aggregator on the endpoint server it reports error 1101 to enforce.

Server Status Error 1101

Endpoint Server Error 1101

Aggregator Logs:

Class: com.vontu.monitor.communication.configitem.ConfigItemSource$UpdateLogger
Method: itemLoaded
Level: FINE
Message:  Loaded DetectionServerConfig: informationMonitorID=4803, uniqueName=<SERVER NAME> (ENDPOINT), channels=[isEnabled=false, maxParallelScans=1, isEnabled=false, port=1344, backlog=16, shouldInspectMultipartOnly=false, isPreventTrial=true, requestConnectionsMax=16, requestBodySizeMin=4096, requestExcludedUrls=null, requestExcludedUserAgents=null, responseConnectionsMax=16, responseBodySizeMin=4096, responseExcludedUrls=null, responseExcludedUserAgents=null, responseContentTypes=text/*
application/pdf, icapChannelSubType=1001, tabletIpRanges=[], isEnabled=false, isPreventTrial=true, maxConnections=12, keyStore=, isReflectMode=true, inlineSmtpChannelID=0, inlineSmtpChannelSubType=2001, smtpForwardHops=[], password=keyAlias=null, isEnabled=false, transferFolderPath=null, packetCaptureChannelID=5705, monitorNICs=[], isEnabled=false, transferFolderPath=null, isEnabled=true, aggregatorHost=, aggregatorPort=8000, agentVersion=null, lastAgentUpgrade=null, replicatorCommLayerPort=10443, replicatorCommLayerHost=, agentConfig=null, isEnabled=false, numSessions=12, port=10080, sessionTimeout=30000, isEnabled=false, port=8080], pgpUniversalServer=null.

Class: com.vontu.communication.transport.TransportConfig
Method: logProperties
Level: INFO
Message:  listenPort: 8000

Class: com.vontu.communication.transport.ServerChannelManager
Method: <init>
Message:  failed to init server channel channel manager Address already in use: bind

Class: com.vontu.communication.dataflow.TransportManager
Method: <init>
Message:  Got IOException while trying to initialize the transport layer!
com.vontu.communication.transport.exception.TransportException: Address already in use: bind


DLP 14.x
DLP 15.x


Another program was binding to port 8000 before the DLP services started.


The solution is to stop the program that is already binding to that port. Use the following troubleshooting stepts to identify the program causing the port conflict.

  1. Find the port that the aggregator is trying to bind. Look at the informational message right before binding error. In the case above it we could see the listen port was attempting to bind to 8000 and then the bind errors occured.
  2. Next stop the vontu services. then run the following command using the port listed in the logs:
Netstat -ano | find "8000"
  1. Get the process ID (PID) at the end of the line that is displayed after the "LISTENING" message
  2. Run the following command to get the process info. In the following exampe we use 6716
tasklist /FI "PID eq 6716"

The listed .exe is the program that is already bound on that port. Stop that program or reconfigure it to use another port. Note: When the vontu services are started and working properly then the listed .exe should be java.exe for the PID using that port.

Alternatively you can run the following command to kill the process

Taskkill /FI "PID eq 6716"

Then start the vontu services. As long as the original process does not restart and bind the same port then the aggregator should bind as expected.