PowerProtect：中繼資料同步工作在變更密碼後失敗

變更密碼後，中繼資料同步工作開始失敗。PowerProtect Data Manager 伺服器中儲存了正確的登入資料。

同步服務記錄 （sync.log） 檔，則有類似於以下內容的條目：

YYYY-MM-DDTHH:MM:SSmssZ INFO [] [resilience-sync] [][][][][] [c.e.b.s.e.r.i.ServerRestClient.lambda$getDestRestConnectionFromCache$1(282)][282 ] -  POWER_PROTECT_REST_CONNECTION_CACHE: No active PowerProtect RestClient found for XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX in cache so computing now 
YYYY-MM-DDTHH:MM:SSmssZ ERROR [] [resilience-sync] [][][][][] [c.e.b.s.e.r.i.ServerRestClient.checkHttpStatus(560)][560 ] -  Return code = 400 BAD_REQUEST, expected = 200 OK 
YYYY-MM-DDTHH:MM:SSmssZ ERROR [] [resilience-sync] [][][][][] [c.e.b.s.e.r.i.ServerRestClient.getDestRestConnectionFromCache(286)][286 ] -  getRestConnectionFromCache failed 
YYYY-MM-DDTHH:MM:SSmssZ ERROR [] [resilience-sync] [][][][][] [c.e.b.s.e.r.i.ServerRestClient.getDestRestConnectionFromCache(288)][288 ] -   Reason: Unable to login to remoteHost <PPDMHostName> with the certificate ., Remediation: Please verify the certificate for <PPDMHostName> and retry the operation., ExtendedInfo: null, ErrorCode: 400 
YYYY-MM-DDTHH:MM:SSmssZ ERROR [] [resilience-sync] [][][][][] [c.e.b.s.e.r.i.SyncInstanceRestClientImpl.getList(90)][90  ] -  Failed to execute request: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX /api/v2/sync-instance GET  
com.emc.brs.sync.api.operation.SyncOperationException: com.emc.brs.sync.api.operation.SyncOperationException: Unable to login to remoteHost <PPDMHostName> with the certificate .
	at com.emc.brs.sync.external.remote.impl.ServerRestClient.getDestRestConnectionFromCache(ServerRestClient.java:291)
	at com.emc.brs.sync.external.remote.impl.ServerRestClient.executeRequest(ServerRestClient.java:163)
	at com.emc.brs.sync.external.remote.impl.SyncInstanceRestClientImpl.getList(SyncInstanceRestClientImpl.java:74)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:196)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:751)
	at org.springframework.retry.interceptor.RetryOperationsInterceptor$1.doWithRetry(RetryOperationsInterceptor.java:92)
	at org.springframework.retry.support.RetryTemplate.doExecute(RetryTemplate.java:344)
	at org.springframework.retry.support.RetryTemplate.execute(RetryTemplate.java:233)
	at org.springframework.retry.interceptor.RetryOperationsInterceptor.invoke(RetryOperationsInterceptor.java:113)
	at org.springframework.retry.annotation.AnnotationAwareRetryOperationsInterceptor.invoke(AnnotationAwareRetryOperationsInterceptor.java:162)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184)
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:751)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:703)
	at com.emc.brs.sync.external.remote.impl.SyncInstanceRestClientImpl$$SpringCGLIB$$0.getList(<generated>)
	at com.emc.brs.sync.context.service.impl.ResilienceScheduleServiceImpl.getSyncInstancesFromRemote(ResilienceScheduleServiceImpl.java:474)
	at com.emc.brs.sync.context.service.impl.ResilienceScheduleServiceImpl.examineSyncWindowGap(ResilienceScheduleServiceImpl.java:299)
	at com.emc.brs.sync.context.service.impl.ResilienceScheduleServiceImpl.retrySyncJobsInFailedCancelledOrPendingState(ResilienceScheduleServiceImpl.java:256)
	at com.emc.brs.sync.context.service.impl.ResilienceScheduleServiceImpl$ResilienceSyncRunnable.lambda$run$0(ResilienceScheduleServiceImpl.java:597)
	at java.base/java.lang.Iterable.forEach(Iterable.java:75)
	at com.emc.brs.sync.context.service.impl.ResilienceScheduleServiceImpl$ResilienceSyncRunnable.run(ResilienceScheduleServiceImpl.java:594)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: com.emc.brs.sync.api.operation.SyncOperationException: Unable to login to remoteHost <PPDMHostName> with the certificate .
	at com.emc.brs.sync.external.remote.impl.ServerRestClient.checkHttpStatus(ServerRestClient.java:567)
	at com.emc.brs.sync.external.remote.impl.ServerRestClient.credentialLogin(ServerRestClient.java:423)
	at com.emc.brs.sync.external.remote.impl.ServerRestClient.powerProtectLogin(ServerRestClient.java:332)
	at com.emc.brs.sync.external.remote.impl.ServerRestClient.lambda$getDestRestConnectionFromCache$1(ServerRestClient.java:283)
	at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4927)
	at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3571)
	at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2313)
	at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2190)
	at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2080)
	at com.google.common.cache.LocalCache.get(LocalCache.java:4012)
	at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4922)
	at com.emc.brs.sync.external.remote.impl.ServerRestClient.getDestRestConnectionFromCache(ServerRestClient.java:281)
	... 26 common frames omitted



