New Comp w/ Win 10 folding fail

JZL

New member
I upgraded my folding comp from an old Opty 175 running Win XP to an E8400 running Win10. I DL'ed FAH client 7.4.4.

Everything seems OK, except that it can't seem to find a WU to download. I'm looking at a page that says F@H Client Advanced Control and it looks like it's tried to get a WU 5x and will try again in about four mins. The Queue says download progress 0% and the Folding slot shows the CPU as "ready."

The viewer mode says connected and has JZL and Team 64, but nothing is happening.

What have I dakked?
 
I get that fairly often on my Xeon E5-2650 v3, but it never happens to me on my i5-6600K

On the Xeon, the log file will say 'WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment. 15:59:50:ERROR:WU00:FS00:Exception: Could not get an assignment'

I think what happens is the project literally runs out of work assignments for certain processors; so it will just sit there saying ready until stanford readies the next batch of simulated proteins to fold.

There's nothing you can do other than wait...
 
How odd, I don't recall ever having to wait on the venerable Opty, but I wasn't gawking at it that much either.

I bought a refurb HP 9700 cakebox micro-desktop for ~ $120 and finally dinked around with it yesterday during the games. This is the first non-laptop computer I bought, instead of made, since the old 1999 Gateway P3-450ghz.

Thx for the help. You probably saved me hours of red-herring trouble-shooting, head-banging, yada. :)
 
Well if you want to make sure; try a full uninstall (including the data) and then reinstall... see if it still does it after that
 
I'd already done that.

It's been almost 24 hrs now. You'd think they'd throw my E8400 a bone by now (?) It's made 13 attempts and the time between tries is over an hour now. Hrmmm.

My client was assigned to the IP address 0.0.0.0. What’s up?

From time to time, we may not have work that matches the requirement of every platform. When that is true, we will not supply you with duplicated work that really isn’t needed. We’d rather have some clients idle and repeatedly rechecking for new work than busy for long periods working on something that doesn’t need to be completed. Even though your computer may see occasional idle periods, we still value your donations. If this continues for an extended period of time, be sure to ask for help in the Forum because that’s not normal.​

[Boldface mine] What do you think an extended period of time is?
 
Last edited:
Have I dakked a firewall setting mebbe? I thought I enabled an exclusion when I installed the app, but maybe I didn't or didn't do it right.

I set an exception for private but not public networks, so I changed that. I'll now in ~ 33 mins when it calls home again.

Well, that wasn't it. Now it'll be another five hours before it even tries again.
 
Last edited:
The program doesn't look like it's really trying to connect. It just rolls over and starts a new countdown. There's no "time-out" going o that I can see.
 
