Discussions specific to the VMware vSphere hypervisor
Post Reply
scottmlew
Influencer
Posts: 18
Liked: 3 times
Joined: Jun 09, 2009 5:26 pm
Full Name: scottmlew
Contact:

Soap fault, Temporary failure in name resolution

Post by scottmlew »

I'm seeing the error "Soap fault. Temporary failure in name resolution" (full detail below). This is happening on 1 of 2 machines in a backup job. Curiously, when I first ran the job, I had forgotten to setup a proxy on one of the hypervisors. So I canceled the job, deployed the proxy, and I'm seeing the error ever since, but only on the VM for which I added the proxy. I found a bunch of forum posts about this error from a long time ago, but nothing recently. I've checked/tried everything in those posts with no success. DNS resolves fine, I rescanned storage, deleted and readded the VM from the job, etc. Any thoughts?

Code: Select all

[02.05.2020 21:07:53] <38> Info     Description: "
[02.05.2020 21:07:53] <38> Info         [Soap] Connection 'vcenter.corp.foobar.com:443:administrator@corp.foobar.com:False::0:38' is disposing.
[02.05.2020 21:07:53] <38> Error    Getting VM info from vSphere
[02.05.2020 21:07:53] <38> Error    Cannot get service content. (Veeam.Backup.Common.CCppComponentException)
[02.05.2020 21:07:53] <38> Error    Soap fault. Temporary failure in name resolutionDetail: 'getaddrinfo failed in tcp_connect()', endpoint: 'https://vcenter.corp.foobar.com:443/sdk' (Veeam.Backup.Common.CCppComponentException)
[02.05.2020 21:07:53] <38> Error    SOAP connection is not available. Connection ID: [vcenter.corp.foobar.com]. (Veeam.Backup.Common.CCppComponentException)
[02.05.2020 21:07:53] <38> Error    Failed to create NFC download stream. NFC path: [nfc://conn:vcenter.corp.foobar.com,nfchost:host-96,stg:datastore-108@mbox1/mbox1.vmx]. (Veeam.Backup.Common.CCppComponentException)
[02.05.2020 21:07:53] <38> Error       in c++: Unable to open source file [nfc://conn:vcenter.corp.foobar.com,nfchost:host-96,stg:datastore-108@mbox1/mbox1.vmx].
[02.05.2020 21:07:53] <38> Error       in c++: Failed to copy local file. Source: [nfc://conn:vcenter.corp.foobar.com,nfchost:host-96,stg:datastore-108@mbox1/mbox1.vmx]. Target: [MemFs://GetRemoteFileText_{d4795084-7818-456a-94d5-77ce88b8e00b}].
[02.05.2020 21:07:53] <38> Error       in c++: Unable to get content of the file. File path: [nfc://conn:vcenter.corp.foobar.com,nfchost:host-96,stg:datastore-108@mbox1/mbox1.vmx].
[02.05.2020 21:07:53] <38> Error       in c++: Client failed to process the command. Command: [file2text].
[02.05.2020 21:07:53] <38> Error       in c++ event: ClientErrorEvt
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.AgentProvider.CClientAgentProtocol.WaitUntilWorking(Int32 timeout)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.AgentProvider.CClientAgentProtocol.DoAgentCommand(String command, String logCommand, Boolean doWait, Nullable`1 outputLogLevel)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.AgentProvider.CClientAgentProtocol.File2Text(String filename, Int64 size)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.AgentProvider.CBackupClient.File2Text(String filename, Int64 size)
[02.05.2020 21:07:53] <38> Error    --- End of stack trace from previous location where exception was thrown ---
[02.05.2020 21:07:53] <38> Error       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.Common.ExceptionFactory.ThrowNecessaryAggregateException(IEnumerable`1 exceptionsCollection)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.AgentProvider.CBackupClientImpl.ConstructException(Exception exception, String error)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.AgentProvider.CBackupClient.ConstructException(Exception ex, String error, Object[] args)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.AgentProvider.CBackupClient.File2Text(String filename, Int64 size)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.Core.CViVmSource.Prepare(ITaskTarget target)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.Core.CViBackupJobPerformer.PrepareSource(IViTaskSource taskSource, IBackupTaskTarget taskTarget, CBackupTaskSession taskSess)
[02.05.2020 21:07:53] <38> Error       at Veeam.Backup.Core.CViBackupJobPerformer.ExecuteTask(IVmBackupTask task, CViJobSource jobSource, CBackupJobTarget jobTarget)

Egor Yakovlev
Veeam Software
Posts: 1785
Liked: 406 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Contact:

Re: Soap fault, Temporary failure in name resolution

Post by Egor Yakovlev »

- In most of the cases NFC errors are caused by "Ports-Permissions-DNS" settings. Please check out KB1198 and go through troubleshooting steps(yes, even confirmed DNS - double check wouldn't hurt). Make sure to check Proxy for DNS too - sometimes people do ping from VBR and get over with it, however all backup components must resolve each other's names.
- In some cases Storage vMotion solves this kind of error.
- last but not least, feel free to open a Support Ticket to be guided by our engineer.
/Thanks!

soncscy
Expert
Posts: 259
Liked: 110 times
Joined: Aug 04, 2019 2:57 pm
Full Name: Harvey Carel
Contact:

Re: Soap fault, Temporary failure in name resolution

Post by soncscy »

Hey Scott,

I'm 99.9% sure that message is straight from vCenter itself:

https://kb.vmware.com/s/article/56944

Do you have PSCA's set up?

I think personally I'd look internally, and as I've dealt with Veeam+Vmware in tons of cases and just that kind of wording sounds more like a VMware thing not a Veeam thing.

Check your VMware environment regardless of the PSCAs and check around in the VMware logs -- I'm 99.9% sure if you grep that message across your VCSA/PSCAs, you'll find it there.

scottmlew
Influencer
Posts: 18
Liked: 3 times
Joined: Jun 09, 2009 5:26 pm
Full Name: scottmlew
Contact:

Re: Soap fault, Temporary failure in name resolution

Post by scottmlew » 1 person likes this post

No PSCAs setup. I had found that KB article earlier, but I double checked everything again this morning with fresh eyes. All looks good, but still saw the problem. I rebooted the proxy (Ubuntu 18) and now all is working as expected. I will keep an eye on it and report back if there is a recurrence.

PetrM
Veeam Software
Posts: 932
Liked: 133 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Soap fault, Temporary failure in name resolution

Post by PetrM »

Hi Scott,

I would pay attention to this line from log file if the same issue was reproduced:

Code: Select all

Temporary failure in name resolutionDetail: 'getaddrinfo failed in tcp_connect()', endpoint: 'https://vcenter.corp.foobar.com:443/sdk' 
Please always include support case id when you create a new topic for technical issue, our possibility to troubleshoot issues via forum is quite limited.

Thanks!

Post Reply

Who is online

Users browsing this forum: No registered users and 15 guests