Skip to main content
NetApp Stage KB

AltaVault cannot resolve host name

Views:
Visibility:
Public
Votes:
0
Category:
altavault
Specialty:
DP
Last Updated:

Applies to

  • AltaVault 400
  • AltaVault 800
  • Virtual AltaVault

Issue

AltaVault  ran out of local space after the device was failing to connect to the cloud bucket

Feb 9 03:56:54 kdcntapava01 rfsd[7778]: [retry.INFO] (10288) retry 19 of meta xxx-xxxx-sg01 / megastore.guid after receiving 6: "Couldn't resolve host name", status=Could not resolve hostname
Feb 9 03:56:54 kdcntapava01 rfsd[7778]: [curl.INFO] (10288) HTTP request for https://xxxx.xxxx.org:18082/xxx-bkup-sg01/megastore.guid
Feb 9 03:56:54 kdcntapava01 rfsd[7778]: [curl.INFO] (10288) (03:56:54.704373): Hostname was NOT found in DNS cache
Feb 9 03:56:54 kdcntapava01 rfsd[7778]: [curl.INFO] (10288) (03:56:54.708447): Could not resolve host: vchsgn.healthbc.org
Feb 9 03:56:54 kdcntapava01 rfsd[7778]: [curl.INFO] (10288) (03:56:54.708453): Closing connection 5
Feb 9 03:56:54 kdcntapava01 rfsd[7778]: [retry.ERR] (10288) failing meta xxx-xxx-sg01 / megastore.guid after 20 retries
Feb 9 03:56:54 kdcntapava01 rfsd[7778]: [megastore_guid.ERR] (10288) Cloud connection check failed: Could not resolve hostname

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
5ccec07a-8df4-4ba3-b16c-ac458e80b197