Page 2 of 3

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 3:01 am
by jcoffland
Should be fixed now.

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 3:07 am
by bollix47
Confirmed ... after a pause / fold sequence my Maxwell did receive a P9201.

Thank you.

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 3:18 am
by Joe_H
jimerickson wrote:even after a pause and restart my 980's are still pointed firmly at 171.67.108.200 and 171.67.108.204. wonder whats up...
Those are the assignment servers, they are not seeing a WS with suitable WU's to connect you with.

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 3:24 am
by SpockLogic
Seems the problem could be widespread. I have 2 Macs, an 8 core MacPro and a 4 core i7 both waiting for work.

This is from the MacPro

Code: Select all

Empty work server assignment
02:53:38:WU00:FS01:Connecting to 171.67.108.204:80
02:53:39:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.204:80':
I've tried restarting to no avail.

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 3:25 am
by Buck Nasty
Agreed. My Linux GPU's have picked up some work after sitting idle. Thanks!

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 3:35 am
by ChristianVirtual
Just also back now ... Receive two new 9201 on GTX 970 under CentOS

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 3:53 am
by jimerickson
indeed. resolved. i now have work for all 980's. thanks much guys!!

Re: 171.67.108.200:80

Posted: Thu Jan 08, 2015 4:01 am
by bruce
jimerickson wrote:even after a pause and restart my 980's are still pointed firmly at 171.67.108.200 and 171.67.108.204. wonder whats up...
And that's the way it should be. See my explanation at Empty work server assignment

Assignment Servers (at 171.67.108.200 and 171.67.108.204) have always been responsible for finding a suitable Work Server, which in turn is then responsible for assigning WUs. Assignment servers never distribute WUs, work servers do. Problems arise when Work Servers don't have any WUs to distribute.

Serverstat does not show Assignment Servers, only Work Servers.

Note: the Assignment Servers have since been added to Serverstat

Re: 171.67.108.200:80

Posted: Tue Mar 17, 2015 2:18 pm
by PS3EdOlkkola
Looks like this server is either down or is empty, or both:

Code: Select all

14:12:11:FS02:Unpaused
14:12:11:WU02:FS02:Connecting to 171.67.108.200:80
14:12:12:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
14:12:12:WU02:FS02:Connecting to 171.67.108.204:80
14:12:12:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
14:12:12:ERROR:WU02:FS02:Exception: Could not get an assignment
14:12:12:WU02:FS02:Connecting to 171.67.108.200:80
14:12:13:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
14:12:13:WU02:FS02:Connecting to 171.67.108.204:80
14:12:13:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
14:12:13:ERROR:WU02:FS02:Exception: Could not get an assignment
14:13:13:WU02:FS02:Connecting to 171.67.108.200:80
14:13:13:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
14:13:13:WU02:FS02:Connecting to 171.67.108.204:80
14:13:14:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
14:13:14:ERROR:WU02:FS02:Exception: Could not get an assignment
14:14:50:WU02:FS02:Connecting to 171.67.108.200:80
14:14:50:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
14:14:50:WU02:FS02:Connecting to 171.67.108.204:80
14:14:51:WARNING:WU02:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
14:14:51:ERROR:WU02:FS02:Exception: Could not get an assignment

Code: Select all

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

Re: 171.67.108.200:80

Posted: Tue Mar 17, 2015 2:19 pm
by PS3EdOlkkola
Seems to be back online now.

Re: 171.67.108.200:80

Posted: Tue Mar 17, 2015 4:14 pm
by Joe_H
PS3EdOlkkola wrote:Looks like this server is either down or is empty, or both:
This server is an Assignment Server. So it would not be down or empty. What those messages mean is that the AS could not find a WS with work appropriate for the configuration and system requesting a new WU. Please read Bruce's linked posting in the one just before yours.

Re: 171.67.108.200:80

Posted: Tue Mar 17, 2015 4:23 pm
by bruce
PS3EdOlkkola wrote:Looks like this server is either down or is empty, or both:
Apparently you didn't understand my previous post.

