IDPA: ACM shows that local user password is out of sync. Please update the password
Summary: This KB covers how to resolve the "Data Protection Central local user password is out of sync. Please update the password," on ACM. When that error is due to a DNS resolution issue on ACM, and ACM not able to reach DPC. ...
Symptoms
ACM UI shows that "Data Protection Central local user password is out of sync. Please update the password."
In the /usr/local/dataprotection/var/configmgr/server_data/logs/server.log, there are errors like the following:
024-05-20 10:44:18,704 INFO [https-openssl-apr-8543-exec-1]-util.SSHUtil: Processing the ssh command execution standard error.
2024-05-20 10:44:20,456 INFO [https-openssl-apr-8543-exec-3]-util.SSHUtil: Processing the ssh command execution standard error.
2024-05-20 10:44:25,609 INFO [https-openssl-apr-8543-exec-3]-util.SSHUtil: Processing the ssh command execution standard error.
...
2024-05-20 10:44:58,292 INFO [Thread-430]-util.SSHUtil: Processing the ssh command execution standard error.
2024-05-20 10:44:58,388 ERROR [Thread-430]-util.RestUtil: Error occured while executing REST request. due to java.net.SocketException: Unexpected end of file from server
2024-05-20 10:44:58,388 ERROR [Thread-430]dpcadapter.DPCUtil: checkLocalUserOutOfSync-> DPC local user password is out of sync
at org.glassfish.jersey.internal.Errors.process(Errors.java:315) ~[jersey-common-2.22.2.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:297) ~[jersey-common-2.22.2.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:228) ~[jersey-common-2.22.2.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:315) ~[jersey-common-2.22.2.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:297) ~[jersey-common-2.22.2.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:228) ~[jersey-common-2.22.2.jar:?]
2024-05-20 10:44:58,424 INFO [Thread-427]-util.SSHUtil: Processing the ssh command execution standard error.
...
2024-05-20 10:44:58,358 INFO [Thread-430]-dpcadapter.DPCUtil: getDPCHostname : getDPCHostname --->
2024-05-20 10:44:58,359 INFO [Thread-430]-util.CommonUtil: hostname: XX.XXX.XXX.XXX ip: <hostname>
2024-05-20 10:44:58,359 INFO [Thread-430]-dpcadapter.DPCUtil: Getting DPC Hostname -<hostname>
2024-05-20 10:44:58,359 INFO [Thread-430]-util.RestUtil: Making REST call: https://<hostname>/elg/manage/info ,method: GET Meditype application/json
2024-05-20 10:44:58,388 ERROR [Thread-430]-util.RestUtil: Error occured while executing REST request. due to java.net.SocketException: Unexpected end of file from server
2024-05-20 10:44:58,388 ERROR [Thread-430]dpcadapter.DPCUtil: checkLocalUserOutOfSync-> DPC local user password is out of sync
com.emc.vcedpa.common.exception.ApplianceException: REST API execution failed.Not return expected response status.
at com.emc.vcedpa.common.util.RestUtil.executeRestAPI(RestUtil.java:173) ~[vcedpa-common-2.7.6.jar:?]
Check that the DNS server is configured. Run the following command:
cat /etc/resolv.conf
Run the following commands with the IP of the first "nameserver" listed in the above output:
ping <nameserver IP>
curl -kv <nameserver IP>:53
Check that ACM can resolve the DPC IP address to a hostname:
host -W 10 -T <DPC IP>
Where <DPC IP> is the IP of the DPC server.Cause
The host command does not return the correct FQDN for the DPC IP address. This shows that there is an issue with hostname resolution from the Customer environment (their external DNS) and that is why the rest call is failing.
Resolution
Name resolution by DNS is required for IDPA systems.
If DNS resolution is failing, have this issue fixed by customer network team.
Once DNS resolution is resolve, ACM can connect to DPC and this issue is resolved.