PowerProtect Data Manager: Linux-implementering Rapporter om kjernestatus Usunn
Oversigt: PowerProtect Data Manager Linux-implementering ppdmadmin-statusrapporter Kjernen er usunn på grunn av HTTP-proxyer
Symptomer
Linux-distribusjon av PowerProtect Data Manage (PPDM) rapporterer en usunn kjernestatus mens søke- og rapporteringsstatusen er Sunn.
+-----------+---------+-----------+----------+----------------------------+
| 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) |
+-----------+---------+-----------+----------+----------------------------+
Loggbevis viser at dp-aiassistant-tjenesten er usunn, noe som utløser at Core-statusen viser usunn.
time="" level=info msg="[PID:] instance_state.go:334 Get container information: {...core-1_dp-aiassistant-service_1 Running Unhealthy ...}"
Valideringstest fra PPDM Core Shell rapporterer at tjenesten ikke er tilgjengelig:
[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
Valideringstest fra Bare Metal-verten opplever et tidsavbrudd for 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
Årsag
API-en for tilstandskontroll kaller opp for å verifisere statusen til dp-aiassistant-tjenesten mislykkes på grunn av tilstedeværelsen av HTTP-proxyer.
Løsning
Omgåelse av problemet:
Kontroller og fjern deretter HTTP-proxyene.
- Bekreft den nøyaktige HTTP- og HTTPS-proxysyntaksen med et ekko.
- Du kan for eksempel teste både små og store bokstaver:
echo $http_proxy
echo $HTTP_PROXY
- Du kan for eksempel teste både små og store bokstaver:
- Avslutte PPDM-kjernen
ppdmadmin stop - Fjern proxy-innstillingen og eventuelle konfigurerte HTTP-proxyer identifisert i trinn #1
unset PROXY_ENABLED
unset HTTP_PROXY
unset HTTPS_PROXY - Start PPDM-kjernen
ppdmadmin start