View Full Version : another install issue
This is the error I just got:
Error: Attempt #1 to get work failed, and no other work to do. Waiting before retry.
I just threw a graphics card into my E6400 rig so I could get FOLDing installed and running while I wont be using it. Is this something on my end that needs to be fixed or is it because of servers?
WarriorII
02-02-07, 12:19 PM
Which client are you using?
Wedos one click?
SMP?
Graphics?
Service install?
Windows or Linux?
Do you have any firewall software blocking it? Have you tried pinging the Stanford server? The IP should be in the log.
My anti-virus was disabled. assign.stanford.edu is the only adress that I can ping and I get an average of 57. Here is exactly what it says:
"[18:43:32] + Attempting to get work packet
[18:43:32] - Will indicate memory of 2047 MB.
[18:43:32] - Connecting to assignment server
[18:43:32] Connecting to http://assign.stanford.edu:8080/
[18:43:32] Posted data.
[18:43:32] Initial: 0000; - Successful: assigned to (0.0.0.0).
[18:43:32] + News From Folding@Home: Welcome to Folding@Home
[18:43:32] Work Unit has an invalid address.
[18:43:32] - Error: Attempt #10 to get work failed, and no other work to do.
Waiting before retry."
[18:43:32] Initial: 0000; - Successful: assigned to (0.0.0.0).
Something is up there. DNS jiggery pokery?
The Assignment Server now defaults to 0.0.0.0 if there is a problem or there is no work. What does client.cfg look like? This is the type error you'd get if you edited client.cfg to change the clienttype to type=2 (deadlineless servers are all off line). Perhaps now you'd get the same error if you edited client.cfg with wordpad.
Here is what client.cfg has in it. The only thing I had to change was my username. I'm using notepad to view and edit.
[settings]
username=inkfx
team=32
asknet=no
machineid=1
local=362
bigpackets=no
[http]
active=no
host=localhost
port=8080
usereg=no
[clienttype]
type=1
[core]
priority=0
cpuusage=100
disableassembly=no
checkpoint=15
ignoredeadlines=no
[power]
battery=no
harlam357
02-02-07, 03:28 PM
Try metapad (http://www.liquidninja.com/metapad/). Open the client.cfg and make sure you didn't mess up and carriage returns. Metapad will read a unix/bin file so you can read it.
If the client.cfg looks like the above in notepad, you bork'd it. Pull the one from the wedo one-click file and re-edit it in metapad.
Pull the one from the wedo one-click file and re-edit it in metapad.
I tried that and I still get the same error.
You might want to edit local to zero if you want the log to accurately reflect how many WUs you've completed.
Heres the standard connectivity test:
What happens when you click the following links?
http://www.stanford.edu/group/pandegroup/
http://assign2.stanford.edu/
http://171.65.103.100
http://assign.stanford.edu:8080/
http://171.65.103.160
You should get the Pandegroup site on the first, and in IE a screen saying OK on the last four. If you don't get the OK, something is blocking the connection.
Well im not on my C2D now. I was using my dads graphics card and was hoping to get it fixed within that time. When I get another chance at using his card I'll try those things.
Junebug
02-02-07, 05:04 PM
I am getting the same thing on one of my clients right now. I was able to sneaker-net two WU's just now, but yet my farm client has been trying for 45 minutes so far with no luck. It looks like the servers are squirrelly again ( perfect Friday night situation). Sometimes it gets 0.0.0.0, sometimes a real server, but it can't seem to get work.
[21:51:29] + Attempting to send results
[21:51:29] - Reading file work/wuresults_08.dat from core
[21:51:29] (Read 1133637 bytes from disk)
[21:51:29] Connecting to http://171.65.103.160:8080/
[21:51:54] Posted data.
[21:51:54] Initial: 0000; - Uploaded at ~42 kB/s
[21:51:55] - Averaged speed for that direction ~25 kB/s
[21:51:55] + Results successfully sent
[21:51:55] Thank you for your contribution to Folding@Home.
[21:51:55] + Number of Units Completed: 170
[21:51:59] Trying to send all finished work units
[21:51:59] + No unsent completed units remaining.
[21:51:59] - Preparing to get new work unit...
[21:51:59] + Attempting to get work packet
[21:51:59] - Will indicate memory of 494 MB
[21:51:59] - Connecting to assignment server
[21:51:59] Connecting to http://assign.stanford.edu:8080/
[21:51:59] Posted data.
[21:51:59] Initial: 0000; - Successful: assigned to (0.0.0.0).
[21:51:59] + News From Folding@Home: Welcome to Folding@Home
[21:51:59] Work Unit has an invalid address.
[21:51:59] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[21:52:16] + Attempting to get work packet
[21:52:16] - Will indicate memory of 494 MB
[21:52:16] - Connecting to assignment server
[21:52:16] Connecting to http://assign.stanford.edu:8080/
[21:52:16] Posted data.
[21:52:16] Initial: 0000; - Successful: assigned to (0.0.0.0).
[21:52:16] + News From Folding@Home: Welcome to Folding@Home
[21:52:16] Work Unit has an invalid address.
[21:52:16] - Error: Attempt #2 to get work failed, and no other work to do.
....
[22:14:18] + Attempting to get work packet
[22:14:18] - Will indicate memory of 494 MB
[22:14:18] - Connecting to assignment server
[22:14:18] Connecting to http://assign.stanford.edu:8080/
[22:14:19] Posted data.
[22:14:19] Initial: 40AB; - Successful: assigned to (171.64.65.58).
[22:14:19] + News From Folding@Home: Welcome to Folding@Home
[22:14:19] Loaded queue successfully.
[22:14:19] Connecting to http://171.64.65.58:8080/
[22:14:19] Posted data.
[22:14:19] Initial: 0000; + Could not connect to Work Server
[22:14:19] - Error: Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[22:35:43] + Attempting to get work packet
[22:35:43] - Will indicate memory of 494 MB
[22:35:43] - Connecting to assignment server
[22:35:43] Connecting to http://assign.stanford.edu:8080/
[22:35:44] Posted data.
[22:35:44] Initial: 0000; - Successful: assigned to (0.0.0.0).
[22:35:44] + News From Folding@Home: Welcome to Folding@Home
[22:35:44] Work Unit has an invalid address.
[22:35:44] - Error: Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.