Exception: Could not get IP address for assign1.foldingathome.org

Moderators: Site Moderators, FAHC Science Team

Post Reply
rjhorn3
Posts: 7
Joined: Tue Sep 20, 2016 10:37 am

Exception: Could not get IP address for assign1.foldingathome.org

Post by rjhorn3 »

I've found a workaround but this description may help find the real bug so that it can be fixed.

After a software upgrade on another system I started having this problem. When I started FAHClient using a proxy I got many variations on this error message:

ERROR:WU01:FS01:Exception: Could not get IP address for assign4.foldingathome.org Could not get IP address for assign1.foldingathome.org: The requested name is valid, but no data of the requested type was found.

At the same time "ping assign1.foldingathome.org" was resolving the IP address and nslookup was resolving the IP address. Only FAHClient was having a problem.

Resolution/workaround: The client system is a Windows 10 system connected to an internal network that has an HTTP proxy, but no gateway or other connection to the outside. When I configured the Windows 10 system to have a gateway, giving a bogus address of a real computer that is not a gateway, the problem went away.

Since the other programs like ping and nslookup were resolving IP addresses properly that indicates that the problem is something inside FAHClient.

Code: Select all

00:34:29:******************************* libFAH ********************************
00:34:29:           Date: Oct 20 2020
00:34:29:           Time: 13:36:55
00:34:29:       Revision: 5ca109d295a6245e2a2f590b3d0085ad5e567aeb
00:34:29:         Branch: master
00:34:29:       Compiler: Visual C++ 2015
00:34:29:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
00:34:29:       Platform: win32 10
00:34:29:           Bits: 32
00:34:29:           Mode: Release
00:34:29:****************************** FAHClient ******************************
00:34:29:        Version: 7.6.21
00:34:29:         Author: Joseph Coffland <joseph@cauldrondevelopment.com>
00:34:29:      Copyright: 2020 foldingathome.org
00:34:29:       Homepage: https://foldingathome.org/
00:34:29:           Date: Oct 20 2020
00:34:29:           Time: 13:41:04
00:34:29:       Revision: 6efbf0e138e22d3963e6a291f78dcb9c6422a278
00:34:29:         Branch: master
00:34:29:       Compiler: Visual C++ 2015
00:34:29:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
00:34:29:       Platform: win32 10
00:34:29:           Bits: 32
00:34:29:           Mode: Release
00:34:29:           Args: --proxy-enable=true --proxy=192.168.xxx.xxx:yyyy
00:34:29:         Config: C:\Users\hornrj\FAHClient\config.xml
00:34:29:******************************** CBang ********************************
00:34:29:           Date: Oct 20 2020
00:34:29:           Time: 11:36:18
00:34:29:       Revision: 7e4ce85225d7eaeb775e87c31740181ca603de60
00:34:29:         Branch: master
00:34:29:       Compiler: Visual C++ 2015
00:34:29:        Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
00:34:29:       Platform: win32 10
00:34:29:           Bits: 32
00:34:29:           Mode: Release
00:34:29:******************************* System ********************************
00:34:29:            CPU: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz
00:34:29:         CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
00:34:29:           CPUs: 4
00:34:29:         Memory: 7.98GiB
00:34:29:    Free Memory: 5.51GiB
00:34:29:        Threads: WINDOWS_THREADS
00:34:29:     OS Version: 6.2
00:34:29:    Has Battery: false
00:34:29:     On Battery: false
00:34:29:     UTC Offset: -4
00:34:29:            PID: 10132
00:34:29:            CWD: C:\Users\xxxxxxxxx
00:34:29:  Win32 Service: false
00:34:29:             OS: Windows 10 Enterprise
00:34:29:        OS Arch: AMD64
00:34:29:           GPUs: 1
00:34:29:          GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:5 GP108 [GeForce GT 1030]
00:34:29:  CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:11.3
00:34:29:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:3.0 Driver:466.11
00:34:29:***********************************************************************
00:34:29:<config>
00:34:29:  <!-- User Information -->
00:34:29:  <passkey v='*****'/>
00:34:29:  <user v='xxxxxx'/>
00:34:29:
00:34:29:  <!-- Folding Slots -->
00:34:29:  <slot id='0' type='CPU'/>
00:34:29:  <slot id='1' type='GPU'>
00:34:29:    <pci-bus v='1'/>
00:34:29:    <pci-slot v='0'/>
00:34:29:  </slot>
00:34:29:</config>
Last edited by Joe_H on Sat Jul 09, 2022 2:02 am, edited 1 time in total.
Reason: added code tags to log
Joe_H
Site Admin
Posts: 7856
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: Exception: Could not get IP address for assign1.foldingathome.org

Post by Joe_H »

The client has limited support for proxies as it is. Did the type of proxy change to an unsupported one?

You can submit a bug report, but it won't be fixed in this version of the client. They are in the process of doing a total rewrite, Version 8 should come out at some point in the future.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
rjhorn3
Posts: 7
Joined: Tue Sep 20, 2016 10:37 am

Re: Exception: Could not get IP address for assign1.foldingathome.org

Post by rjhorn3 »

The proxy was not changed at all. The change was in the DHCP setup on the network. Rather than provide an address for a non-existant gateway, it stopped providing a gateway address. That appears to be the source of the problem. When I changed the configuration to provide a gateway address for the subnet the problem went away. The machine that I pointed to as a gateway has IP routing disabled and black holes any attempt to relay packets. From the log on that machine it appears that FAHClient did not attempt to use the gateway, it just needed an address of a real machine on the network.

As a guess, the DNS resolution code inside FAHClient is checking for a valid gateway address before it checks whether it should use a proxy.

Security considerations prohibit IP routing for this subnet. 100% of all external traffic (including DNS) goes through proxies that log all attempts and only permit traffic to approved destinations. The DNS logs indicated that the FAHClient was requesting and getting DNS resolutions for the assignment machines. So the error message was misleading. DNS did provide an IP address, but the lack of a gateway cause the IP address error.
Post Reply