Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

Empty work server assigment - [ CPU:11 ]

https://foldingforum.org/viewtopic.php?t=28863

Page 1 of 1

Empty work server assigment - [ CPU:11 ]

Posted: Tue May 31, 2016 2:28 am
by DeeGee
Since yesterday keep getting this error on those servers. No work on CPU.

Code: Select all

*********************** Log Started 2016-05-31T02:14:23Z ***********************
02:14:23:************************* Folding@home Client *************************
02:14:23:      Website: http://folding.stanford.edu/
02:14:23:    Copyright: (c) 2009-2014 Stanford University
02:14:23:       Author: Joseph Coffland <[email protected]>
02:14:23:         Args: --open-web-control
02:14:23:       Config: C:/ProgramData/FAHClient/config.xml
02:14:23:******************************** Build ********************************
02:14:23:      Version: 7.4.4
02:14:23:         Date: Mar 4 2014
02:14:23:         Time: 20:26:54
02:14:23:      SVN Rev: 4130
02:14:23:       Branch: fah/trunk/client
02:14:23:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
02:14:23:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
02:14:23:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
02:14:23:     Platform: win32 XP
02:14:23:         Bits: 32
02:14:23:         Mode: Release
02:14:23:******************************* System ********************************
02:14:23:          CPU: Intel(R) Core(TM) i7 CPU 970 @ 3.20GHz
02:14:23:       CPU ID: GenuineIntel Family 6 Model 44 Stepping 2
02:14:23:         CPUs: 12
02:14:23:       Memory: 11.99GiB
02:14:23:  Free Memory: 9.02GiB
02:14:23:      Threads: WINDOWS_THREADS
02:14:23:   OS Version: 6.2
02:14:23:  Has Battery: false
02:14:23:   On Battery: false
02:14:23:   UTC Offset: 3
02:14:23:          PID: 4388
02:14:23:          CWD: C:/ProgramData/FAHClient
02:14:23:           OS: Windows 10 Pro
02:14:23:      OS Arch: AMD64
02:14:23:         GPUs: 1
02:14:23:        GPU 0: ATI:5 Hawaii [Radeon R9 200/300 Series]
02:14:23:         CUDA: Not detected
02:14:23:Win32 Service: false
02:14:23:***********************************************************************
02:14:23:<config>
02:14:23:  <!-- Folding Slot Configuration -->
02:14:23:  <cause v='CANCER'/>
02:14:23:
02:14:23:  <!-- Network -->
02:14:23:  <proxy v=':8080'/>
02:14:23:
02:14:23:  <!-- Slot Control -->
02:14:23:  <power v='full'/>
02:14:23:
02:14:23:  <!-- User Information -->
02:14:23:  <passkey v='********************************'/>
02:14:23:  <team v='365'/>
02:14:23:  <user v='DeeGee'/>
02:14:23:
02:14:23:  <!-- Folding Slots -->
02:14:23:  <slot id='0' type='GPU'>
02:14:23:    <client-type v='beta'/>
02:14:23:    <core-priority v='low'/>
02:14:23:    <pause-on-start v='true'/>
02:14:23:    <paused v='true'/>
02:14:23:  </slot>
02:14:23:  <slot id='1' type='CPU'>
02:14:23:    <client-type v='advanced'/>
02:14:23:    <max-packet-size v='big'/>
02:14:23:    <pause-on-start v='true'/>
02:14:23:    <paused v='true'/>
02:14:23:  </slot>
02:14:23:</config>
02:14:23:Trying to access database...
02:14:23:Successfully acquired database lock
02:14:23:Enabled folding slot 00: PAUSED gpu:0:Hawaii [Radeon R9 200/300 Series] (by user)
02:14:23:Enabled folding slot 01: PAUSED cpu:11 (by user)
02:14:40:FS00:Unpaused
02:14:40:FS01:Unpaused
02:14:40:WU01:FS00:Starting
02:14:40:WU01:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/ATI/R600/beta/Core_17.fah/FahCore_17.exe -dir 01 -suffix 01 -version 704 -lifeline 4388 -checkpoint 15 -gpu 0 -gpu-vendor ati
02:14:40:WU01:FS00:Started FahCore on PID 5088
02:14:40:WU01:FS00:Core PID:8032
02:14:40:WU01:FS00:FahCore 0x17 started
02:14:41:WU01:FS00:0x17:*********************** Log Started 2016-05-31T02:14:40Z ***********************
02:14:41:WU01:FS00:0x17:Project: 10467 (Run 0, Clone 361, Gen 315)
02:14:41:WU01:FS00:0x17:Unit: 0x0000020a538b3db9538bc2b308534046
02:14:41:WU01:FS00:0x17:CPU: 0x00000000000000000000000000000000
02:14:41:WU01:FS00:0x17:Machine: 0
02:14:41:WU01:FS00:0x17:Digital signatures verified
02:14:41:WU01:FS00:0x17:Folding@home GPU core17
02:14:41:WU01:FS00:0x17:Version 0.0.55
02:14:41:WU00:FS01:Connecting to 171.67.108.45:8080
02:14:41:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
02:14:41:WU00:FS01:Connecting to 171.64.65.35:80
02:14:42:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
02:14:42:ERROR:WU00:FS01:Exception: Could not get an assignment
02:14:42:WU00:FS01:Connecting to 171.67.108.45:8080
02:14:43:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
02:14:43:WU00:FS01:Connecting to 171.64.65.35:80
02:14:44:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
02:14:44:ERROR:WU00:FS01:Exception: Could not get an assignment
02:15:24:Removing old file 'configs/config-20160527-160240.xml'
02:15:24:Saving configuration to config.xml
02:15:24:<config>
02:15:24:  <!-- Folding Slot Configuration -->
02:15:24:  <cause v='CANCER'/>
02:15:24:
02:15:24:  <!-- Network -->
02:15:24:  <proxy v=':8080'/>
02:15:24:
02:15:24:  <!-- Slot Control -->
02:15:24:  <power v='full'/>
02:15:24:
02:15:24:  <!-- User Information -->
02:15:24:  <passkey v='********************************'/>
02:15:24:  <team v='365'/>
02:15:24:  <user v='DeeGee'/>
02:15:24:
02:15:24:  <!-- Folding Slots -->
02:15:24:  <slot id='0' type='GPU'>
02:15:24:    <client-type v='beta'/>
02:15:24:    <core-priority v='low'/>
02:15:24:    <pause-on-start v='true'/>
02:15:24:  </slot>
02:15:24:  <slot id='1' type='CPU'>
02:15:24:    <client-type v='advanced'/>
02:15:24:    <max-packet-size v='big'/>
02:15:24:    <pause-on-start v='true'/>
02:15:24:  </slot>
02:15:24:</config>
02:15:43:WU00:FS01:Connecting to 171.67.108.45:8080
02:15:43:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
02:15:43:WU00:FS01:Connecting to 171.64.65.35:80
02:15:44:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
02:15:44:ERROR:WU00:FS01:Exception: Could not get an assignment
02:16:45:WU01:FS00:0x17:Completed 0 out of 5000000 steps (0%)
02:16:45:WU01:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
02:17:20:WU00:FS01:Connecting to 171.67.108.45:8080
02:17:21:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
02:17:21:WU00:FS01:Connecting to 171.64.65.35:80
02:17:21:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
02:17:21:ERROR:WU00:FS01:Exception: Could not get an assignment
02:19:57:WU00:FS01:Connecting to 171.67.108.45:8080
02:19:58:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
02:19:58:WU00:FS01:Connecting to 171.64.65.35:80
02:19:58:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
02:19:58:ERROR:WU00:FS01:Exception: Could not get an assignment
02:21:28:WU01:FS00:0x17:Completed 50000 out of 5000000 steps (1%)
02:24:11:WU00:FS01:Connecting to 171.67.108.45:8080
02:24:12:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
02:24:12:WU00:FS01:Connecting to 171.64.65.35:80
02:24:13:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
02:24:13:ERROR:WU00:FS01:Exception: Could not get an assignment
02:26:01:WU01:FS00:0x17:Completed 100000 out of 5000000 steps (2%)

