Detection server unknown after upgrading to 25.1

Products

• Data Loss Prevention Core Package

Issue/Introduction

After an upgrade to 25.1 1 detection server went into an unknown state while the others upgraded without issue.

Cause

Errors found leading to this cause:

PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed

Level: SEVERE
Message:  Failed to start EnforceConnectorControllerUDS
org.jboss.netty.channel.ChannelException: Failed to bind to: <EXAMPLE>/<unresolved>:8100

TC - Fatal exception  for connection number 161 at DATE/TIME. Unrecoverable exception in exceptionCaught() for connection 'C-161 to '/I<PADDRESS>:26897'.  Runtime exception was caught.Connection specific high frequency logs for connection number = 161. There is no peerId information for this connection.

 

 

Resolution

In EnforceConnector.properties it was found that the UDS keystore file path was pointing to a very old keystore Monitor.date.sslKeystore

When we changed the path to the monitor.default.jks and restarted services the detection server came right up in the Enforce console