I have two machines that can't seem to get new work units. This is the log file of my machine at home:

--- Opening Log file [August 1 21:47:04]

# Windows Graphical Edition ###################################################

###############################################################################

Folding@Home Client Version 5.03

http://folding.stanford.edu

###############################################################################

###############################################################################

Launch directory: C:\Program Files\Folding@Home

[21:47:04] - Ask before connecting: No

[21:47:04] - Use IE connection settings: Yes

[21:47:04] - User name: Tiptronic (Team 42567)

[21:47:04] - User ID: 55FEC2157046FE79

[21:47:04] - Machine ID: 1

[21:47:04]

[21:47:05] Loaded queue successfully.

[21:47:05] Initialization complete

[21:47:05] + Benchmarking ...

[21:47:08] - Preparing to get new work unit...

[21:47:08] + Attempting to get work packet

[21:47:09] - Connecting to assignment server

[21:48:07] Opening

http://vspx27.stanford.edu/cgi-bin/main.py?qtype=userpage&username=Tiptronic

...

[21:48:54] - Successful: assigned to (171.64.122.133).

[21:48:54] + News From Folding@Home: Welcome to Folding@Home

[21:48:54] Loaded queue successfully.

[21:48:54] - Error: Attempt #1 to get work failed, and no other work to do.

Waiting before retry.

[21:49:06] + Attempting to get work packet

[21:49:06] - Connecting to assignment server

[21:49:08] - Successful: assigned to (171.64.122.133).

[21:49:08] + News From Folding@Home: Welcome to Folding@Home

[21:49:08] Loaded queue successfully.

[21:49:09] - Error: Attempt #2 to get work failed, and no other work to do.

Waiting before retry.

[21:49:31] + Attempting to get work packet

[21:49:31] - Connecting to assignment server

[21:49:32] - Successful: assigned to (171.64.122.133).

[21:49:32] + News From Folding@Home: Welcome to Folding@Home

[21:49:32] Loaded queue successfully.

[21:49:33] - Error: Attempt #3 to get work failed, and no other work to do.

Waiting before retry.

[21:50:07] + Attempting to get work packet

[21:50:07] - Connecting to assignment server

[21:50:08] - Successful: assigned to (171.64.122.133).

[21:50:08] + News From Folding@Home: Welcome to Folding@Home

[21:50:08] Loaded queue successfully.

[21:50:08] - Error: Attempt #4 to get work failed, and no other work to do.

Waiting before retry.

[21:50:50] + Attempting to get work packet

[21:50:50] - Connecting to assignment server

[21:50:51] - Successful: assigned to (171.64.122.133).

[21:50:51] + News From Folding@Home: Welcome to Folding@Home

[21:50:51] Loaded queue successfully.

[21:50:51] - Error: Attempt #5 to get work failed, and no other work to do.

Waiting before retry.

[21:52:23] + Attempting to get work packet

[21:52:23] - Connecting to assignment server

[21:52:24] - Successful: assigned to (171.64.122.133).

[21:52:24] + News From Folding@Home: Welcome to Folding@Home

[21:52:24] Loaded queue successfully.

[21:52:27] - Error: Attempt #6 to get work failed, and no other work to do.

Waiting before retry.

[21:55:11] + Attempting to get work packet

[21:55:11] - Connecting to assignment server

[21:55:12] - Successful: assigned to (171.64.122.133).

[21:55:12] + News From Folding@Home: Welcome to Folding@Home

[21:55:13] Loaded queue successfully.

[21:55:13] - Error: Attempt #7 to get work failed, and no other work to do.

Waiting before retry.

[22:00:42] + Attempting to get work packet

[22:00:42] - Connecting to assignment server

[22:00:43] - Successful: assigned to (171.64.122.133).

[22:00:43] + News From Folding@Home: Welcome to Folding@Home

[22:00:43] Loaded queue successfully.

[22:00:44] - Error: Attempt #8 to get work failed, and no other work to do.

Waiting before retry.

I also have another one running the console version that is having the same issue. Other machines are OK, and seem to be sending results and getting new units without problems.

Any ideas chaps?

All the Best

Chris

My laptop does this all the time :thumbdwn:

I switch it off and re-start it. It then re-connects, sends the completed WU and gets a new WU to work on

Oh, and I'm not a chap

I always found a good reboot and a kick sorted this kind of thing out. Never figured out why - was usually due to my dongle dropping the connection.

Oh, and I am a chap.

Sorry Tinkerbell, no offence intended, honest.

This error keeps happening regardless of restarts, so that doesn't solve it in either of these cases.

Looking again at the log file on the console version, that one connects to the server, but then says it could not send HTTP request to the server. The finished units have already been sent, they don't seem to be able to get a new unit to work on.

Still puzzled!:confused:

Thanks

Chris

Perhaps they are having server problems, how long has the machine been idle now.

Perhaps they are having server problems, how long has the machine been idle now.

Hi Manny

My one at home (graphical) has been like this for well over week now, and the other one (console) since Friday I think.

My first thought was server problems, but then wouldn't the other machines have the same issue? The other machines are sending and receiving work without a problem.

Maybe I will have to uninstall and reinstall it on those two machines?

All the Best

Chris

I am getting it all the time, it gets very infuriating as i had a box sat for ages doing no work due to this.

I get errors from the same IP address also :S

I did a reinstall, it worked once then stopped :(

Found an answer!! Decided to have a look on the forum on Stanford, and somebody had posted with the same issue.

This is the response:

Currently the .133 server has run out of WUs, and at the moment we don't know when that will change.

If your machine does not need to run deadlineless WUs (given that it's a G5 it shouldn't need to), you can turn "Request WUs with no deadlines" to OFF, which will allow you to connect to some of the regular work servers which have plenty of WUs to run.

So cos we've all got them set to accept deadlined work, it won't go to another server until that option is changed.

All the Best

Chris

Found an answer!! Decided to have a look on the forum on Stanford' date=' and somebody had posted with the same issue.

This is the response:

[indent']Currently the .133 server has run out of WUs, and at the moment we don't know when that will change.

If your machine does not need to run deadlineless WUs (given that it's a G5 it shouldn't need to), you can turn "Request WUs with no deadlines" to OFF, which will allow you to connect to some of the regular work servers which have plenty of WUs to run.[/indent]

So cos we've all got them set to accept deadlined work, it won't go to another server until that option is changed.

All the Best

Chris

Scrub that!

There appears to be contradictory information on the Folding site.

When I got home last night, I checked my machine and found it was already set for deadlineless. So had a deeper look at the Stanford Folding forum, and it would appear that the assignment servers have run out of deadlineless units.

So that means to keep folding, your machines need to be set to standard units.

All the Best

Chris

UPDATE: Changed the preferences on my machine (graphical) at home to no preference, and it immediately tried another server and downloaded a new unit.

Just need to do the same on the console machine.