F@H: Problem uploading results

[MechEng]

For two or three days now, I have been getting this on one of my PC's:

[22:47:35] + Attempting to get work packet
[22:47:35] - Will indicate memory of 255 MB.
[22:47:35] - Connecting to assignment server
[22:47:35] - Successful: assigned to (171.64.122.112).
[22:47:35] + News From Folding@Home: Welcome to Folding@Home
[22:47:36] Loaded queue successfully.
[22:47:36] Error: Got status code 503 from server
[22:47:36] + Could not connect to Work Server
[22:47:36] - Error: Attempt #7 to get work failed, and no other work to do.
Waiting before retry.

Anyone knows what error code 503 is?

When I look here it seems that the server is heavily loaded, but fully functional.
I've had this problem before, but not for so long.

 

[MechEng]

I've found out here that the server is having some problems and needs to be rebootet, which will happen sometime today.

The machine is having some trouble and needs to be rebooted. I'll do it at some point today.

Thank you for tthe patience!
Young Min

 

[GLeeM]

One of the problems with choosing to crunch deadlineless WUs is if the server is down, you are sitting still in the water.

Do you cache up to ten WUs? That might help keep the PC busy for a while when the server is down.

Or you could change the configuration to do regular WUs until the "timeless" WU server is back up.

 

[MechEng]

Originally posted by: GLeeM
One of the problems with choosing to crunch deadlineless WUs is if the server is down, you are sitting still in the water.

Do you cache up to ten WUs? That might help keep the PC busy for a while when the server is down.

Or you could change the configuration to do regular WUs until the "timeless" WU server is back up.

How should I cache them???
Manually with different folders or are you thinking of the "Minimize networking -- get and submit work in bathces" setting?
The latter I have never used.

For the moment I have the PC running SETI Classic, until the WU-server is up again. The PC I have running timeless WU's is a rather slow P3-550, and I won't run the larger WU's due to the time and memory-ressources they need.

 

[GLeeM]

Originally posted by: MechEng
How should I cache them???
Manually with different folders or are you thinking of the "Minimize networking -- get and submit work in bathces" setting?
The latter I have never used.

For the moment I have the PC running SETI Classic, until the WU-server is up again. The PC I have running timeless WU's is a rather slow P3-550, and I won't run the larger WU's due to the time and memory-ressources they need.

Yeah, with the Minimize networking setting. The problem with that setting is that it caches ten (eight?) WUs and a slower computer can't finish the last few before they would be sent out again. You still get points, but you might be doing duplicate work.

Your solution is good, keep crunching

 

[Soggys1stBrat]

Hello I'm new to this distibuted computing thing. I've been running S@H for a year now, but with all the talk about the classic being turned off in favor of boinc, I'm trying to see waht all the other stuff is that the TEAM is into like the F@H. What is F@H and what does it do?

 

[Spacehead]

Originally posted by: Soggys1stBrat
Hello I'm new to this distibuted computing thing. I've been running S@H for a year now, but with all the talk about the classic being turned off in favor of boinc, I'm trying to see waht all the other stuff is that the TEAM is into like the F@H. What is F@H and what does it do?

This should answer a few of your questions.

 

[MechEng]

Originally posted by: GLeeM

Originally posted by: MechEng
How should I cache them???
Manually with different folders or are you thinking of the "Minimize networking -- get and submit work in bathces" setting?
The latter I have never used.

For the moment I have the PC running SETI Classic, until the WU-server is up again. The PC I have running timeless WU's is a rather slow P3-550, and I won't run the larger WU's due to the time and memory-ressources they need.

Yeah, with the Minimize networking setting. The problem with that setting is that it caches ten (eight?) WUs and a slower computer can't finish the last few before they would be sent out again. You still get points, but you might be doing duplicate work.

Your solution is good, keep crunching

Thanks for the help...