No such host is known

Moderators: Site Moderators, FAHC Science Team

Post Reply
SPAS-ID
Posts: 2
Joined: Tue May 17, 2016 8:25 pm

No such host is known

Post by SPAS-ID »

GPU isn't running, i checked the log and it says

20:24:51:WARNING:Attempting to update GPUs.txt from assign-GPU.stanford.edu:80: Could not get IP address for assign-GPU.stanford.edu: No such host is known.
20:24:51:Connecting to assign-GPU2.stanford.edu:80
20:25:00:WARNING:Attempting to update GPUs.txt from assign-GPU2.stanford.edu:80: Could not get IP address for assign-GPU2.stanford.edu: No such host is known.
20:25:02:WU00:FS00:0xa4:Completed 350000 out of 5000000 steps (7%)
20:27:45:WU00:FS00:0xa4:Completed 400000 out of 5000000 steps (8%)
20:29:41:Connecting to assign-GPU.stanford.edu:80
20:29:41:WARNING:Attempting to update GPUs.txt from assign-GPU.stanford.edu:80: Could not get IP address for assign-GPU.stanford.edu: No such host is known.
20:29:41:Connecting to assign-GPU2.stanford.edu:80
20:29:41:WARNING:Attempting to update GPUs.txt from assign-GPU2.stanford.edu:80: Could not get IP address for assign-GPU2.stanford.edu: No such host is known.
20:30:26:WU00:FS00:0xa4:Completed 450000 out of 5000000 steps (9%)

so is there any solution ? Windows Firewall allowed FAHClient
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: No such host is known

Post by bruce »

From the Windows Command Prompt, you can easily confirm whether your ISP's DNS server recognizes the host:

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Nikki>ping assign-GPU.stanford.edu

Pinging vsp11.stanford.edu [171.67.108.45] with 32 bytes of data:
Reply from 171.67.108.45: bytes=32 time=73ms TTL=49
Reply from 171.67.108.45: bytes=32 time=73ms TTL=49
Reply from 171.67.108.45: bytes=32 time=73ms TTL=49
Reply from 171.67.108.45: bytes=32 time=73ms TTL=49

Ping statistics for 171.67.108.45:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 73ms, Maximum = 73ms, Average = 73ms
The message suggests that the problem is either in DNS or perhaps in your security software. (FAH makes use of those services provided by your OS)
Post Reply