Empty work server assignment??? [cpu:7]

[JimboPalmer]

Didn't any of the recommendations mention giving us the first one hundred lines of your log file?

Right now we do not know anything, and would be guessing randomly. (we do not know your OS, if you have a video card, what CPUs you have, what version of the FAH software you are running, etc. we can't look at your history, your configuration or events prior to the error.)

[eliot1785]

I am not the OP but having the same issue. Looks like some servers are empty. Pasting my logs below.

Code: Select all

*********************** Log Started 2016-05-31T00:56:00Z ***********************
******************************* Date: 2016-05-31 *******************************
15:30:00:FS00:Unpaused
15:30:00:WU01:FS00:Starting
15:30:00:WU01:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Stephen/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 01 -suffix 01 -version 704 -lifeline 3048 -checkpoint 15 -np 7
15:30:00:WU01:FS00:Started FahCore on PID 13512
15:30:00:WU01:FS00:Core PID:5160
15:30:00:WU01:FS00:FahCore 0xa4 started
15:30:00:WU01:FS00:0xa4:
15:30:00:WU01:FS00:0xa4:*------------------------------*
15:30:00:WU01:FS00:0xa4:Folding@Home Gromacs GB Core
15:30:00:WU01:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
15:30:00:WU01:FS00:0xa4:
15:30:00:WU01:FS00:0xa4:Preparing to commence simulation
15:30:01:WU01:FS00:0xa4:- Looking at optimizations...
15:30:01:WU01:FS00:0xa4:- Files status OK
15:30:01:WU01:FS00:0xa4:- Expanded 825379 -> 1398040 (decompressed 169.3 percent)
15:30:01:WU01:FS00:0xa4:Called DecompressByteArray: compressed_data_size=825379 data_size=1398040, decompressed_data_size=1398040 diff=0
15:30:01:WU01:FS00:0xa4:- Digital signature verified
15:30:01:WU01:FS00:0xa4:
15:30:01:WU01:FS00:0xa4:Project: 9039 (Run 315, Clone 1, Gen 206)
15:30:01:WU01:FS00:0xa4:
15:30:01:WU01:FS00:0xa4:Assembly optimizations on if available.
15:30:01:WU01:FS00:0xa4:Entering M.D.
15:30:06:WU01:FS00:0xa4:Using Gromacs checkpoints
15:30:06:WU01:FS00:0xa4:Mapping NT from 7 to 7 
15:30:06:WU01:FS00:0xa4:Resuming from checkpoint
15:30:06:WU01:FS00:0xa4:Verified 01/wudata_01.log
15:30:06:WU01:FS00:0xa4:Verified 01/wudata_01.trr
15:30:06:WU01:FS00:0xa4:Verified 01/wudata_01.xtc
15:30:06:WU01:FS00:0xa4:Verified 01/wudata_01.edr
15:30:07:WU01:FS00:0xa4:Completed 151855 out of 250000 steps  (60%)
15:30:31:WU01:FS00:0xa4:Completed 152500 out of 250000 steps  (61%)
15:32:24:WU01:FS00:0xa4:Completed 155000 out of 250000 steps  (62%)
15:34:25:WU01:FS00:0xa4:Completed 157500 out of 250000 steps  (63%)
15:37:28:WU01:FS00:0xa4:Completed 160000 out of 250000 steps  (64%)
15:40:43:WU01:FS00:0xa4:Completed 162500 out of 250000 steps  (65%)
15:44:08:WU01:FS00:0xa4:Completed 165000 out of 250000 steps  (66%)
15:47:37:WU01:FS00:0xa4:Completed 167500 out of 250000 steps  (67%)
15:51:08:WU01:FS00:0xa4:Completed 170000 out of 250000 steps  (68%)
15:54:40:WU01:FS00:0xa4:Completed 172500 out of 250000 steps  (69%)
15:58:16:WU01:FS00:0xa4:Completed 175000 out of 250000 steps  (70%)
16:01:52:WU01:FS00:0xa4:Completed 177500 out of 250000 steps  (71%)
16:05:33:WU01:FS00:0xa4:Completed 180000 out of 250000 steps  (72%)
16:09:15:WU01:FS00:0xa4:Completed 182500 out of 250000 steps  (73%)
16:12:58:WU01:FS00:0xa4:Completed 185000 out of 250000 steps  (74%)
16:16:42:WU01:FS00:0xa4:Completed 187500 out of 250000 steps  (75%)
16:20:29:WU01:FS00:0xa4:Completed 190000 out of 250000 steps  (76%)
16:24:18:WU01:FS00:0xa4:Completed 192500 out of 250000 steps  (77%)
16:28:09:WU01:FS00:0xa4:Completed 195000 out of 250000 steps  (78%)
16:32:03:WU01:FS00:0xa4:Completed 197500 out of 250000 steps  (79%)
16:36:01:WU01:FS00:0xa4:Completed 200000 out of 250000 steps  (80%)
16:40:00:WU01:FS00:0xa4:Completed 202500 out of 250000 steps  (81%)
16:44:00:WU01:FS00:0xa4:Completed 205000 out of 250000 steps  (82%)
16:47:59:WU01:FS00:0xa4:Completed 207500 out of 250000 steps  (83%)
16:52:01:WU01:FS00:0xa4:Completed 210000 out of 250000 steps  (84%)
16:56:02:WU01:FS00:0xa4:Completed 212500 out of 250000 steps  (85%)
17:00:08:WU01:FS00:0xa4:Completed 215000 out of 250000 steps  (86%)
17:04:16:WU01:FS00:0xa4:Completed 217500 out of 250000 steps  (87%)
17:08:24:WU01:FS00:0xa4:Completed 220000 out of 250000 steps  (88%)
17:12:32:WU01:FS00:0xa4:Completed 222500 out of 250000 steps  (89%)
17:16:48:WU01:FS00:0xa4:Completed 225000 out of 250000 steps  (90%)
17:21:05:WU01:FS00:0xa4:Completed 227500 out of 250000 steps  (91%)
17:25:21:WU01:FS00:0xa4:Completed 230000 out of 250000 steps  (92%)
17:29:11:WU01:FS00:0xa4:Completed 232500 out of 250000 steps  (93%)
17:33:22:WU01:FS00:0xa4:Completed 235000 out of 250000 steps  (94%)
17:37:40:WU01:FS00:0xa4:Completed 237500 out of 250000 steps  (95%)
17:42:04:WU01:FS00:0xa4:Completed 240000 out of 250000 steps  (96%)
17:46:29:WU01:FS00:0xa4:Completed 242500 out of 250000 steps  (97%)
17:50:56:WU01:FS00:0xa4:Completed 245000 out of 250000 steps  (98%)
17:55:28:WU01:FS00:0xa4:Completed 247500 out of 250000 steps  (99%)
17:55:29:WU02:FS00:Connecting to 171.67.108.45:8080
17:55:30:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
17:55:30:WU02:FS00:Connecting to 171.64.65.35:80
17:55:30:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
17:55:30:ERROR:WU02:FS00:Exception: Could not get an assignment
17:55:30:WU02:FS00:Connecting to 171.67.108.45:8080
17:55:31:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
17:55:31:WU02:FS00:Connecting to 171.64.65.35:80
17:55:31:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
17:55:31:ERROR:WU02:FS00:Exception: Could not get an assignment
17:56:30:WU02:FS00:Connecting to 171.67.108.45:8080
17:56:31:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
17:56:31:WU02:FS00:Connecting to 171.64.65.35:80
17:56:31:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
17:56:31:ERROR:WU02:FS00:Exception: Could not get an assignment
17:58:07:WU02:FS00:Connecting to 171.67.108.45:8080
17:58:08:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
17:58:08:WU02:FS00:Connecting to 171.64.65.35:80
17:58:08:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
17:58:08:ERROR:WU02:FS00:Exception: Could not get an assignment
17:59:58:WU01:FS00:0xa4:Completed 250000 out of 250000 steps  (100%)
17:59:59:WU01:FS00:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
18:00:09:WU01:FS00:0xa4:
18:00:09:WU01:FS00:0xa4:Finished Work Unit:
18:00:09:WU01:FS00:0xa4:- Reading up to 811440 from "01/wudata_01.trr": Read 811440
18:00:09:WU01:FS00:0xa4:trr file hash check passed.
18:00:09:WU01:FS00:0xa4:- Reading up to 745904 from "01/wudata_01.xtc": Read 745904
18:00:09:WU01:FS00:0xa4:xtc file hash check passed.
18:00:09:WU01:FS00:0xa4:edr file hash check passed.
18:00:09:WU01:FS00:0xa4:logfile size: 25063
18:00:09:WU01:FS00:0xa4:Leaving Run
18:00:11:WU01:FS00:0xa4:- Writing 1584895 bytes of core data to disk...
18:00:11:WU01:FS00:0xa4:Done: 1584383 -> 1538201 (compressed to 97.0 percent)
18:00:11:WU01:FS00:0xa4:  ... Done.
18:00:12:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
18:00:12:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:9039 run:315 clone:1 gen:206 core:0xa4 unit:0x000000e7ab436c9e56982853a3490005
18:00:12:WU01:FS00:Uploading 1.47MiB to 171.67.108.158
18:00:12:WU01:FS00:Connecting to 171.67.108.158:8080
18:00:14:WU01:FS00:Upload complete
18:00:14:WU01:FS00:Server responded WORK_ACK (400)
18:00:14:WU01:FS00:Final credit estimate, 207.00 points
18:00:14:WU01:FS00:Cleaning up
18:00:45:WU02:FS00:Connecting to 171.67.108.45:8080
18:00:45:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:00:45:WU02:FS00:Connecting to 171.64.65.35:80
18:00:46:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:00:46:ERROR:WU02:FS00:Exception: Could not get an assignment
18:04:59:WU02:FS00:Connecting to 171.67.108.45:8080
18:04:59:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:04:59:WU02:FS00:Connecting to 171.64.65.35:80
18:05:00:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:05:00:ERROR:WU02:FS00:Exception: Could not get an assignment
18:11:50:WU02:FS00:Connecting to 171.67.108.45:8080
18:11:51:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:11:51:WU02:FS00:Connecting to 171.64.65.35:80
18:11:51:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:11:51:ERROR:WU02:FS00:Exception: Could not get an assignment
18:22:56:WU02:FS00:Connecting to 171.67.108.45:8080
18:22:57:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:22:57:WU02:FS00:Connecting to 171.64.65.35:80
18:22:57:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:22:57:ERROR:WU02:FS00:Exception: Could not get an assignment
18:40:53:WU02:FS00:Connecting to 171.67.108.45:8080
18:40:53:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:40:53:WU02:FS00:Connecting to 171.64.65.35:80
18:40:54:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:40:54:ERROR:WU02:FS00:Exception: Could not get an assignment
19:09:55:WU02:FS00:Connecting to 171.67.108.45:8080
19:09:55:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
19:09:55:WU02:FS00:Connecting to 171.64.65.35:80
19:09:56:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
19:09:56:ERROR:WU02:FS00:Exception: Could not get an assignment
19:56:54:WU02:FS00:Connecting to 171.67.108.45:8080
19:56:54:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
19:56:54:WU02:FS00:Connecting to 171.64.65.35:80
19:56:55:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
19:56:55:ERROR:WU02:FS00:Exception: Could not get an assignment
21:12:55:WU02:FS00:Connecting to 171.67.108.45:8080
21:12:55:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:12:55:WU02:FS00:Connecting to 171.64.65.35:80
21:12:56:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:12:56:ERROR:WU02:FS00:Exception: Could not get an assignment
******************************* Date: 2016-05-31 *******************************
23:15:54:WU02:FS00:Connecting to 171.67.108.45:8080
23:15:55:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
23:15:55:WU02:FS00:Connecting to 171.64.65.35:80
23:15:55:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
23:15:56:ERROR:WU02:FS00:Exception: Could not get an assignment
23:34:49:FS00:Paused
23:58:19:FS00:Unpaused
23:58:19:WU02:FS00:Connecting to 171.67.108.45:8080
23:58:20:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
23:58:20:WU02:FS00:Connecting to 171.64.65.35:80
23:58:21:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
23:58:21:ERROR:WU02:FS00:Exception: Could not get an assignment
23:59:56:WU02:FS00:Connecting to 171.67.108.45:8080
23:59:57:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
23:59:57:WU02:FS00:Connecting to 171.64.65.35:80
23:59:57:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
23:59:57:ERROR:WU02:FS00:Exception: Could not get an assignment
00:02:33:WU02:FS00:Connecting to 171.67.108.45:8080
00:02:34:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:02:34:WU02:FS00:Connecting to 171.64.65.35:80
00:02:34:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:02:34:ERROR:WU02:FS00:Exception: Could not get an assignment
00:06:48:WU02:FS00:Connecting to 171.67.108.45:8080
00:06:48:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:06:48:WU02:FS00:Connecting to 171.64.65.35:80
00:06:49:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:06:49:ERROR:WU02:FS00:Exception: Could not get an assignment
00:13:39:WU02:FS00:Connecting to 171.67.108.45:8080
00:13:40:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:13:40:WU02:FS00:Connecting to 171.64.65.35:80
00:13:40:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:13:40:ERROR:WU02:FS00:Exception: Could not get an assignment
00:24:45:WU02:FS00:Connecting to 171.67.108.45:8080
00:24:45:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:24:45:WU02:FS00:Connecting to 171.64.65.35:80
00:24:46:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:24:46:ERROR:WU02:FS00:Exception: Could not get an assignment
00:42:41:WU02:FS00:Connecting to 171.67.108.45:8080
00:42:42:WARNING:WU02:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:42:42:WU02:FS00:Connecting to 171.64.65.35:80
00:42:42:WARNING:WU02:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:42:42:ERROR:WU02:FS00:Exception: Could not get an assignment

[DeeGee]

Apparently workservers were changed during the weekend to not give workunits to clients running "Large Prime" (7, 11, 13, 17, 19 etc.) number of threads. Your client seem to be set at 7 threads, so change it to next lower one. In OP's case 6.

[eliot1785]

Apparently workservers were changed during the weekend to not give workunits to clients running "Large Prime" (7, 11, 13, 17, 19 etc.) number of threads. Your client seem to be set at 7 threads, so change it to next lower one. In OP's case 6.

How do I do that?

And yeah that seems strange - is that a bug? If so I assume I am going to want to change it back once they fix that bug.

[pimpanther]

i have the same prob.52 million without a prob and no cpu folding just empty servers,[4790k] os 10 gpu 980gtx HoF

Code: Select all

*********************** Log Started 2016-06-02T21:50:17Z ***********************
21:50:17:************************* Folding@home Client *************************
21:50:17:      Website: http://folding.stanford.edu/
21:50:17:    Copyright: (c) 2009-2014 Stanford University
21:50:17:       Author: Joseph Coffland <[email protected]>
21:50:17:         Args: --open-web-control
21:50:17:       Config: C:/Users/ant/AppData/Roaming/FAHClient/config.xml
21:50:17:******************************** Build ********************************
21:50:17:      Version: 7.4.4
21:50:17:         Date: Mar 4 2014
21:50:17:         Time: 20:26:54
21:50:17:      SVN Rev: 4130
21:50:17:       Branch: fah/trunk/client
21:50:17:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
21:50:17:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
21:50:17:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
21:50:17:     Platform: win32 XP
21:50:17:         Bits: 32
21:50:17:         Mode: Release
21:50:17:******************************* System ********************************
21:50:17:          CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
21:50:17:       CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
21:50:17:         CPUs: 8
21:50:17:       Memory: 15.94GiB
21:50:17:  Free Memory: 11.09GiB
21:50:17:      Threads: WINDOWS_THREADS
21:50:17:   OS Version: 6.2
21:50:17:  Has Battery: false
21:50:17:   On Battery: false
21:50:17:   UTC Offset: 1
21:50:17:          PID: 11540
21:50:17:          CWD: C:/Users/ant/AppData/Roaming/FAHClient
21:50:17:           OS: Windows 10 Home
21:50:17:      OS Arch: AMD64
21:50:17:         GPUs: 1
21:50:17:        GPU 0: NVIDIA:5 GM204 [GeForce GTX 980]
21:50:17:         CUDA: 5.2
21:50:17:  CUDA Driver: 8000
21:50:17:Win32 Service: false
21:50:17:***********************************************************************
21:50:17:<config>
21:50:17:  <!-- Network -->
21:50:17:  <proxy v=':8080'/>
21:50:17:
21:50:17:  <!-- Slot Control -->
21:50:17:  <pause-on-battery v='false'/>
21:50:17:  <power v='FULL'/>
21:50:17:
21:50:17:  <!-- User Information -->
21:50:17:  <passkey v='********************************'/>
21:50:17:  <team v='40051'/>
21:50:17:  <user v='pimpanther'/>
21:50:17:
21:50:17:  <!-- Folding Slots -->
21:50:17:  <slot id='0' type='CPU'/>
21:50:17:  <slot id='1' type='GPU'/>
21:50:17:</config>
21:50:17:Trying to access database...
21:50:17:Successfully acquired database lock
21:50:17:Enabled folding slot 00: READY cpu:7
21:50:17:Enabled folding slot 01: READY gpu:0:GM204 [GeForce GTX 980]
21:50:17:WU01:FS01:Starting
21:50:17:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/ant/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_18.fah/FahCore_18.exe -dir 01 -suffix 01 -version 704 -lifeline 11540 -checkpoint 15 -gpu 0 -gpu-vendor nvidia
21:50:17:WU01:FS01:Started FahCore on PID 9568
21:50:17:WU01:FS01:Core PID:5196
21:50:17:WU01:FS01:FahCore 0x18 started
21:50:17:WU01:FS01:0x18:*********************** Log Started 2016-06-02T21:50:17Z ***********************
21:50:17:WU01:FS01:0x18:Project: 9159 (Run 22, Clone 0, Gen 361)
21:50:17:WU01:FS01:0x18:Unit: 0x0000019bab404154567457924ade4c85
21:50:17:WU01:FS01:0x18:CPU: 0x00000000000000000000000000000000
21:50:17:WU01:FS01:0x18:Machine: 1
21:50:17:WU01:FS01:0x18:Digital signatures verified
21:50:17:WU01:FS01:0x18:Folding@home GPU core18
21:50:17:WU01:FS01:0x18:Version 0.0.4
21:50:17:WU01:FS01:0x18:  Found a checkpoint file
21:50:18:WU00:FS00:Connecting to 171.67.108.45:8080
21:50:24:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:50:24:WU00:FS00:Connecting to 171.64.65.35:80
21:50:25:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:50:25:ERROR:WU00:FS00:Exception: Could not get an assignment
21:50:25:WU00:FS00:Connecting to 171.67.108.45:8080
21:50:26:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:50:26:WU00:FS00:Connecting to 171.64.65.35:80
21:50:27:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:50:27:ERROR:WU00:FS00:Exception: Could not get an assignment
21:50:30:19:127.0.0.1:New Web connection
21:50:33:WU01:FS01:0x18:Completed 500000 out of 2500000 steps (20%)
21:50:33:WU01:FS01:0x18:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
21:51:25:WU00:FS00:Connecting to 171.67.108.45:8080
21:51:27:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:51:27:WU00:FS00:Connecting to 171.64.65.35:80
21:51:29:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:51:29:ERROR:WU00:FS00:Exception: Could not get an assignment
21:51:48:WU01:FS01:0x18:Completed 525000 out of 2500000 steps (21%)
21:52:19:Saving configuration to config.xml
21:52:19:<config>
21:52:19:  <!-- Network -->
21:52:19:  <proxy v=':8080'/>
21:52:19:
21:52:19:  <!-- Slot Control -->
21:52:19:  <pause-on-battery v='false'/>
21:52:19:  <power v='FULL'/>
21:52:19:
21:52:19:  <!-- User Information -->
21:52:19:  <passkey v='********************************'/>
21:52:19:  <team v='40051'/>
21:52:19:  <user v='Deadlock'/>
21:52:19:
21:52:19:  <!-- Folding Slots -->
21:52:19:  <slot id='0' type='CPU'/>
21:52:19:  <slot id='1' type='GPU'/>
21:52:19:</config>
21:52:57:WU01:FS01:0x18:Completed 550000 out of 2500000 steps (22%)
21:53:02:WU00:FS00:Connecting to 171.67.108.45:8080
21:53:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:53:04:WU00:FS00:Connecting to 171.64.65.35:80
21:53:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:53:05:ERROR:WU00:FS00:Exception: Could not get an assignment
21:54:07:WU01:FS01:0x18:Completed 575000 out of 2500000 steps (23%)
21:55:16:WU01:FS01:0x18:Completed 600000 out of 2500000 steps (24%)
21:55:40:WU00:FS00:Connecting to 171.67.108.45:8080
21:55:42:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:55:42:WU00:FS00:Connecting to 171.64.65.35:80
21:55:43:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:55:43:ERROR:WU00:FS00:Exception: Could not get an assignment
21:56:31:WU01:FS01:0x18:Completed 625000 out of 2500000 steps (25%)
21:57:41:WU01:FS01:0x18:Completed 650000 out of 2500000 steps (26%)
21:58:51:WU01:FS01:0x18:Completed 675000 out of 2500000 steps (27%)
21:59:54:WU00:FS00:Connecting to 171.67.108.45:8080
21:59:55:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:59:55:WU00:FS00:Connecting to 171.64.65.35:80
21:59:56:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:59:56:ERROR:WU00:FS00:Exception: Could not get an assignment
22:00:01:WU01:FS01:0x18:Completed 700000 out of 2500000 steps (28%)

[7im]

Not a sound recommendation, IMO, to turn off a top of the line CPU for folding.

Change the CPU setting from -1 to 6. For some reason, the servers don't like CPU:7 at the moment, which is what happens when an 8 thread CPU uses the "-1" auto setting. It reserves a thread for the GPU (aka 7). Instead, set the CPU thread count to 6 manually. Performance doesn't change much at all. That CPU only has 4 FPUs anyway, which do all the processing for FAH.

The FAH Configuration Guide has some pictorial assistance. Edit the CPU slot and change the -1 setting to 6. Save, okay, etc.

[bruce]

... If F@H can't fix this flaw....

Not a sound recommendation, IMO,...

GROMACS has dropped support for 7 CPUs. If you can convince them to fix it, please do.

Stanford can devise a strategy to make all CPU:7 systems revert to CPU:6 even without you manually making the change. Unfortunately it can't do that quickly, so you're better off following 7im's suggestion (above).

[eliot1785]

Wow. That's quite a blow from GROMACS since I would imagine that 7 CPU's are a plurality of contributors (or nearly so).

I will follow 7im's instructions.

[7im]

... If F@H can't fix this flaw....

Not a sound recommendation, IMO,...

GROMACS has dropped support for 7 CPUs. If you can convince them to fix it, please do.

Regardless of what Gromacs decides to do in some future version of its software, FAH is still running the exact same a4 core from several years ago. Nothing has changed in that core, so this is not a core issue, aka not a Gromacs issue.

This is a issue with the server settings getting changed to disallow CPU:7 assignments, and PG did so without any donor notification.

And just a guess, but this also sounds like a compromise done to enable testing on the previously mentioned AVX core. Only a new version of GROMACS, in a new FAHCore would have a new "feature" like dropping CPU:7 support.

Pande Group better come up with a better solution to this problem than waiting for each of the donors running this kind of config to show up in the forum. As others have noted, this is a big waste of resources, and a significant customer disservice.

[bruce]

"Houston, we have a problem." (sic)

Consider the facts here. The servers have NOT been changed. The FAHCore has not been changed.

What's left? I suspect that the active servers have run out of projects for which 7 CPUs has been permitted.

Please look back in your logs. What were the last few projects that you successfully completed with CPU:7? Are those projects active today? (I don't have any way to check if that's the issue.)

Also, look back in the history of what has been recommended by this forum. We've always suggested that the setting CPU:7 limits your access to a few projects and warned you that they might run out at any time. Then they might come back at any time.

It's also a fact that GROMACS recommends against using 7 and in some future core, it will be re-mapped to 6.

[bruce]

FAH's default settings are set when FAH is installed ant after that, it's up to you to reconfigure. The current settings are reported to the Assignment Server and it attempts to find a project designed for that particular configuration. If the Assignment Server constructs a list of Work Servers that have projects which may be assigned to your configuration. If that list is empty, it gives the error message saying that list is empty.

The client doesn't know what WUs are available, nor does it automatically reconfigure itself. (There is no "second guessing.")

[eliot1785]

"Houston, we have a problem." (sic)

Consider the facts here. The servers have NOT been changed. The FAHCore has not been changed.

What's left? I suspect that the active servers have run out of projects for which 7 CPUs has been permitted.

Please look back in your logs. What were the last few projects that you successfully completed with CPU:7? Are those projects active today? (I don't have any way to check if that's the issue.)

Also, look back in the history of what has been recommended by this forum. We've always suggested that the setting CPU:7 limits your access to a few projects and warned you that they might run out at any time. Then they might come back at any time.

It's also a fact that GROMACS recommends against using 7 and in some future core, it will be re-mapped to 6.

If the 7-CPU projects are not coming back soon, could they just remap on the server side to send 6-CPU projects when somebody presents with 7 CPU's?

Either way, the participants here haven't set CPU:7, we set CPU:-1. I don't know if I'm just beating a dead horse at this point, but the vast majority of medium-to-high-end consumer PC's sold today will have a 4 core CPU (8 logical cores) with 1 GPU, meaning those defaults are going to be problematic if not fixed on the server side somehow.

[eliot1785]

To put it another way: I think that GROMACS sees no problem with disallowing 7 cores because honestly, are there *any* CPU's with 7 logical cores instead of a multiple of 2?

But FaH defaults don't align with this, because FaH defaults subtract 1 for the GPU. So what is unlikely for GROMACS becomes highly likely for FaH.

[bruce]

The CPUs-1_Per_GPU was simple but it does create a problem for a lot of system. It should have been CPUs-1per_GPU EXCEPT if that gives 7, or 11 or a larger prime, but that's not the way the client was written ... and it has been a long, long time since anybody worked on a revision for the client. It just wasn't considered more critical than a lot of other things ... until all of the projects that run successfully on CPU:7 disappeared.

The responsibility for each portion of the assignment process is divided between the client logic, the server logic, and the FahCore remapping logic. To change the client requires (A) working out logic that will work better without changes to the other two, (B) Beta testing that client, and (C) Asking everybody to update their client (including those who do not read sources of on-line information). Installing a new client is a manual operation.

If a client is configured for CPU:7, the assignment logic will only assign WUs that will work with 7 from whatever active projects it finds at the time. A WU that works with 7 will also work with 6 so that mapping COULD be included in a FAHCore but Cores a4/a5 didn’t think that needed to be done, I'm confident that this is a big enough issue for that to be included in the next Core.

[Joe_H]

If the 7-CPU projects are not coming back soon, could they just remap on the server side to send 6-CPU projects when somebody presents with 7 CPU's?

In theory the servers could, however the current client and CPU folding core do not support doing that mapping. As mentioned by Bruce, a future core could handle doing this. Dr. Pande has announced such a core was being worked on, but no release date has yet been given.