gpu WUs not assigning from 171.67.108.201:80

Moderators: Site Moderators, FAHC Science Team

fab@fold
Posts: 14
Joined: Mon Apr 14, 2014 5:49 pm

Re: gpu WUs not assigning from 171.67.108.201:80

Post by fab@fold »

thx, already done that... booted the pc and the modem... i point out that at the beginning of the problems, 2 days ago, only the gpu download was halted, the cpu was successfully donwloading... after i reinstall the client yesterday (AFTER the successuff cpu wu download in the log), also the cpu got stuck... other clients like boing are working ok, last try of yesterday was joining a new boinc project, and the client correctly downloaded both the program EXE and some WUssss... it appears that only the f@h client is affected by this problem...
P5-133XL
Posts: 2948
Joined: Sun Dec 02, 2007 4:36 am
Hardware configuration: Machine #1:

Intel Q9450; 2x2GB=8GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460; Windows Server 2008 X64 (SP1).

Machine #2:

Intel Q6600; 2x2GB=4GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460 video card; Windows 7 X64.

Machine 3:

Dell Dimension 8400, 3.2GHz P4 4x512GB Ram, Video card GTX 460, Windows 7 X32

I am currently folding just on the 5x GTX 460's for aprox. 70K PPD
Location: Salem. OR USA

Re: gpu WUs not assigning from 171.67.108.201:80

Post by P5-133XL »

I'd check your AV programs again to find if any of them are blocking the folding client or cores
Image
fab@fold
Posts: 14
Joined: Mon Apr 14, 2014 5:49 pm

Re: gpu WUs not assigning from 171.67.108.201:80

Post by fab@fold »

all AV programs are disabled in main PC... and the other PC in my home network, that shows the same behaviuor, does not even have an AV installed....
7im
Posts: 10189
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: gpu WUs not assigning from 171.67.108.201:80

Post by 7im »

AV software doesn't always disable itself fully. You might try booting to safe mode with networking.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
fab@fold
Posts: 14
Joined: Mon Apr 14, 2014 5:49 pm

Re: gpu WUs not assigning from 171.67.108.201:80

Post by fab@fold »

done..rebooted in safe mode with networking... i checked that internet connection was working, all ok, but folding client had the same problem... no wu download..
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: gpu WUs not assigning from 171.67.108.201:80

Post by bruce »

davidcoton wrote:

Code: Select all

16:25:13:  <!-- Folding Slots -->
16:25:13:  <slot id='0' type='CPU'/>
16:25:13:  <slot id='1' type='GPU'/>
16:25:13:</config>
16:25:13:Set client configured
16:25:13:WU00:FS00:Connecting to 171.67.108.200:8080
16:25:13:WU01:FS01:Connecting to 171.67.108.200:8080
16:25:14:WU00:FS00:Connecting to 171.67.108.200:8080
16:25:14:WU01:FS01:Connecting to 171.67.108.201:80
16:25:14:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': 10002: Received short response, expected 272 bytes, got 0
16:25:14:WU01:FS01:Connecting to 171.64.65.160:80
Question for the gurus: Why is FS01 (GPU?) trying to connect to the Classic AS on 171.67.108.200:8080 ? But the port 80 attempt looks better.

David
That cannot be explained unless the wrong IP is being provided by a DNS lookup.

A GPU slot should start with 171.67.108.201 or 171.64.65.160 on port 8080 and if that one fails, try the other one on port 80.
fab@fold
Posts: 14
Joined: Mon Apr 14, 2014 5:49 pm

Re: gpu WUs not assigning from 171.67.108.201:80

Post by fab@fold »