The Assignment Servers are doing their job, as far as possible. At times, that job cannot be completed. This message does NOT indicate a problem with either 171.57.108.200 or with 171.67.108.204 but rather a global problem for the type of WUs your system is requesting.

* The message "Could not get an assignment" is coming from one of the Assignment Servers, so that server is not down.
* Assignment Servers are ALWAYS empty. They do not distribute WUs.
* Their sole job is to assign you to a Work Server that has does have WUs that can be distributed to your machine -- if such an assignment can be made.
* When the Assignment Server can not find ANY Work Server that is able to satisfy your request, the AS will tell you no work is available with that rather cryptic message. "Empty work server assignment"


When results are uploaded to Work Servers, new WUs are automatically generated, possibly resolving the problem automatically.
Rarely (but recently true for Maxwell) very few projects run successfully on a particular platform and, at times, no WUs may be available, especially when a key work server goes off-line.

Please search recent logs and determine which servers have recently provided WUs for whichever slot is unable to get work. Investigate the status of those work servers and, if necessary, report problems with them.

Topic Closed.

Failed to get assignment from '171.67.108.200:8080'

Posted: Mon Mar 23, 2015 11:01 pm
by Evanguy
Just got home to see one of my WUs complete and then not be able to get anything else... here's the log:

Code: Select all

22:28:52:WU02:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
22:28:53:WU02:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
22:28:53:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:9014 run:289 clone:3 gen:104 core:0xa4 unit:0x00000084664f2de453e5590d0d29c15d
22:28:53:WU02:FS00:Uploading 1.64MiB to 171.64.65.124
22:28:53:WU02:FS00:Connecting to 171.64.65.124:8080
22:28:59:WU02:FS00:Upload 49.48%
22:29:05:WU02:FS00:Upload 98.96%
22:29:18:WARNING:WU02:FS00:Exception: Failed to send results to work server: 10002: Received short response, expected 512 bytes, got 0
22:29:18:WU02:FS00:Trying to send results to collection server
22:29:18:WU02:FS00:Uploading 1.64MiB to 171.65.103.160
22:29:18:WU02:FS00:Connecting to 171.65.103.160:8080
22:29:24:WU02:FS00:Upload 41.87%
22:29:30:WU02:FS00:Upload 87.55%
22:29:58:WU00:FS00:Connecting to 171.67.108.200:8080
22:29:59:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
22:29:59:WU00:FS00:Connecting to 171.67.108.204:80
22:29:59:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
22:29:59:ERROR:WU00:FS00:Exception: Could not get an assignment
22:30:06:WU02:FS00:Upload complete
22:30:07:WU02:FS00:Server responded WORK_ACK (400)
22:30:07:WU02:FS00:Final credit estimate, 1792.00 points
22:30:07:WU02:FS00:Cleaning up
22:32:36:WU00:FS00:Connecting to 171.67.108.200:8080
22:32:36:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
22:32:36:WU00:FS00:Connecting to 171.67.108.204:80
22:32:37:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
22:32:37:ERROR:WU00:FS00:Exception: Could not get an assignment
22:34:23:FS00:Finishing
22:36:50:WU00:FS00:Connecting to 171.67.108.200:8080
22:36:50:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
22:36:50:WU00:FS00:Connecting to 171.67.108.204:80
22:36:51:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
22:36:51:ERROR:WU00:FS00:Exception: Could not get an assignment
22:43:41:WU00:FS00:Connecting to 171.67.108.200:8080
22:43:42:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
22:43:42:WU00:FS00:Connecting to 171.67.108.204:80
22:43:42:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
22:43:42:ERROR:WU00:FS00:Exception: Could not get an assignment
22:54:47:WU00:FS00:Connecting to 171.67.108.200:8080
22:54:47:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
22:54:47:WU00:FS00:Connecting to 171.67.108.204:80
22:54:48:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
22:54:48:ERROR:WU00:FS00:Exception: Could not get an assignment

Re: Failed to get assignment from '171.67.108.200:8080'

