Unable to download new WU

[Joe_H]

@kwerboom please turn off the verbosity setting. It makes it really hard to figure out what's going on.

@bruce Verbosity goes 1-5. I set it to 5 for maximum information when I installed the 7.1.38 beta. What should verbosity be set at?

Please leave the logging verbosity set to the default of 3. Higher levels are only useful in a few, extremely rare cases. Verbosity level 3 gives the information about any setting that is different from the default client settings.

[7im]

Verbosity = 3 is the default setting. Use that one.

[FaaR]

Had a GPU slot log that looked like this for hours and hours:
(No extra settings anywhere, just default stuff you get when doing a clean install. No preference regarding projects/type of work units, and so on.)

Code: Select all

22:52:06:WU00:FS01:Connecting to 171.67.108.204:80
22:52:07:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
22:52:07:ERROR:WU00:FS01:Exception: Could not get an assignment
23:39:05:WU00:FS01:Connecting to 171.67.108.45:80
23:39:05:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
23:39:05:WU00:FS01:Connecting to 171.67.108.204:80
23:39:06:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:39:06:ERROR:WU00:FS01:Exception: Could not get an assignment

Then I came here, looking for help, and it seems other people have been having the same problems. I set "client-type" "advanced" in the client settings, re-started FaH, and it immediately fetched a new work unit for me. Weird.

Anyway, where can I read up on what client-type advanced and max-packet-size big really do? Can I enter both at once? Should I, is there a point to it or is it even bad?

Thanks for assistance.

[davidcoton]

It's in the read-mes somewhere -- try this
max-packet-size=big and client-type=advanced will work together.
Advanced will give you slightly less well tested projects, with a slightly higher risk of failures. That should be the only downside.

[bruce]

@kwerboom please turn off the verbosity setting. It makes it really hard to figure out what's going on.

@bruce Verbosity goes 1-5. I set it to 5 for maximum information when I installed the 7.1.38 beta. What should verbosity be set at?

Removing the verbosity setting will reset it to the default, which is 3.

I've never found anything useful at higher values.

[FaaR]

It's in the read-mes somewhere -- try this
max-packet-size=big and client-type=advanced will work together.
Advanced will give you slightly less well tested projects, with a slightly higher risk of failures. That should be the only downside.

Thanks a lot! Really appreciate the help.

Maybe I'm imagining things, but the fans of my R9 390X seems to roar louder after switching to client-type advanced... Maybe it's actually working harder, folding these WUs?

[bruce]

It's probably working harder, but every project is a little different. It's not a direct function of "advanced" although that will often give you different projects.

[kwerboom]

Please leave the logging verbosity set to the default of 3. Higher levels are only useful in a few, extremely rare cases. Verbosity level 3 gives the information about any setting that is different from the default client settings.

Thanks for letting me know. I reset it to 3.

It's in the read-mes somewhere -- try this
max-packet-size=big and client-type=advanced will work together.
Advanced will give you slightly less well tested projects, with a slightly higher risk of failures. That should be the only downside.

I did what you recommended with max-packet-size and client-type and my F@H started working again when I restarted. Thank you.

[djay86]

Setting client-type value advanced in the expert tab solved the issue for me.

[btupsx]

Looks like the 9201s are being accepted without rejection now. I let one slot complete, and the server accepted. Thank for letting all of us know, Stanford....

[arkaine23]

150+ Windows 6.34 SMP clients using -smp - forceasm and accepting big packets. I set one to verbose mode and snipped some of the log.

Same thing happened in October and took weeks to return to normal. All of these i5's are having issues getting work again, such that production is around 1/6th of what it is normally (1.7M PPD down to 300K PPD). I have no problem opening http://assign.standford.edu:8080 or http://assign.standford.edu:80 in a browser.


[22:36:22] Loaded queue successfully.
[22:36:22] - Preparing to get new work unit...
[22:36:22] - Autosending finished units... [December 14 22:36:22 UTC]
[22:36:22] Cleaning up work directory
[22:36:22] Trying to send all finished work units
[22:36:22] + Attempting to get work packet
[22:36:22] + No unsent completed units remaining.
[22:36:22] Passkey found
[22:36:22] - Autosend completed
[22:36:22] - Will indicate memory of 3917 MB
[22:36:22] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 7
[22:36:22] - Connecting to assignment server
[22:36:22] Connecting to http://assign.stanford.edu:8080/
[22:36:23] Posted data.
[22:36:23] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[22:36:23] + Couldn't get work instructions.
[22:36:23] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[22:36:31] + Attempting to get work packet

Repeated hundreds of times.


Interestingly after a few client restarts, and a couple of failures to get work, this particular client got a WU.

[22:45:18] - Connecting to assignment server
[22:45:18] Connecting to http://assign.stanford.edu:8080/
[22:45:18] Posted data.
[22:45:18] Initial: 8F80; - Successful: assigned to (128.143.199.97).
[22:45:18] + News From Folding@Home:
[22:45:18] Loaded queue successfully.
[22:45:18] Sent data
[22:45:18] Connecting to http://128.143.199.97:8080/
[22:45:20] Posted data.
[22:45:20] Initial: 0000; - Receiving payload (expected size: 1988324)
[22:45:22] - Downloaded at ~970 kB/s
[22:45:22] - Averaged speed for that direction ~818 kB/s
[22:45:22] + Received work.
[22:45:22] + Closed connections


In general though, all of these clients are suffering 80+% downtime just trying to get work. The production started to fall around 12/4.

[7im]

Only a few of the work servers still support the older v6 client, and the WU availability will continue to decline for v6.
Most servers require V7.29 or above. Please consider an upgrade to the latest V7.4.4 client.

[klasseng]

FAH 7.4.4 on a Late 2014 Mac Pro:

22:07:09:WU00:FS01:Connecting to 171.67.108.45:8080
22:07:10:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
22:07:10:WU00:FS01:Connecting to 171.67.108.204:80
22:07:11:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
22:07:11:ERROR:WU00:FS01:Exception: Could not get an assignment

[toTOW]

I think this is related : viewtopic.php?p=282322#p282322

How many threads do you allow for your SMP slot ?

[_r2w_ben]

The projects on the server mentioned in toTow's post (128.252.203.2) support 1-4, 6, or 8 cores. You may need to run 2 slots with half the cores.