thx Bruce, after all the verifictions i'm also brought to think that there's a problem with my ISP (that, by the way, is italian's largest......) tonight i will try changing my DNS primary server from 192.168.1.1 to a public DNS lookup server and see how it goes....... can someone tell my the details about a test (tracert ?) that i could perform, i.e. what is the expected routing of ip address to expect when tracing (what address ?) ?
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: gpu WUs not assigning from 171.67.108.201:80

Post by bruce »

The primary GPU assignment server has multiple aliases and I'm not sure which one is used inside FAHClient. The most obvious one is vsp10v-vz01.stanford.edu. If that one works correctly and the client is using a different one that is misdirected, I can't help you at this moment.
fab@fold
Posts: 14
Joined: Mon Apr 14, 2014 5:49 pm

Re: gpu WUs not assigning from 171.67.108.201:80

Post by fab@fold »

nope, i tried 2 different dns servers, dind't work.. i have ruled out everything i could on my side... maybe i'll try again in the future.. thx everyone for their efforts,
Fab
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: gpu WUs not assigning from 171.67.108.201:80

Post by bruce »

Code: Select all

C:\Users\bruce>ping vsp10v-vz01.stanford.edu

Pinging vsp10v-vz01.stanford.edu [171.67.108.201] with 32 bytes of data:
Reply from 171.67.108.201: bytes=32 time=19ms TTL=50
Reply from 171.67.108.201: bytes=32 time=19ms TTL=50
Reply from 171.67.108.201: bytes=32 time=19ms TTL=50
Reply from 171.67.108.201: bytes=32 time=18ms TTL=50

Ping statistics for 171.67.108.201:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 19ms, Average = 18ms
fab@fold
Posts: 14
Joined: Mon Apr 14, 2014 5:49 pm

Re: gpu WUs not assigning from 171.67.108.201:80

Post by fab@fold »

same here....

Esecuzione di Ping vsp10v-vz01.stanford.edu [171.67.108.201] con 32 byte di dati:
Risposta da 171.67.108.201: byte=32 durata=238ms TTL=47
Risposta da 171.67.108.201: byte=32 durata=216ms TTL=47
Risposta da 171.67.108.201: byte=32 durata=216ms TTL=47
Risposta da 171.67.108.201: byte=32 durata=224ms TTL=47

Statistiche Ping per 171.67.108.201:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 216ms, Massimo = 238ms, Medio = 223ms
fab@fold
Posts: 14
Joined: Mon Apr 14, 2014 5:49 pm

Re: gpu WUs not assigning from 171.67.108.201:80

Post by fab@fold »

somehow i managed to better the situation... i fired up an image of my s.o. of a week ago, with an installed working version of the client... when it re-finished to cpu wu, it got stuck in updating the a3 core... here's what it says in the log :

Code: Select all

15:03:40:WU00:FS00:Downloading core from http://www.stanford.edu/~pande/Win32/AMD64/Core_a3.fah
15:03:40:WU00:FS00:Connecting to www.stanford.edu:80
15:03:40:ERROR:WU00:FS00:Exception: Failed to read stream

then i get this one, don't know what it means, i have a r9 280x gpu :

Code: Select all

15:04:46:WU01:FS01:0x17:Completed 4625000 out of 5000000 steps (92%)
15:04:46:WU01:FS01:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: gpu WUs not assigning from 171.67.108.201:80

Post by PantherX »

For the CPU (FS00) error message, I have seen this error due to:
1) Incorrect permissions to run the application
2) Security application detecting it as a threat and causing issues
3) Can't write to the save location (path where F@H works from)
4) Insufficient disk space

Regarding the GPU (FS01) message, that is a temperature control feature but it only works on a single Nvidia GPU system. You can safely ignore it and your GPU should function normally.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
muckelpupp
Posts: 6
Joined: Fri Oct 29, 2010 8:30 am

Re: gpu WUs not assigning from 171.67.108.201:80

Post by muckelpupp »

Hi there!

I am pushing this topic, as I too, seem to have a connectivity issue with this specific server that has been going on for a couple of hours now.
Also I read through all the steps and hints at what to do first, as well as the suggestions already posted here in this thread. So long nothing did work out and my GPU keeps getting error messages.

Code: Select all

*********************** Log Started 2014-05-26T09:09:38Z ***********************
09:10:04:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:10:07:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:10:07:ERROR:WU01:FS01:Exception: Could not get an assignment
09:10:28:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:10:29:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:10:29:ERROR:WU01:FS01:Exception: Could not get an assignment
09:11:29:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:11:30:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:11:30:ERROR:WU01:FS01:Exception: Could not get an assignment
09:13:06:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:13:18:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:13:18:ERROR:WU01:FS01:Exception: Could not get an assignment
09:15:43:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:15:43:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:15:43:ERROR:WU01:FS01:Exception: Could not get an assignment
09:19:57:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:19:59:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:19:59:ERROR:WU01:FS01:Exception: Could not get an assignment
09:26:49:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:26:49:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:26:49:ERROR:WU01:FS01:Exception: Could not get an assignment
09:37:54:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Failed to connect to 171.67.108.201:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
09:37:55:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
09:37:55:ERROR:WU01:FS01:Exception: Could not get an assignment
I know that the servers are up and running and seemingly without problems (http://fah-web.stanford.edu/pybeta/serverstat.html). Strange thing, that I am able to ping/tracert just this one: 171.64.65.160
171.67.108.201 can not be even ping'ed.

So if it is an issue on my side, I would not know where to look. There is no AV blocking, there has not been a change to the system (hard or software), and it has been working fine for almost three weeks now.
Any help is greatly appreciated! Thank you very much!

Mod Edit: Changed Quote Tags To Code Tags - PantherX
Image

Image
P5-133XL
Posts: 2948
Joined: Sun Dec 02, 2007 4:36 am
Hardware configuration: Machine #1:

Intel Q9450; 2x2GB=8GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460; Windows Server 2008 X64 (SP1).

Machine #2:

Intel Q6600; 2x2GB=4GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460 video card; Windows 7 X64.

Machine 3:

Dell Dimension 8400, 3.2GHz P4 4x512GB Ram, Video card GTX 460, Windows 7 X32

I am currently folding just on the 5x GTX 460's for aprox. 70K PPD
Location: Salem. OR USA

Re: gpu WUs not assigning from 171.67.108.201:80

Post by P5-133XL »

I've contacted PG about it. According to the server page, the servers have no work, nor should anything be being assigned to them.

Do note that today is a national holiday (Memorial day) so their staff may be limited.
Image
Post Reply