PowerProtect Data Manager: Relatórios de status do núcleo de implementação do Linux Não íntegros

A implementação do PowerProtect Data Manager (PPDM) Linux relata um status Unhealthy Core enquanto o status Search and Reporting é 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) |
+-----------+---------+-----------+----------+----------------------------+

As evidências de log mostram que o serviço dp-aiassistant não está íntegro, acionando o status Core para mostrar que não está íntegro.
time="" level=info msg="[PID:] instance_state.go:334 Get container information: {...core-1_dp-aiassistant-service_1 Running Unhealthy ...}"

O teste de validação do PPDM Core Shell relata que o serviço está indisponível:

[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

O teste de validação do host bare metal apresenta um tempo de espera excedido do gateway:

[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

As chamadas da API de verificação de integridade para verificar o status do serviço dp-aiassistant falham devido à presença de proxies HTTP.  

Solução temporária:

Verifique e remova os proxies HTTP.

1. Verifique a sintaxe exata do proxy HTTP e HTTPS com um eco.   
   1. Por exemplo, teste letras minúsculas e maiúsculas:
      echo $http_proxy
echo $HTTP_PROXY
2. Desligue o núcleo do PPDM
   ppdmadmin stop
3. Remova a configuração Proxy e todos os proxies HTTP configurados identificados na Etapa #1
   unset PROXY_ENABLED
unset HTTP_PROXY
unset HTTPS_PROXY
4. Iniciar o núcleo do PPDM
   ppdmadmin start