Application service not starting on the secondary cluster node after installing ePO 5.10 Update 10 or later

Technical Articles ID: KB94883
Last Modified: 2023-08-10 12:14:02 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.10 Update 10 or later

Problem

The ePO Application service is missing or not started when you install ePO 5.10 Update 10 on a cluster. You see this issue only on the secondary cluster node.

This issue occurs when you upgrade to ePO 5.10 Update 10 because Update 10 upgrades tomcat7.exe to tomcat9.exe.

Cause

When you run the ePO 5.10 Update 10 on the primary cluster node, it successfully updates the folders on the data drive and registry. But, when you do a failover to the secondary node, the Tomcat is still with tomcat7.exe.

NOTES:

You can't rerun the ePO 5.10 Update 10 setup because the same shared folder is used by the secondary node.
With ePO 5.10 Update 1–9, there's no upgrade for the Tomcat service.

Solution

To get the ePO registry and services to update on the secondary cluster node, you need to use the REPAIR option.

Run the REPAIR option on the secondary node through the ePO 5.10 Update 10 or later installer.

This action allows the updating of both the registry and services to use tomcat9.exe.

To find out more about Disaster Recovery in a cluster environment, see the ePO 5.10 Update 10 Release Notes.

Knowledge Center

Application service not starting on the secondary cluster node after installing ePO 5.10 Update 10 or later

Environment

Problem

Cause

Solution

Related Information

Affected Products

Languages:

Title

Title

Knowledge Center

Application service not starting on the secondary cluster node after installing ePO 5.10 Update 10 or later

Environment

Problem

Cause

Solution

Related Information

Affected Products

Languages:

Choose your region

Title

Title