Isolated folding problem

[freakitchen]

Hi folks.

Got a bit of a problem with my 'second system''s folding client (specs in sig). Upon finishing a work unit, the console client sends the wu successfully. It then does the following:

Preparing to Get new work unit
Attempting to get work packet
Connecting to assignment server
Successful: assigned to (171.65.103.158)
News from Folding@Home: Welcome to Folding@Home
Loaded queue successfully.

And there it sticks. I'm not sure whether at this point it's actually got a new WU, but it hangs there doing no work (CPU on 0%). If i close and restart the client at this point, it gets a new work unit just fine, but obviously this creates periods of idling for this machine.

Any ideas guys? There's no special settings on this client, everything left default.

Cheers,

FK

*************************

Edit:

It gets stranger. The client stayed at that point for exactly an hour. Then, it kicked into life, saying:

Could not get Work unit data from Work Server
-Error: Attempt #1 to get work failed, and no other work to do. Waiting before retry.

Then it immediately tried again, at which point it got a work unit successfully.

Normally I'd put this down to failing to connect to the assignment server - but whenever I've had that issue before, the client has tried to connect every 10-15 minutes or so. Seems strange that if this was the problem, it would wait for exactly an hour without any output.

[pam123]

It doesn't seem to have anything to do with your end of the deal.
I'd put this down to server problems of one sort or another.

[Panama Red]

If it's server related, this link may help. It shows the real time status of Folding servers.

http://vspx27.stanford.edu/serverstat.html

[freakitchen]

Yeah, I agree with ya Pam - though I was by no means sure of that 'till the client got the WU after an hour of waiting. I'd always managed to catch it and restart when it played up previously, so I'd never left it waiting long enough.

Cheers for that list, PR, should prove useful

FK