Posted: Tue Mar 24, 2015 1:33 am
by sortofageek
When I read your post, I checked the client on my desktop. It appeared to be having the same problem. Before I could isolate the relevant log for comparison, I was reassigned and now have work to do. I hope you are seeing that, too?


Code: Select all

******************************* Date: 2015-03-23 *******************************
23:30:00:WU01:FS01:Connecting to 171.67.108.200:8080
23:30:00:WU01:FS01:Assigned to work server 171.64.65.124
23:30:00:WU01:FS01:Requesting new work unit for slot 01: RUNNING cpu:7 from 171.64.65.124
23:30:00:WU01:FS01:Connecting to 171.64.65.124:8080
23:30:04:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
23:30:04:WU01:FS01:Connecting to 171.64.65.124:80
23:30:08:ERROR:WU01:FS01:Exception: Failed to connect to 171.64.65.124:80: No connection could be made because the target machine actively refused it.
23:30:08:WU01:FS01:Connecting to 171.67.108.200:8080
23:30:09:WU01:FS01:Assigned to work server 171.64.65.124
23:30:09:WU01:FS01:Requesting new work unit for slot 01: RUNNING cpu:7 from 171.64.65.124
23:30:09:WU01:FS01:Connecting to 171.64.65.124:8080
23:30:12:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
23:30:12:WU01:FS01:Connecting to 171.64.65.124:80
23:30:16:ERROR:WU01:FS01:Exception: Failed to connect to 171.64.65.124:80: No connection could be made because the target machine actively refused it.
23:31:08:WU01:FS01:Connecting to 171.67.108.200:8080
23:31:08:WU01:FS01:Assigned to work server 171.64.65.124
23:31:09:WU01:FS01:Requesting new work unit for slot 01: RUNNING cpu:7 from 171.64.65.124
23:31:09:WU01:FS01:Connecting to 171.64.65.124:8080
23:31:12:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
23:31:12:WU01:FS01:Connecting to 171.64.65.124:80
23:31:16:ERROR:WU01:FS01:Exception: Failed to connect to 171.64.65.124:80: No connection could be made because the target machine actively refused it.
23:32:45:WU01:FS01:Connecting to 171.67.108.200:8080
23:32:46:WU01:FS01:Assigned to work server 171.64.65.124
23:32:46:WU01:FS01:Requesting new work unit for slot 01: READY cpu:7 from 171.64.65.124
23:32:46:WU01:FS01:Connecting to 171.64.65.124:8080
23:32:49:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
23:32:49:WU01:FS01:Connecting to 171.64.65.124:80
23:32:53:ERROR:WU01:FS01:Exception: Failed to connect to 171.64.65.124:80: No connection could be made because the target machine actively refused it.
23:35:23:WU01:FS01:Connecting to 171.67.108.200:8080
23:35:23:WU01:FS01:Assigned to work server 171.64.65.124
23:35:23:WU01:FS01:Requesting new work unit for slot 01: READY cpu:7 from 171.64.65.124
23:35:23:WU01:FS01:Connecting to 171.64.65.124:8080
23:35:27:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
23:35:27:WU01:FS01:Connecting to 171.64.65.124:80
23:35:30:ERROR:WU01:FS01:Exception: Failed to connect to 171.64.65.124:80: No connection could be made because the target machine actively refused it.
23:39:37:WU01:FS01:Connecting to 171.67.108.200:8080
23:39:37:WU01:FS01:Assigned to work server 171.64.65.124
23:39:37:WU01:FS01:Requesting new work unit for slot 01: READY cpu:7 from 171.64.65.124
23:39:37:WU01:FS01:Connecting to 171.64.65.124:8080
23:39:41:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
23:39:41:WU01:FS01:Connecting to 171.64.65.124:80
23:39:45:ERROR:WU01:FS01:Exception: Failed to connect to 171.64.65.124:80: No connection could be made because the target machine actively refused it.
23:46:28:WU01:FS01:Connecting to 171.67.108.200:8080
23:46:29:WU01:FS01:Assigned to work server 171.64.65.124
23:46:29:WU01:FS01:Requesting new work unit for slot 01: READY cpu:7 from 171.64.65.124
23:46:29:WU01:FS01:Connecting to 171.64.65.124:8080
23:46:32:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
23:46:32:WU01:FS01:Connecting to 171.64.65.124:80
23:46:36:ERROR:WU01:FS01:Exception: Failed to connect to 171.64.65.124:80: No connection could be made because the target machine actively refused it.
23:57:34:WU01:FS01:Connecting to 171.67.108.200:8080
23:57:34:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:57:34:WU01:FS01:Connecting to 171.67.108.204:80
23:57:37:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:57:37:ERROR:WU01:FS01:Exception: Could not get an assignment
00:15:31:WU01:FS01:Connecting to 171.67.108.200:8080
00:15:31:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
00:15:31:WU01:FS01:Connecting to 171.67.108.204:80
00:15:32:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
00:15:32:ERROR:WU01:FS01:Exception: Could not get an assignment
00:44:33:WU01:FS01:Connecting to 171.67.108.200:8080
00:44:33:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
00:44:33:WU01:FS01:Connecting to 171.67.108.204:80
00:44:34:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
00:44:34:ERROR:WU01:FS01:Exception: Could not get an assignment
01:31:32:WU01:FS01:Connecting to 171.67.108.200:8080
01:31:32:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
01:31:32:WU01:FS01:Connecting to 171.67.108.204:80
01:31:33:WU01:FS01:Assigned to work server 171.64.65.100
01:31:33:WU01:FS01:Requesting new work unit for slot 01: READY cpu:7 from 171.64.65.100
01:31:33:WU01:FS01:Connecting to 171.64.65.100:8080
01:31:33:WU01:FS01:Downloading 615.84KiB
01:31:34:WU01:FS01:Download complete
01:31:34:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:7812 run:1520 clone:0 gen:155 core:0xa4 unit:0x0000015e664f2dcc528fc952caf6be12
01:31:34:WU01:FS01:Starting
01:31:34:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 01 -suffix 01 -version 704 -lifeline 7772 -checkpoint 15 -np 7
01:31:34:WU01:FS01:Started FahCore on PID 104980
01:31:34:WU01:FS01:Core PID:92448
01:31:34:WU01:FS01:FahCore 0xa4 started
01:31:34:WU01:FS01:0xa4:
01:31:34:WU01:FS01:0xa4:*------------------------------*
01:31:34:WU01:FS01:0xa4:Folding@Home Gromacs GB Core
01:31:34:WU01:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
01:31:34:WU01:FS01:0xa4:
01:31:34:WU01:FS01:0xa4:Preparing to commence simulation
01:31:34:WU01:FS01:0xa4:- Looking at optimizations...
01:31:34:WU01:FS01:0xa4:- Created dyn
01:31:34:WU01:FS01:0xa4:- Files status OK
01:31:34:WU01:FS01:0xa4:- Expanded 630113 -> 869808 (decompressed 138.0 percent)
01:31:34:WU01:FS01:0xa4:Called DecompressByteArray: compressed_data_size=630113 data_size=869808, decompressed_data_size=869808 diff=0
01:31:34:WU01:FS01:0xa4:- Digital signature verified
01:31:34:WU01:FS01:0xa4:
01:31:34:WU01:FS01:0xa4:Project: 7812 (Run 1520, Clone 0, Gen 155)
01:31:34:WU01:FS01:0xa4:
01:31:34:WU01:FS01:0xa4:Assembly optimizations on if available.
01:31:34:WU01:FS01:0xa4:Entering M.D.
01:31:40:WU01:FS01:0xa4:Mapping NT from 7 to 7 
01:31:40:WU01:FS01:0xa4:Completed 0 out of 500000 steps  (0%)
01:33:07:WU01:FS01:0xa4:Completed 5000 out of 500000 steps  (1%)

Re: Failed to get assignment from '171.67.108.200:8080'

Posted: Tue Mar 24, 2015 3:09 am
by Evanguy
Haha yep, all good now!

Maybe I jumped the gun a bit there, just haven't seen that happen in a long time. Glad everything's back!