Folding Forum

There always were (atleast for me) 2 minutes of delay after the completed work is sent. According to your log, the client asked for new WU immediately after sending the finished one, no wonder those two servers didnt have time to sync up. The question is why didnt your client wait those 2 mins.

^w^ing wrote:There always was (atleast for me) 2 minutes of delay after the completed work is sent. According to your log, the client asked for new WU immediately after sending the finished one, no wonder those two servers didnt have time to sync up. The question is why didnt your client wait those 2 mins.

As I started to respond to this, I realized what a specious post it was. I didn't write the software, I just run it. Re-read the log file.

sick willie wrote:As I started to respond to this, I realized what a specious post it was. I didn't write the software, I just run it. Re-read the log file.

Of course I know that, I dont blame you for what your client did Sorry if it sounded like that. I was just pointing out that the client didnt proceed as it normally do. Maybe because first attempts to send that unit didnt succeed.

sick willie wrote:[09:53:13] + Could not connect to Work Server (results) / (171.64.65.64:8080)

[09:53:15] + Could not connect to Work Server (results) / (171.64.65.64:8080)

[09:53:15] Connecting to http://171.64.122.86:8080/
[09:57:46] + Results successfully sent

[09:57:46] Connecting to http://171.64.65.64:8080/
[09:58:00] - Downloaded at ~587 kB/s

You're right . . . I didn't see it.

Failed to connect to server .64 at 09:53:13 and again at 09:53:15 so reverted to the Collection server.
Successfully connected to server .64 at 09:58:00

It would've been nice to have been acknowledged with an answer. But, then, I guess the absence of an answer is an answer, in and of itself.

We've been concentrating on making sure this doesn't happen again. We'll look into the feasibility of a manual stats recredit in this situation.

PS We've done a manual recredit.

Thank you.