Folding Forum

Hi everyone,

I'm a new member of the folding@home community. While my folding client is relatively stable, I have a problem with collection server 0.0.0.0
I've finished my current WU but it's unable to send the results to an aforementioned server.
Does anyone have any idea what to do in such situation?

Thanks for any tips,
Mike

If no CS is defined, the upload only goes to the WS. Uploads always first get tried to the WS.

Also it always helps if you at least mention the server you having problem with.
Yes as a new member you could have restrictions on pasting URL:s, but at least you could write down the server name (first part of the result if in a cmd window paste "nslookup <ip address>"

If this turns out to be a problem you have with the "plfah1-x" Work servers, then those seem to have been restarted about 1hour ago, and seem to be working now.
Restart you client if this is the Work Server you having problem with (or wait for the next attempt, could be hours if more than a day has passed with an error, and hope the server wont go down again)

So in summary: a Collection server with the address of 0.0.0.0 is not going to be used, but instead the upload will go to the Work Server (as Joe_H said)
Not much you can do if you find yourself in a situation like this, but to wait that the Work Server will be up again (serverstats)

Thanks for help. I have one more question: what happens when the WU is being sent to the WS instead of CS?
Does it count as a completed WU?

The response to this topic will explain the normal steps involved viewtopic.php?f=16&t=34205&p=324506 … it is actually the WS that needs the work back - a CS is simply an intermediary offload should WS be to busy to receive returning WUs it then forwards them to the WS as/when it has capacity to deal with them … these steps would be incurred in between the two steps below:

Work Server acknowledges the connection attempt
Completed WU is successfully transferred to the Work Server

If there is no CS then the client simply keeps retrying the WS until it gets a chance to upload.

Neil-B wrote:The response to this topic will explain the normal steps involved viewtopic.php?f=16&t=34205&p=324506 … it is actually the WS that needs the work back - a CS is simply an intermediary offload should WS be to busy to receive returning WUs it then forwards them to the WS as/when it has capacity to deal with them … these steps would be incurred in between the two steps below:

Work Server acknowledges the connection attempt
Completed WU is successfully transferred to the Work Server

If there is no CS then the client simply keeps retrying the WS until it gets a chance to upload.

Thanks for that, I have edited my reply and included a sentence about it.