Folding Forum

I can successfully connect but get no work unit. This has been going on for over 12 hours as of 042820111501Z.

Here is a representative log entry.

Launch directory: C:\Folding @ Home\Console 1
Executable: C:\Folding @ Home\Console 1\Folding@home-Win32-x86.exe
Arguments: -verbosity 9

[14:55:50] - Ask before connecting: No
[14:55:50] - User name: LonePalm (Team 36120)
[14:55:50] - User ID: [redacted]
[14:55:50] - Machine ID: 1
[14:55:50]
[14:55:50] Loaded queue successfully.
[14:55:50] - Preparing to get new work unit...
[14:55:50] - Autosending finished units... [April 28 14:55:50 UTC]
[14:55:50] + Attempting to get work packet
[14:55:50] Trying to send all finished work units
[14:55:50] - Will indicate memory of 6135 MB
[14:55:50] + No unsent completed units remaining.
[14:55:50] - Detect CPU.[14:55:50] - Autosend completed
Vendor: GenuineIntel, Family: 6, Model: 14, Stepping: 5
[14:55:50] - Connecting to assignment server
[14:55:50] Connecting to http://assign.stanford.edu:8080/
[14:55:51] Posted data.
[14:55:51] Initial: 43AB; - Successful: assigned to (171.67.108.42).
[14:55:51] + News From Folding@Home: Welcome to Folding@Home
[14:55:51] Loaded queue successfully.
[14:55:51] Connecting to http://171.67.108.42:8080/
[14:55:51] Posted data.
[14:55:51] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[14:55:51] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.

lonepalm@att.net

Welcome to the forum, http://171.67.108.42:8080/

Has this always been server 171.67.108.42? I see only one attempt to connect and in 12 hours, there should be many, many more connection attempts, normally including connection attempts to other servers.

Were you running beta or adv?

win32-x86-623

gwildperson wrote:Welcome to the forum, http://171.67.108.42:8080/

Has this always been server 171.67.108.42? I see only one attempt to connect and in 12 hours, there should be many, many more connection attempts, normally including connection attempts to other servers.

I had just restarted the client with verbosity set to 9. I have three clients that can't get work at the moment and all three are trying to get work from 171.67.108.42 and no other. I compared the logs.

What I posted above is representative of all the log files.

Hm, this is using the advmethods flag? It seems the server may have been a bit low on jobs, I've increased them now, we'll see if that helps. It's strange that it only tries to connect to 171.67.108.42, it's supposed to start trying other servers if one keeps failing

I restarted the clients and got WUs immediately.

Thanks.