Page 1 of 1

Project 7505 (0,2,19) upload fails

Posted: Mon Sep 26, 2011 8:10 am
by davidcoton
This upload (4MB+) is regularly timing out at 15 minutes

Please remember us Brits with ghastly slow ADSL upload !

Regards,

David

Code: Select all

[06:50:20] Completed 365000 out of 500000 steps  (73%)
[06:54:51] - Couldn't send HTTP request to server
[06:54:51] + Could not connect to Work Server (results)
[06:54:51]     (128.143.199.97:8080)
[06:54:51] + Retrying using alternative port
[06:54:51] Connecting to http://128.143.199.97:80/
[06:55:01] - Couldn't send HTTP request to server
[06:55:01] + Could not connect to Work Server (results)
[06:55:01]     (128.143.199.97:80)
[06:55:01] - Error: Could not transmit unit 09 (completed September 25) to work server.
[06:55:01] - 3 failed uploads of this unit.


[06:55:01] + Attempting to send results [September 26 06:55:01 UTC]
[06:55:01] - Reading file work/wuresults_09.dat from core
[06:55:01]   (Read 41690416 bytes from disk)
[06:55:01] Connecting to http://130.237.165.141:8080/
[06:57:37] Completed 370000 out of 500000 steps  (74%)
[07:04:07] Completed 375000 out of 500000 steps  (75%)
[07:10:02] - Couldn't send HTTP request to server
[07:10:02] + Could not connect to Work Server (results)
[07:10:02]     (130.237.165.141:8080)
[07:10:02] + Retrying using alternative port
[07:10:02] Connecting to http://130.237.165.141:80/
[07:10:39] Completed 380000 out of 500000 steps  (76%)
[07:17:10] Completed 385000 out of 500000 steps  (77%)
[07:23:40] Completed 390000 out of 500000 steps  (78%)
[07:25:03] - Couldn't send HTTP request to server
[07:25:03] + Could not connect to Work Server (results)
[07:25:03]     (130.237.165.141:80)
[07:25:03]   Could not transmit unit 09 to Collection server; keeping in queue.
[07:25:03] + Sent 0 of 1 completed units to the server
[07:25:03] - Autosend completed

Re: Project 7505 (0,2,19) upload fails

Posted: Tue Sep 27, 2011 9:48 am
by kasson
What client version are you using? Both servers mentioned in your log (130.237.165.141 and 128.143.199.97) should be set to allow a 45-minute connection time. I wonder if this is a client-side issue? Do you have >15 minute uploads working to other servers?

Re: Project 7505 (0,2,19) upload fails

Posted: Tue Sep 27, 2011 6:13 pm
by davidcoton
Sorry for omitting the info -- forgot this was not on the v7 beta forum!
This is on Linux 64-bit version 6.34. I have seen at least one 45-minute timeout on 128.143.199.97, it looks as if even that is not long enough (if time is the real issue).
I don't think there is anything at my end that would cause a timeout, though suggestions for Linux things to check are welcome (i am a Linux novice).
I am permanently connected via ADSL and the PC and hub run 24/7.

David

Re: Project 7505 (0,2,19) upload fails

Posted: Thu Sep 29, 2011 8:21 am
by davidcoton
Here's some more info about upload time.

The results file is >41MB (typo in original email). My average upload speed is 6kB/s. So the upload time will be around 7000 seconds -- almost 2 hours.

Timeouts are occurring at either 15 or 45 minutes, consistently. I am fairly sure this is the server timeout -- can it be extended? otherwise I shall have to exclude big units (by dumping them if necessary) since results of this size will never be uploaded within the permitted transfer time.

David

Re: Project 7505 (0,2,19) upload fails

Posted: Fri Sep 30, 2011 12:03 pm
by kasson
If your upload speeds are 6kB/s, I'd recommend using the client option for small work units (<5 MB) or normal work units (<10 MB) to make sure you get work units that aren't too big for your link to handle within the allotted time.

Re: Project 7505 (0,2,19) upload fails

Posted: Fri Sep 30, 2011 5:08 pm
by P5-133XL
kasson wrote:If your upload speeds are 6kB/s, I'd recommend using the client option for small work units (<5 MB) or normal work units (<10 MB) to make sure you get work units that aren't too big for your link to handle within the allotted time.
i.e. uniprocessor WU's

Re: Project 7505 (0,2,19) upload fails

Posted: Fri Sep 30, 2011 5:09 pm
by 7im
Switching from one SMP client to multiple copies of the CPU client is also a good way to go.