Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
Nutanix Backup Proxy deployment failure with error "Error occurred while reading cluster credentials”
Nutanix Backup Proxy deployment failure with error "Error occurred while reading cluster credentials”
Updated over 3 months ago

Problem description

While deploying the Druva Hybrid Backup Proxy to connect to Prism Element, the deployment would get failed.

Cause

Ubuntu 18.x and 20.x are unable to resolve domain names ending in ".local".

Traceback

When you review the deployment log, you would find below error message.
/var/log/Phoenix/AHV/

proxy_deployment.log:

level=error ts=XXXXXXXXX= Command=deploy Stage=Activation Message="Error occurred while reading cluster credentials: error reading cluster credential file: open /etc/Phoenix/AHV/.cluster_credentials: no such file or directory\r\n" Error="PhoenixAHVActivate command execution failed: Process exited with status 1"
level=error ts=XXXXXXXX5074382Z Command=deploy Status=failure Error="PhoenixAHVActivate command execution failed: Process exited with status 1" RetryStage=
level=info ts=2022-10-31T06:14:48.371525Z Command=validate-credentials Message="Validating prism credentials"
level=error ts=2022-10-31T06:14:52.6695255Z Command=deploy Stage=Activation Message="Error occurred while reading cluster credentials: error reading cluster credential file: open /etc/Phoenix/AHV/.cluster_credentials: no such file or directory\r\n" Error="PhoenixAHVActivate command execution failed: Process exited with status 1"

Resolution

Step 1:

  • Verify the communication between the proxy server and the Nutanix Cluster IP or FQDN by pinging the Cluster IP/FQDN from the proxy server.

  • If the communication is successful, retry the backup proxy activation.

  • If activation continues to fail, proceed to step 2.

Step2 :

  • On the proxy server Run this command to edit resolved.conf:

    sudo nano /etc/systemd/resolved.conf

  • Change the line "#domains=" to "domains=<yourinternaldomain.local>"

  • Change the line "#DNS=" to "DNS=<IP address of DNS server 1> <IP address of DNS server 2 "

  • Then run this command to restart DNS client: service systemd-resolved restart

Did this answer your question?