155.247.166.219 not assigning work unit

Moderators: Site Moderators, FAHC Science Team

Post Reply
davidcoton
Posts: 1094
Joined: Wed Nov 05, 2008 3:19 pm
Location: Cambridge, UK

155.247.166.219 not assigning work unit

Post by davidcoton »

This problem has been happening for several hours. Sanitised log info reassembled after changing verbosity to 3 -- don't know why I had it at 5!
Actual messages filtered to show CPU slot only.

Any ideas, anyone?

Code: Select all

*********************** Log Started 2013-07-12T19:04:26Z ***********************
19:04:26:************************* Folding@home Client *************************
19:04:26:      Website: http://folding.stanford.edu/
19:04:26:    Copyright: (c) 2009-2013 Stanford University
19:04:26:       Author: Joseph Coffland <[email protected]>
19:04:26:         Args: 
19:04:26:       Config: C:/Users/David/AppData/Roaming/FAHClient/config.xml
19:04:26:******************************** Build ********************************
19:04:26:      Version: 7.3.6
19:04:26:         Date: Feb 18 2013
19:04:26:         Time: 15:25:17
19:04:26:      SVN Rev: 3923
19:04:26:       Branch: fah/trunk/client
19:04:26:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
19:04:26:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
19:04:26:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
19:04:26:     Platform: win32 XP
19:04:26:         Bits: 32
19:04:26:         Mode: Release
19:04:26:******************************* System ********************************
19:04:26:          CPU: AMD Athlon(tm) II X4 640 Processor
19:04:26:       CPU ID: AuthenticAMD Family 16 Model 5 Stepping 3
19:04:26:         CPUs: 4
19:04:26:       Memory: 3.50GiB
19:04:26:  Free Memory: 2.13GiB
19:04:26:      Threads: WINDOWS_THREADS
19:04:26:  Has Battery: false
19:04:26:   On Battery: false
19:04:26:   UTC offset: 0
19:04:26:          PID: 5340
19:04:26:          CWD: C:/Users/David/AppData/Roaming/FAHClient
19:04:26:           OS: Windows Vista (TM) Home Premium Service Pack 2
19:04:26:      OS Arch: X86
19:04:26:         GPUs: 1
19:04:26:        GPU 0: NVIDIA:3 GK104 [GeForce GTX 660 Ti]
19:04:26:         CUDA: 3.0
19:04:26:  CUDA Driver: 5000
19:04:26:Win32 Service: false
19:04:26:***********************************************************************

...


21:01:52:Removing old file 'configs/config-20111110-225725.xml'
21:01:52:Saving configuration to config.xml
21:01:52:<config>
21:01:52:  <!-- Folding Core -->
21:01:52:  <checkpoint v='5'/>
21:01:52:
21:01:52:  <!-- Folding Slot Configuration -->
21:01:52:  <client-type v='advanced'/>
21:01:52:  <extra-core-args v='-forceasm'/>
21:01:52:  <power v='full'/>
21:01:52:
21:01:52:  <!-- HTTP Server -->
21:01:52:  <allow v='127.0.0.1 192.168.1.0/24'/>
21:01:52:
21:01:52:  <!-- Network -->
21:01:52:  <proxy v=':8080'/>
21:01:52:
21:01:52:  <!-- Remote Command Server -->
21:01:52:  <password v='*******'/>
21:01:52:
21:01:52:  <!-- User Information -->
21:01:52:  <passkey v='********************************'/>
21:01:52:  <user v='davidcoton'/>
21:01:52:
21:01:52:  <!-- Folding Slots -->
21:01:52:  <slot id='0' type='CPU'>
21:01:52:    <cpus v='3'/>
21:01:52:  </slot>
21:01:52:  <slot id='1' type='GPU'>
21:01:52:    <client-type v='advanced'/>
21:01:52:  </slot>
21:01:52:</config>

...

