I'm new to folding, but did prime search etc. before so not a newbie.
I installed client 6.23 via auto install. The server is up and accepting according to the status screen, but I can't get any work.
The last line is a change, but still no work.
Log file attached:
--- Opening Log file [December 17 13:47:13 UTC]
# Windows CPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\JJ\AppData\Roaming\Folding@home-x86
[13:49:09] - Ask before connecting: No
[13:49:09] - User name: JamesOrleff (Team 0)
[13:49:09] - User ID not found locally
[13:49:09] + Requesting User ID from server
[13:49:10] - Machine ID: 1
[13:49:10]
[13:49:10] Work directory not found. Creating...
[13:49:10] Could not open work queue, generating new queue...
[13:49:11] Initialization complete
[13:49:11] - Preparing to get new work unit...
[13:49:11] + Attempting to get work packet
[13:49:11] - Connecting to assignment server
[13:49:11] - Successful: assigned to (171.67.108.33).
[13:49:11] + News From Folding@Home: Welcome to Folding@Home
[13:49:11] Loaded queue successfully.
[13:49:12] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[13:49:21] + Attempting to get work packet
[13:49:21] - Connecting to assignment server
[13:49:21] - Successful: assigned to (171.67.108.33).
[13:49:21] + News From Folding@Home: Welcome to Folding@Home
[13:49:22] Loaded queue successfully.
[13:49:22] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
... identical entries for 3 hours deleted
[16:03:34] + Attempting to get work packet
[16:03:34] - Connecting to assignment server
[16:03:35] - Successful: assigned to (171.67.108.33).
[16:03:35] + News From Folding@Home: Welcome to Folding@Home
[16:03:35] Loaded queue successfully.
[16:03:35] - Attempt #12 to get work failed, and no other work to do.
Waiting before retry.
[16:22:54] Opening C:\Users\JJ\AppData\Roaming\Folding@home-x86\MyFolding.html...
If it's still doing it, stop the client and restart it. Sometimes it just needs that kick in the butt to get out of the loop. If that doesn't work, then the server is currently low on work units and you need to just sit and wait for new work to be available.
Do you have a firewall or anything else that may be blocking the program? I had an old version of an Internet Security Program that worked great it just didn't like to allow the new downloading of a WU at times by default even thou I had allowed it to run in it's pop-up that came up after installation. You may have to allow it to run through the firewall to get it to work.
I had to disable it to let the downloading of a new WU when that would happen. Then re-enable it after the WU started crunching. Mine was an older program so decided to upgrade instead of trying to mess with firewall rules which I'm not use too.
It must not have had work units available. I just waited and now it's working.
Just a thought, but I wonder how many potential workers the project loses because of things like this. It would be easy for a beginner to just abandon the project with a shrug after hours of nothing happening.
Maybe adding a bit of extra code to make sure a brand new account actually gets work would be good idea.
My F@H has had 11 attempts and it still hasn't got a new work unit yet what do i do?
this is the log file
23:07:50] + Attempting to send results [January 1 23:07:50 UTC]
[23:07:50] + Attempting to get work packet
[23:07:55] - Couldn't send HTTP request to server
[23:07:55] + Could not connect to Work Server (results)
[23:07:55] (171.64.65.79:8080)
[23:07:55] + Retrying using alternative port
[23:07:55] - Couldn't send HTTP request to server
[23:07:55] + Could not connect to Work Server (results)
[23:07:55] (171.64.65.79:80)
[23:07:55] - Error: Could not transmit unit 01 (completed January 1) to work server.
[23:07:55] + Attempting to send results [January 1 23:07:55 UTC]
[23:07:55] - Couldn't send HTTP request to server
[23:07:55] + Could not connect to Work Server (results)
[23:07:55] (171.67.108.26:8080)
[23:07:55] + Retrying using alternative port
[23:07:55] - Couldn't send HTTP request to server
[23:07:55] + Could not connect to Work Server (results)
[23:07:55] (171.67.108.26:80)
[23:07:55] Could not transmit unit 01 to Collection server; keeping in queue.
[23:07:55] - Connecting to assignment server
[23:07:55] - Couldn't send HTTP request to server
[23:07:55] + Could not connect to Assignment Server
[23:07:55] - Couldn't send HTTP request to server
[23:07:55] + Could not connect to Assignment Server 2
[23:07:55] + Couldn't get work instructions.
[23:07:55] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.
"Could not connect ti the Assignment Server" or "...2" means either that Stanford has gone entirely off-line or you've got something blocking your connection.
