DPA Shows Application Server Admin UI as Red in ACM After Upgrade to IDPA 2.7.6

Summary: This article covers how to fix an issue with Reporting and Analytics in Data Protection Advisor (DPA) after upgrade to IDPA version 2.7.6.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

After the upgrade to IDPA 2.7.6, the Reporting and Analytics (DPA) shows red in the ACM UI.

In the ACM server.log, one of the two following errors is seen:

2024-02-09 10:42:54,841 INFO  [Thread-25170]-util.RestUtil: Making REST call: https://x.x.x.x:9002/dpa-api/license ,method: GET Meditype application/v
nd.emc.apollo-v1+xml
2024-02-09 10:42:54,882 INFO  [Thread-25170]-util.RestUtil:  REST request return code: 500, expected code: OK
2024-02-13 19:58:25,577 INFO  [Thread-93984]-util.RestUtil: Making REST call: https://x.x.x.x:9002/dpa-api/license ,method: GET Meditype application/vnd.emc.apollo-v1+xml
...
2024-02-13 19:58:25,601 INFO  [Timer-4]-dao.HealthMonitorUtilityDao: getDeviceDataByType --> Executing query to get device by type and ip
2024-02-13 19:58:25,602 INFO  [Thread-93984]-util.RestUtil:  REST request return code: 404, expected code: OK

In the DPA APP server.log, errors like the following are seen:

16224:2024-02-09 14:24:20,299 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.web.deployment.default-host./reportengine-api: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./reportengine-api: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
16238:2024-02-09 14:24:20,318 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 72) JBWEB001100: Error starting context: java.lang.IllegalArgumentException: JBWEB006706: Document base /opt/emc/dpa/services/./standalone/tmp/vfs/deployment/deploymentd28786588379a29/listener-processor-war.war-37c80da349d9164f does not exist or is not a readable directory
16252:2024-02-09 14:24:20,338 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 72) JBWEB001103: Error detected during context /listener-processor-api start, will stop it
16253:2024-02-09 14:24:20,339 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 72) MSC000001: Failed to start service jboss.web.deployment.default-host./listener-processor-api: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./listener-processor-api: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
16296:2024-02-09 14:24:21,337 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.4.1.Final-redhat-SNAPSHOT "Janus" started (with errors) in 41681ms - Started 21215 of 21353 services (58 services failed or missing dependencies, 315 services are lazy, passive or on-demand)

Cause

DPA has processes in the /opt/emc/dpa/services/./standalone subdirectories that are causing the APP services to function properly. DPA shows services running but some internal services have failed.

Resolution

Run the following procedure to address this issue:
  1. Stop the DPA services with the following command. Run this command on the DPA DS server first then the DPA APP server. 
dpa.sh svc stop
  1. Log in to the DPA APP server as root using SSH or PuTTY and run the following command:
rm -rf /opt/emc/dpa/services/standalone/data
rm -rf /opt/emc/dpa/services/standalone/tmp
  1. Reboot the DPA DS server and start services:
reboot
dpa.sh svc start
  1. Reboot the DPA APP server and start services. 
reboot
dpa.sh svc start
  1. Confirm that you can log in to the DPA UI.
  2. Confirm that DPA shows green in ACM UI. 
Article Properties
Article Number: 000222530
Article Type: Solution
Last Modified: 26 Mar 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.