129.74.246.143 Upload timeout not long enough

[M4rt1n]

I have a WU which is taking >30 minutes to upload due to its size 16.72MB and my slow upload speed of 96k.

Is it possible to increase the timeout please?

[bruce]

What project is generating an upload package that's 16.72MB? Please post the portion of the log where it says what project is being uploaded and how big it is going to be. (We don't need all the details after that.) What numbers does your ISP give for your line-speed?

Have you altered the setting for packet-size={small | normal | big | (a numerical value)}?

We have two problems. One is to somehow take care of the current WU and another is to revisit the Pande Group's plan for slow uploads. The default server timeout has been 15 minutes and in a few instances it has been increased to 30 minutes but it sounds like you should be seeking smaller WUs. We may have to talk to the project owners and work out a better plan for future assignments.

[M4rt1n]

Here's the log entries as requested.
09:17:11:WU00:FS00:Upload 80.01%
09:17:11:WARNING:WU00:FS00:Exception: Failed to send results to work server: Transfer failed
09:17:11:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:7041 run:0 clone:797 gen:0 core:0xa4 unit:0x000000040001329c51450018d37639a0
09:17:11:WU00:FS00:Uploading 16.72MiB to 129.74.246.143

Current line speed is 1,152,000 down and 96,000 up.

Packet size not altered.

Grateful for any suggestions.

[M4rt1n]

Does anyone have any suggestions as to how I remove the WU that is failing to upload please? I now have the same issue on another PC.

TIA

[bruce]

Ideally, the FAH Client should discard the WU after the WU expires, but I don't know if that actually works correctly. It's a fairly rare condition.

To manually discard the WU from a Windows installation, stop FAHClient. Open the data directory, and inside of a directory called work, you will find a subdirectory for each WU that's in the queue. In the case shown above, it says 09:17:11:WU00:FS00 so it's WU 00 in directory 00. (That number will vary.) Delete that directory. Restart FAHClient. Check your connection first to make sure it's operating at the expected speed. You do not want to delete WUs until you're certain that the upload will never succeed.

Please post the same log information from the other WU on the other machine.

[7im]

I want to see the sections of the log where the client is trying to upload.

At 96000 Kbps, you should be able to upload more than 10 GB in 15 minutes.

[Joe_H]

At 96000 Kbps, you should be able to upload more than 10 GB in 15 minutes.

Agree with 7im about seeing the log for a failed upload, though the estimate is a bit off, MB not GB in that time frame. With DSL overhead, about 9-10 MB should upload in 15 minutes and probably closer to 9.

As for settings of small, normal or big, when I tested those I found they had no discernible effect on which WU's were assigned to SMP folding clients. I think they only were checked by the servers for uniprocessor projects. If that is the case, perhaps they can be made active on the servers for SMP assignments.

[M4rt1n]

At 96000 Kbps, you should be able to upload more than 10 GB in 15 minutes.

I can only dream of those speeds... 96000 is bits per second or 96Kbps. Hopefully that puts it into perspective and sorry for any confusion

I will follow bruce's suggestion and see how I get on.

Thanks for the feedback.

[M4rt1n]

Ideally, the FAH Client should discard the WU after the WU expires, but I don't know if that actually works correctly. It's a fairly rare condition

You were correct Bruce, when I checked I found this in the log

18:11:51:WARNING:WU00:FS00:Past final deadline 2013-09-21T18:11:50Z, dumping

and the WU had disappeared.