YYYY-MM-DDTHH:MM:SSmssZ ERROR [] [Thread-1204] [][][][TRACE_ID:xxxxxxxxxxxxxxxx;JOB_ID:xxxxxxxxxxxxxxxx][] [c.e.b.s.o.s.i.UploadReplicaMetaDataServiceImpl.executeUpload(199)][199 ] - Failed to upload metadata files:
com.emc.brs.sync.api.operation.SyncOperationException: Unable to check the download status for file: sync.gz
at com.emc.brs.sync.operation.service.internal.UploadReplicaMetaDataServiceImpl

AAA 服務記錄 （aaa.log） 上，包含與其中報告的以下內容類似的項目：

YYYY-MM-DDTHH:MM:SSmssZ WARN [] [https-jsse-nio-9090-exec-4] [][][][TRACE_ID:a1c5180f2192d528][] [jakarta.persistence.spi.log(170)] - jakarta.persistence.spi::No valid providers found. 
YYYY-MM-DDTHH:MM:SSmssZ INFO [] [https-jsse-nio-9090-exec-4] [][][][TRACE_ID:a1c5180f2192d528][] [c.e.b.c.r.RestCommunicator.lambda$ensureResponse$10(376)] - HTTP: 400: "{\"error\":\"invalid_grant\",\"error_description\":\"Account is not fully set up\"}" 
YYYY-MM-DDTHH:MM:SSmssZ INFO [] [https-jsse-nio-9090-exec-20] [][][][TRACE_ID:91b599479f17cc42][] [c.e.b.c.r.RestCommunicator.lambda$ensureResponse$10(376)] - HTTP: 400: "{\"error\":\"invalid_grant\",\"error_description\":\"Account is not fully set up\"}"

變更用於同步作業的帳戶密碼時，會勾選「強制變更密碼」選項。因此，同步服務收到的 HTTP 回應是 400 而不是 200。

變更用於同步中繼資料的帳戶密碼時，請勿選取「強制密碼變更」選項。

若要解決此問題，請嘗試使用已用於同步中繼資料的登入資料登入 PowerProtect Data Manager 使用者介面。

系統應會提示使用者變更密碼。範例如下：

在新 密碼與 確認密碼欄位中，新增儲存在遠端 PowerProtect Data Manager 中的密碼。

此步驟中會提到遠端 PowerProtect Data Manager，因為這是嘗試連線至此伺服器並傳回 HTTP 400 回應的伺服器。

在 PowerProtect Data Manager 19.21 之後的未來版本中，記錄中的錯誤訊息將會受到強化，以協助使用者找出原因。