171.67.108.200/204 [You MUST report a different server.]

[PS3EdOlkkola]

Same issue for the past 5 hours. Client stopped, exit, restart, same issue:
Seems to be isolated to only rigs running AMD GPUs

Code: Select all

01:05:50:WU00:FS01:Connecting to 171.67.108.200:80
01:05:50:WU01:FS02:Connecting to 171.67.108.200:80
01:05:53:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
01:05:53:WU00:FS01:Connecting to 171.67.108.204:80
01:05:53:WARNING:WU01:FS02:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
01:05:53:WU01:FS02:Connecting to 171.67.108.204:80
01:05:54:WARNING:WU01:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
01:05:54:ERROR:WU01:FS02:Exception: Could not get an assignment
01:05:54:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
01:05:54:ERROR:WU00:FS01:Exception: Could not get an assignment

Code: Select all

*********************** Log Started 2015-03-27T01:04:36Z ***********************
01:04:36:************************* Folding@home Client *************************
01:04:36:      Website: http://folding.stanford.edu/
01:04:36:    Copyright: (c) 2009-2014 Stanford University
01:04:36:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
01:04:36:         Args: --open-web-control
01:04:36:       Config: C:/Users/Ed/AppData/Roaming/FAHClient/config.xml
01:04:36:******************************** Build ********************************
01:04:36:      Version: 7.4.4
01:04:36:         Date: Mar 4 2014
01:04:36:         Time: 20:26:54
01:04:36:      SVN Rev: 4130
01:04:36:       Branch: fah/trunk/client
01:04:36:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
01:04:36:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
01:04:36:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
01:04:36:     Platform: win32 XP
01:04:36:         Bits: 32
01:04:36:         Mode: Release
01:04:36:******************************* System ********************************
01:04:36:          CPU: AMD FX(tm)-8350 Eight-Core Processor
01:04:36:       CPU ID: AuthenticAMD Family 21 Model 2 Stepping 0
01:04:36:         CPUs: 8
01:04:36:       Memory: 32.00GiB
01:04:36:  Free Memory: 28.62GiB
01:04:36:      Threads: WINDOWS_THREADS
01:04:36:   OS Version: 6.1
01:04:36:  Has Battery: false
01:04:36:   On Battery: false
01:04:36:   UTC Offset: -5
01:04:36:          PID: 5728
01:04:36:          CWD: C:/Users/Ed/AppData/Roaming/FAHClient
01:04:36:           OS: Windows 7 Ultimate
01:04:36:      OS Arch: AMD64
01:04:36:         GPUs: 2
01:04:36:        GPU 0: ATI:5 Vesuvius []
01:04:36:        GPU 1: ATI:5 Vesuvius []
01:04:36:         CUDA: Not detected
01:04:36:Win32 Service: false

[bruce]

As I've explained elsewhere, 171.67.108.200 never has any WUs to distribute, it's an assignment server, not a work server. It's doing it's job trying to find a Work Server that has WUs that you can process but there currently are none.

Search back in your log for the IPs of Work servers to/from which WUs were uploaded/download for your system. Examine the status of THOSE servers.

See also (Do This First)

It looks like the messages have improved.

Code: Select all

00:14:42:WU01:FS01:Connecting to 171.67.108.200:80
00:14:43:WU01:FS01:Assigned to work server 171.64.65.56
00:14:43:WU01:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:GM206 [GeForce GTX 960] from 171.64.65.56
00:14:43:WU01:FS01:Connecting to 171.64.65.56:8080
00:14:43:ERROR:WU01:FS01:Exception: Server did not assign work unit
00:14:43:WU01:FS01:Connecting to 171.67.108.200:80
00:14:43:WU01:FS01:Assigned to work server 140.163.4.234
00:14:43:WU01:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:GM206 [GeForce GTX 960] from 140.163.4.234
00:14:43:WU01:FS01:Connecting to 140.163.4.234:8080
00:14:44:WU01:FS01:Downloading 2.31MiB

In this case, the AS 171.67.108.200 had more than one choice. 171.64.65.56 failed to assign work unit so the second choice, work server 140.163.4.234 was assigned and it succeeded.

Conceivably, if 140.163.4.234 happened to be off-line, the AS wouldn't be able to assign you to either one and you'd need to report a potential problem with 171.64.65.56. If 171.64.65.56 had also been off-line, 171.67.108.200 wouldn't be able to direct you to either one so you'd have to find the IP addresses servers from your logged history for that slot.


Topic closed (again).

[LonePalm]

16:57:35:WU00:FS00:Connecting to 171.67.108.200:80
16:57:36:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
16:57:36:WU00:FS00:Connecting to 171.67.108.204:80
16:57:37:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:57:37:ERROR:WU00:FS00:Exception: Could not get an assignment
16:59:13:WU00:FS00:Connecting to 171.67.108.200:80
16:59:14:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
16:59:14:WU00:FS00:Connecting to 171.67.108.204:80
16:59:15:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment

[LonePalm]

Please ignore this. While I was posting, the server was refilled.

[Joe_H]

In the future please check for the existing topic. As explained here 171.67.108.200 and 171.67.108.204 are Assignment Servers. Without any information on which servers your system normally gets work from we can not determine which Work Servers might be out of work.

(Topic remains closed)

[bruce]

Please ignore this. While I was posting, the server was refilled.

Check your logs. The server 171.67.108.204 was NOT refilled. Some other server supplied your WU, not the one you reported.