Re: Empty work server assigment, 171.67.108.45 & 171.64.65.3

Posted: Tue May 31, 2016 2:55 am
by Joe_H
Set your CPU count to a non-prime number such as 10.

Re: Empty work server assigment - [ CPU:11 ]

Posted: Tue May 31, 2016 4:01 am
by MarkyMark7
Wow - changing #/CPUs from 7 to 6 worked for me! Prime number causing issue.... interesting

Re: Empty work server assigment - [ CPU:11 ]

Posted: Tue May 31, 2016 8:48 am
by ivanx
It is also happening to me as well. Maybe the servers were turned off because of the holiday yesterday.

Re: Empty work server assigment - [ CPU:11 ]

Posted: Tue May 31, 2016 12:03 pm
by DeeGee
Dropping thread count to 10 seems to have fixed this. Thanks.

But the client sets thread count automatically to x-1, if there is GPU slot. So that logic should probably be fixed if for some reason you can't use odd number of threads anymore (I used 11 threads for years without problems).

Re: Empty work server assigment - [ CPU:11 ]

Posted: Tue May 31, 2016 4:50 pm
by DocJonz
I have been having a similar problem for a day or so with CPU=22 - not a prime number that I am aware of ... strange that the other CPU set up (set at CPU=24 on the same machine) seems to be fine. Anyone explain that one?!

Code: Select all

16:46:15:WU00:FS01:Connecting to 171.67.108.45:8080
16:46:16:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:46:16:WU00:FS01:Connecting to 171.64.65.35:80
16:46:16:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:46:16:ERROR:WU00:FS01:Exception: Could not get an assignment

Re: Empty work server assigment - [ CPU:11 ]

Posted: Tue May 31, 2016 5:13 pm
by DeeGee
In a another thread, it seemed that large thread count clients had to split the threads between several CPU slots. Like 10+12 threads for example.
There seems to be something weird going on with the workunit servers, as there hasn't been this kind of limitation on CPU threads before.

Re: Empty work server assigment - [ CPU:11 ]

Posted: Tue May 31, 2016 5:50 pm
by Joe_H
DocJonz wrote:I have been having a similar problem for a day or so with CPU=22 - not a prime number that I am aware of ... strange that the other CPU set up (set at CPU=24 on the same machine) seems to be fine. Anyone explain that one?!
22 is a multiple of a "large" prime, so it is not used. If you were getting assignments in the past with that setting, the client would have been switching to a lower value and a "Mapping NT 22 to 20" type message would have shown up in your log file.

One of the WS had adjustments made to its assignment settings over the weekend as it was giving out WU's that would fail on systems with settings that were multiples of 7. It is possible the settings were made too widely, and included CPU numbers that were being taken care of automatically by the client.
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited