DCS Manager service crashing after upgrading to 6.9.3 while using an old sha1 compatible server.xml for Legacy Agents
search cancel

DCS Manager service crashing after upgrading to 6.9.3 while using an old sha1 compatible server.xml for Legacy Agents

book

Article ID: 259830

calendar_today

Updated On:

Products

Data Center Security Server Advanced

Issue/Introduction

The DCS Manager service is crashing after upgrading to 6.9.3 while using an old sha1 compatible server.xml for Legacy Agents

manager.err log

SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@4c36250e]

...

...

Caused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files (x86)\Symantec\Data Center Security Server\Server\tomcat\symapps\bridge\dcs-bridge] is not valid
    at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:762)
    at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:719)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    ... 30 more

 

Environment

DCS 6.9.3.x 

Cause

Old operating systems like Windows 2000 or Windows NT are not compatible with SHA256 and therefore need SHA1 certificates. Starting with 6.9.2 the ciphers are upgraded and removes sha256. Because of this the old server.xml file needs to be replaced with the backup server.xml file from version 6.9.1.

https://knowledge.broadcom.com/external/article/241624/upgrading-the-data-center-security-serve.html 

Additionally, the DCS version 6.9.3 does not use the bridge services and removes it from the server.xml file that was upgraded. Because of this, the bridge service needs to be removed from the prior server.xml before placing it back into the <install Directory>\Symantec\Data Center Security Server\Server\tomcat\conf directory or the DCS Manager service will crash because it's looking for a service that's no longer in the system.

Resolution

1. Stop the DCS Manager services

2. Move the upgraded server.xml out of the directory and into a safe backup location
<install Directory>\Symantec\Data Center Security Server\Server\tomcat\conf\server.xml

3. Open the backup server.xml that was used prior to the upgrade and remove the bridge-service portion of the server.xml file



4. Save the file and place it back in the <install Directory>\Symantec\Data Center Security Server\Server\tomcat\conf\ directory

5. Restart the DCS Manager services and check if the legacy agents are communicating to the Manager and that the DCS services are staying up