AltaVault 无法解析主机名

最后更新
另存为PDF

Views:: 11

Visibility:: Public

Votes:: 0

Category:: altavault<a>AltaVault</a><a>DNS</a><a>AltaVault 虚拟设备</a>

Specialty:: dp

Last Updated:

适用场景

AltaVault 400
AltaVault 800
虚拟 AltaVault

问题描述

在设备无法连接到云分段后， AltaVault 用尽本地空间

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