AltaVault cannot resolve host name

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 125

Visibility:: Public

Votes:: 0

Category:: altavault

Specialty:: legacy

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