PowerProtect Data Manager: Linux deployment Core status reports Unhealthy

Summary: PowerProtect Data Manager Linux deployment ppdmadmin status reports Core is Unhealthy due to HTTP Proxies

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.

Symptoms

PowerProtect Data Manage (PPDM) Linux deployment reports an Unhealthy Core status while the Search and Reporting status is Healthy. 

+-----------+---------+-----------+----------+----------------------------+
| NAMES     | STATUS  | HEALTHY   | INSTANCE | LAST UPDATED               |
+-----------+---------+-----------+----------+----------------------------+
| core      | Started | Unhealthy | 1/1      | 14 minutes ago             |
| search    | Started | Healthy   | 1/1      | 1 week ago                 |
| reporting | Started | Healthy   | 1/1      | 1 week ago (uptime 1 week) |
+-----------+---------+-----------+----------+----------------------------+


  

Log evidence shows the dp-aiassistant service is unhealthy, triggering the Core status to show unhealthy.
time="" level=info msg="[PID:] instance_state.go:334 Get container information: {...core-1_dp-aiassistant-service_1 Running Unhealthy ...}"

Validation test from the PPDM Core Shell reports Service Unavailable:

[2026-06-25 10:16:42.432] You are now in ppdm-core shell. Type exit and press Enter to return to the host shell.
[2026-06-25 10:16:42.705] ppdm-core:/home/admin # curl -skv -X GET https://dp-asassiassistant:8-010/aiassistant/v1/health
[2026-06-25 10:17:59.630] * Uses proxy env variable no_proxy == 'localhost, 127.0.0.1,172.24.0.192/26,ppdm-core,keycloak,ciam-bora,iam-gateway,iam-token-handler,ese,ese.ppdm.local,reporting-engine,search-instance-1,search-instance-2,search-instance-3,search-instance-4,search-instance-5'
. . .
[2026-06-25 10:17:59.644] * Establish HTTP proxy tunnel to dp-aiassistant:8010
[2026-06-25 10:17:59.644] > CONNECT dp-aiassistant:8010 HTTP/1.1
[2026-06-25 10:17:59.644] > Host: dp-aiassistant:8010
[2026-06-25 10:17:59.644] > User-Agent: curl/8.14.1
[2026-06-25 10:17:59.646] > Proxy-Connection: Keep-Alive
[2026-06-25 10:17:59.646] >
[2026-06-25 10:17:59.726] < HTTP/1.1 503 Service Unavailable
[2026-06-25 10:17:59.726] < Connection: Keep-Alive
[2026-06-25 10:17:59.726] <
[2026-06-25 10:17:59.726] * CONNECT tunnel failed, response 503
[2026-06-25 10:17:59.726] * closing connection #0
[2026-06-25 10:17:59.744] ppdm-core:/home/admin # exit

Validation test from the Bare Metal host experiences a Gateway Time-out:

[2026-06-25 10:18:45.135] Bare_Metal_Host:/# curl -skv -X GET https://172.24.0.193:8010/aiassistant/v1/health
[2026-06-25 10:19:36.916] * Uses proxy env variable no_proxy == 'localhost, 127.0.0.1'
. . .
[2026-06-25 10:20:29.948] ^C< HTTP/1.1 504 Gateway Time-out
[2026-06-25 10:20:51.963] < Connection: Keep-Alive
[2026-06-25 10:20:51.963] <
[2026-06-25 10:20:51.963] * CONNECT tunnel failed, response 504
[2026-06-25 10:20:51.963] * closing connection #0

 

Cause

The health check API calls for verifying the status of the dp-aiassistant service fail due to the presence of HTTP proxies.  

Resolution

Workaround:

Verify and then remove the HTTP proxies.

  1. Verify the exact HTTP and HTTPS proxy syntax with an echo.   
    1. For example test both lowercase and uppercase letters:
      echo $http_proxy
      echo $HTTP_PROXY
  2. Shutdown the PPDM core
    ppdmadmin stop
  3. Remove the Proxy setting and any configured HTTP Proxies identified in Step #1
    unset PROXY_ENABLED
    unset HTTP_PROXY
    unset HTTPS_PROXY
  4. Start the PPDM core
    ppdmadmin start
Article Properties
Article Number: 000505943
Article Type: Solution
Last Modified: 14 أيلول 2026
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.