*********************** Log Started 2016-01-10T16:38:36Z ***********************
16:38:36:************************* Folding@home Client *************************
16:38:36: Website: http://folding.stanford.edu/
16:38:36: Copyright: (c) 2009-2014 Stanford University
16:38:36: Author: Joseph Coffland <[email protected]>
16:38:36: Args:
16:38:36: Config: C:/ProgramData/FAHClient/config.xml
16:38:36:******************************** Build ********************************
16:38:36: Version: 7.4.4
16:38:36: Date: Mar 4 2014
16:38:36: Time: 20:26:54
16:38:36: SVN Rev: 4130
16:38:36: Branch: fah/trunk/client
16:38:36: Compiler: Intel(R) C++ MSVC 1500 mode 1200
16:38:36: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
16:38:36: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
16:38:36: Platform: win32 XP
16:38:36: Bits: 32
16:38:36: Mode: Release
16:38:36:******************************* System ********************************
16:38:36: CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
16:38:36: CPU ID: GenuineIntel Family 6 Model 23 Stepping 10
16:38:36: CPUs: 2
16:38:36: Memory: 3.71GiB
16:38:36: Free Memory: 2.64GiB
16:38:36: Threads: WINDOWS_THREADS
16:38:36: OS Version: 6.2
16:38:36: Has Battery: false
16:38:36: On Battery: false
16:38:36: UTC Offset: -6
16:38:36: PID: 2440
16:38:36: CWD: C:/ProgramData/FAHClient
16:38:36: OS: Windows 10 Pro
16:38:36: OS Arch: AMD64
16:38:36: GPUs: 0
16:38:36: CUDA: Not detected
16:38:36:Win32 Service: false
16:38:36:***********************************************************************
16:38:36:<config>
16:38:36: <!-- Slot Control -->
16:38:36: <power v='light'/>
16:38:36:
16:38:36: <!-- User Information -->
16:38:36: <team v='64'/>
16:38:36: <user v='JZL'/>
16:38:36:
16:38:36: <!-- Folding Slots -->
16:38:36: <slot id='0' type='CPU'/>
16:38:36:</config>
16:38:36:Trying to access database...
16:38:36:Successfully acquired database lock
16:38:36:Enabled folding slot 00: READY cpu:1
16:38:37:WU00:FS00:Connecting to 171.67.108.45:8080
16:38:38:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:38:38:WU00:FS00:Connecting to 171.67.108.204:80
16:38:39:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:38:39:ERROR:WU00:FS00:Exception: Could not get an assignment
16:38:40:WU00:FS00:Connecting to 171.67.108.45:8080
16:38:41:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:38:41:WU00:FS00:Connecting to 171.67.108.204:80
16:38:41:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:38:41:ERROR:WU00:FS00:Exception: Could not get an assignment
16:39:40:WU00:FS00:Connecting to 171.67.108.45:8080
16:39:40:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:39:40:WU00:FS00:Connecting to 171.67.108.204:80
16:39:41:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:39:41:ERROR:WU00:FS00:Exception: Could not get an assignment
16:41:17:WU00:FS00:Connecting to 171.67.108.45:8080
16:41:18:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:41:18:WU00:FS00:Connecting to 171.67.108.204:80
16:41:18:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:41:18:ERROR:WU00:FS00:Exception: Could not get an assignment
16:43:54:WU00:FS00:Connecting to 171.67.108.45:8080
16:43:55:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:43:55:WU00:FS00:Connecting to 171.67.108.204:80
16:43:55:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:43:55:ERROR:WU00:FS00:Exception: Could not get an assignment
16:48:09:WU00:FS00:Connecting to 171.67.108.45:8080
16:48:09:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:48:09:WU00:FS00:Connecting to 171.67.108.204:80
16:48:10:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:48:10:ERROR:WU00:FS00:Exception: Could not get an assignment
16:55:00:WU00:FS00:Connecting to 171.67.108.45:8080
16:55:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
16:55:00:WU00:FS00:Connecting to 171.67.108.204:80
16:55:01:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:55:01:ERROR:WU00:FS00:Exception: Could not get an assignment
17:06:05:WU00:FS00:Connecting to 171.67.108.45:8080
17:06:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
17:06:06:WU00:FS00:Connecting to 171.67.108.204:80
17:06:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:06:06:ERROR:WU00:FS00:Exception: Could not get an assignment
17:24:02:WU00:FS00:Connecting to 171.67.108.45:8080
17:24:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
17:24:03:WU00:FS00:Connecting to 171.67.108.204:80
17:24:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:24:04:ERROR:WU00:FS00:Exception: Could not get an assignment
17:53:04:WU00:FS00:Connecting to 171.67.108.45:8080
17:53:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
17:53:05:WU00:FS00:Connecting to 171.67.108.204:80
17:53:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:53:06:ERROR:WU00:FS00:Exception: Could not get an assignment
18:40:04:WU00:FS00:Connecting to 171.67.108.45:8080
18:40:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:40:04:WU00:FS00:Connecting to 171.67.108.204:80
18:40:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
18:40:05:ERROR:WU00:FS00:Exception: Could not get an assignment
19:56:04:WU00:FS00:Connecting to 171.67.108.45:8080
19:56:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
19:56:05:WU00:FS00:Connecting to 171.67.108.204:80
19:56:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
19:56:05:ERROR:WU00:FS00:Exception: Could not get an assignment
21:59:04:WU00:FS00:Connecting to 171.67.108.45:8080
21:59:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:59:04:WU00:FS00:Connecting to 171.67.108.204:80
21:59:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
21:59:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-01-11 *******************************
01:18:05:WU00:FS00:Connecting to 171.67.108.45:8080
01:18:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
01:18:05:WU00:FS00:Connecting to 171.67.108.204:80
01:18:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
01:18:05:ERROR:WU00:FS00:Exception: Could not get an assignment
04:12:31:24:127.0.0.1:New Web connection
06:40:04:WU00:FS00:Connecting to 171.67.108.45:8080
06:40:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:40:05:WU00:FS00:Connecting to 171.67.108.204:80
06:40:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
06:40:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-01-11 *******************************
12:40:05:WU00:FS00:Connecting to 171.67.108.45:8080
12:40:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
12:40:05:WU00:FS00:Connecting to 171.67.108.204:80
12:40:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
12:40:06:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-01-11 *******************************
18:40:05:WU00:FS00:Connecting to 171.67.108.45:8080
18:40:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:40:05:WU00:FS00:Connecting to 171.67.108.204:80
18:40:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
18:40:06:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-01-12 *******************************
00:40:05:WU00:FS00:Connecting to 171.67.108.45:8080
00:40:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:40:05:WU00:FS00:Connecting to 171.67.108.204:80
00:40:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
00:40:06:ERROR:WU00:FS00:Exception: Could not get an assignment
00:46:37:FS00:Paused
00:47:13:Saving configuration to config.xml
00:47:13:<config>
00:47:13: <!-- Slot Control -->
00:47:13: <power v='light'/>
00:47:13:
00:47:13: <!-- User Information -->
00:47:13: <team v='64'/>
00:47:13: <user v='JZL'/>
00:47:13:
00:47:13: <!-- Folding Slots -->
00:47:13: <slot id='0' type='CPU'>
00:47:13: <paused v='true'/>
00:47:13: </slot>
00:47:13:</config>
00:49:39:FS00:Unpaused
00:49:39:WU00:FS00:Connecting to 171.67.108.45:8080
00:49:40:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:49:40:WU00:FS00:Connecting to 171.67.108.204:80
00:49:40:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
00:49:40:ERROR:WU00:FS00:Exception: Could not get an assignment
 
Eureka!

I also posted my log at the F@H forum. Apparently there's a bug in the new (v. 7) client that can fool it on a first time run to thinking it's on a single core, and there aren't really single-core-compatible WU's left anymore.
Thus, the client has to be set for FULL cpu usage the first time, and mine wasn't because I'd wanted to start out the new comp on one of the lower settings. I set it to full, got a WU, then throttled back to monitor temps.
 
255K a day? Huh, wha? I'm only doing 400 or so. Are they giving you all the EASY PROTEINS?
 
No ****-- you must have some little Matrix-like computer farm goin' there. You're distributing your distributed computing?
 
No ****-- you must have some little Matrix-like computer farm goin' there. You're distributing your distributed computing?

mad points = GPU folding :D

Y'all remember the good ol days when How??? was kickin ass and our team was super active? You know things are different when I of all people are on the EOC stats first page :lol:

:fold:
 
Yeah, weren't we in the top 10 for a long time? Top 3? I guess there are a lot more teams these days.
 
Back
Top