*********************** Log Started 2013-07-12T19:04:26Z ***********************
19:04:45:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:04:46:WU00:FS00:News: Welcome to Folding@Home
19:04:46:WU00:FS00:Assigned to work server 155.247.166.219
19:04:46:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:04:46:WU00:FS00:Connecting to 155.247.166.219:8080
19:04:47:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:04:47:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:04:48:WU00:FS00:News: Welcome to Folding@Home
19:04:48:WU00:FS00:Assigned to work server 155.247.166.219
19:04:48:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:04:48:WU00:FS00:Connecting to 155.247.166.219:8080
19:04:48:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:05:47:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:05:47:WU00:FS00:News: Welcome to Folding@Home
19:05:47:WU00:FS00:Assigned to work server 155.247.166.219
19:05:48:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:05:48:WU00:FS00:Connecting to 155.247.166.219:8080
19:05:48:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:07:24:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:07:25:WU00:FS00:News: Welcome to Folding@Home
19:07:25:WU00:FS00:Assigned to work server 155.247.166.219
19:07:25:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:07:25:WU00:FS00:Connecting to 155.247.166.219:8080
19:07:25:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:10:01:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:10:02:WU00:FS00:News: Welcome to Folding@Home
19:10:02:WU00:FS00:Assigned to work server 155.247.166.219
19:10:02:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:10:02:WU00:FS00:Connecting to 155.247.166.219:8080
19:10:03:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:14:16:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:14:16:WU00:FS00:News: Welcome to Folding@Home
19:14:16:WU00:FS00:Assigned to work server 155.247.166.219
19:14:17:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:14:17:WU00:FS00:Connecting to 155.247.166.219:8080
19:14:17:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:21:07:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:21:08:WU00:FS00:News: Welcome to Folding@Home
19:21:08:WU00:FS00:Assigned to work server 155.247.166.219
19:21:08:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:21:08:WU00:FS00:Connecting to 155.247.166.219:8080
19:21:08:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:32:12:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:32:13:WU00:FS00:News: Welcome to Folding@Home
19:32:13:WU00:FS00:Assigned to work server 155.247.166.219
19:32:13:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:32:13:WU00:FS00:Connecting to 155.247.166.219:8080
19:32:14:ERROR:WU00:FS00:Exception: Server did not assign work unit
19:50:09:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:50:10:WU00:FS00:News: Welcome to Folding@Home
19:50:10:WU00:FS00:Assigned to work server 155.247.166.219
19:50:10:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
19:50:10:WU00:FS00:Connecting to 155.247.166.219:8080
19:50:11:ERROR:WU00:FS00:Exception: Server did not assign work unit
20:19:11:WU00:FS00:Connecting to assign3.stanford.edu:8080
20:19:12:WU00:FS00:News: Welcome to Folding@Home
20:19:12:WU00:FS00:Assigned to work server 155.247.166.219
20:19:12:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
20:19:12:WU00:FS00:Connecting to 155.247.166.219:8080
20:19:13:ERROR:WU00:FS00:Exception: Server did not assign work unit
21:06:10:WU00:FS00:Connecting to assign3.stanford.edu:8080
21:06:11:WU00:FS00:News: Welcome to Folding@Home
21:06:11:WU00:FS00:Assigned to work server 155.247.166.219
21:06:11:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
21:06:11:WU00:FS00:Connecting to 155.247.166.219:8080
21:06:11:ERROR:WU00:FS00:Exception: Server did not assign work unit
David
Image
Top
7im
Posts: 10179
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:
Contact 7im

Re: 155.247.166.219 not assigning work unit

Post by 7im »

Remove this... (not needed any more, though unrelated)

21:01:52: <extra-core-args v='-forceasm'/>

Could be an assingment server issue doesn't like CPU=3. Try cores=2 or 4 and see of that gets work.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Top
davidcoton
Posts: 1094
Joined: Wed Nov 05, 2008 3:19 pm
Location: Cambridge, UK

Re: 155.247.166.219 not assigning work unit

Post by davidcoton »

forceasm removed.
CPU:4 and CPU:2 get the same problem.

David
Image
Top
7im
Posts: 10179
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:
Contact 7im

Re: 155.247.166.219 not assigning work unit

Post by 7im »

Try removing the "advanced" setting from the CPU client (looks to be set on the expert tab).
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Top
davidcoton
Posts: 1094
Joined: Wed Nov 05, 2008 3:19 pm
Location: Cambridge, UK

Re: 155.247.166.219 not assigning work unit

Post by davidcoton »

Can't try that until GPU slot finishes (could loose the unit). I thought advanced should fall back if no advanced units are available? (BTW, this configuration has been working happily since 8900 went to advanced).

David
Image
Top
bollix47
Posts: 2957
Joined: Sun Dec 02, 2007 5:04 am
Location: Canada

Re: 155.247.166.219 not assigning work unit

Post by bollix47 »

Your GPU slot has it's own advanced setting and should not be affected by removing the other reference to advanced:

21:01:52: <!-- Folding Slot Configuration -->
21:01:52: <client-type v='advanced'/>

As 7im mentioned this has probably been set in the Expert tab of FAHControl.

Most changes like this one do not take effect until you request a new work unit and since it's the CPU slot that can't get work there's no need to pause the GPU slot. The CPU slot should be paused(although even that may not be necessary in this case), then make the change, and set it fold again but you can, of course, set the GPU to Finish and make the change then if you prefer. No need to remove the client-type advanced in your GPU slot configuration, just the one in the Expert tab.
Top
davidcoton
Posts: 1094
Joined: Wed Nov 05, 2008 3:19 pm
Location: Cambridge, UK

Re: 155.247.166.219 not assigning work unit

Post by davidcoton »

Oops, didn't notice that!

Removed the advanced setting on the expert tab, and immediately got an 8702 unit

From my POV, case solved -- unless there are any questions about why it works that way.

Thanks both for your input.

David
Image
Top
hinebaud
Posts: 4
Joined: Wed Dec 15, 2010 4:32 pm

Re: 155.247.166.219 not assigning work unit

Post by hinebaud »

I had problems with this server today. I could not get a work unit for an hour. SMP 4 and did not have advanced setting. I was finally assigned work server 128.143.231.202 and immediately downloaded new work unit.
Top
SodaAnt
Posts: 38
Joined: Sat Aug 06, 2011 12:03 am

Re: 155.247.166.219 not assigning work unit

Post by SodaAnt »

Same issue happening for me too.
Top
PantherX
Site Moderator
Posts: 6986
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:
Contact PantherX

Re: 155.247.166.219 not assigning work unit

Post by PantherX »

Thanks for informing us. Sever Owner has been notified of this issue.
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
Top
vvoelz
Pande Group Member
Posts: 552
Joined: Sun Dec 02, 2007 8:07 pm
Location: Temple University, Philadelphia PA

Re: 155.247.166.219 not assigning work unit

Post by vvoelz »

This is Vince, the "Server Owner". For some reason the server was out of available WUs. I've made more available, which should fix the immediate problem (already I see assignments are being made). --Vince
Top
Post Reply

Return to “Issues with a specific server”