Page 1 of 2
171.64.65.20 and 171.67.108.25
Posted: Sun Jan 11, 2009 1:40 pm
by MtM
46 failed uploads on one client, 16 on another. Clients where on a hdd which ran out off space last night so wu's got corrupted I guess even when it doesn't complain now about wrong file size or anything it's definetly not a connection issue as I can connect manually without problems. The line where it says 'read 1 byte' should actually give this away already. I was just surprised I think this isn't handeld better? Shouldn't it say the results are corrupted, and not only say 'can not connect' when I'm sure that's not the issue here?
Code: Select all
[13:20:15] Folding@home Core Shutdown: FINISHED_UNIT
[13:20:18] CoreStatus = 64 (100)
[13:20:18] Unit 0 finished with 91 percent of time to deadline remaining.
[13:20:18] Updated performance fraction: 0.906451
[13:20:18] Sending work to server
[13:20:18] Project: 5016 (Run 0, Clone 801, Gen 20)
[13:20:18] + Attempting to send results [January 11 13:20:18 UTC]
[13:20:18] - Reading file work/wuresults_00.dat from core
[13:20:18] (Read 1154961 bytes from disk)
[13:20:18] Connecting to http://171.64.65.20:8080/
[13:20:31] Posted data.
[13:20:31] Initial: 0000; - Uploaded at ~86 kB/s
[13:20:31] - Averaged speed for that direction ~88 kB/s
[13:20:31] + Results successfully sent
[13:20:31] Thank you for your contribution to Folding@Home.
[13:20:31] + Number of Units Completed: 83
[13:20:35] Trying to send all finished work units
[13:20:35] Project: 5016 (Run 9, Clone 844, Gen 3)
[13:20:35] + Attempting to send results [January 11 13:20:35 UTC]
[13:20:35] - Reading file work/wuresults_03.dat from core
[13:20:35] (Read 1 bytes from disk)
[13:20:35] Connecting to http://171.64.65.20:8080/
[13:20:36] Posted data.
[13:20:36] Initial: 0000; + Could not connect to Work Server (results)
[13:20:36] (171.64.65.20:8080)
[13:20:36] + Retrying using alternative port
[13:20:36] Connecting to http://171.64.65.20:80/
[13:20:37] Posted data.
[13:20:37] Initial: 0000; + Could not connect to Work Server (results)
[13:20:37] (171.64.65.20:80)
[13:20:37] - Error: Could not transmit unit 03 (completed January 10) to work se
rver.
[13:20:37] - 45 failed uploads of this unit.
[13:20:37] + Attempting to send results [January 11 13:20:37 UTC]
[13:20:37] - Reading file work/wuresults_03.dat from core
[13:20:37] (Read 1 bytes from disk)
[13:20:37] Connecting to http://171.67.108.25:8080/
[13:20:37] - Couldn't send HTTP request to server
[13:20:37] (Got status 503)
[13:20:37] + Could not connect to Work Server (results)
[13:20:37] (171.67.108.25:8080)
[13:20:37] + Retrying using alternative port
[13:20:37] Connecting to http://171.67.108.25:80/
[13:20:38] - Couldn't send HTTP request to server
[13:20:38] (Got status 503)
[13:20:38] + Could not connect to Work Server (results)
[13:20:38] (171.67.108.25:80)
[13:20:38] Could not transmit unit 03 to Collection server; keeping in queue.
[13:20:38] + Sent 0 of 1 completed units to the server
[13:20:38] - Preparing to get new work unit...
[13:20:38] + Attempting to get work packet
[13:20:38] - Will indicate memory of 8190 MB
[13:20:38] - Connecting to assignment server
[13:20:38] Connecting to http://assign-GPU.stanford.edu:8080/
[13:20:38] Posted data.
[13:20:38] Initial: 40AB; - Successful: assigned to (171.64.65.20).
[13:20:38] + News From Folding@Home: GPU folding beta
[13:20:38] Loaded queue successfully.
[13:20:38] Connecting to http://171.64.65.20:8080/
[13:20:39] Posted data.
[13:20:39] Initial: 0000; - Receiving payload (expected size: 44640)
[13:20:40] - Downloaded at ~43 kB/s
[13:20:40] - Averaged speed for that direction ~37 kB/s
[13:20:40] + Received work.
[13:20:40] Trying to send all finished work units
[13:20:40] Project: 5016 (Run 9, Clone 844, Gen 3)
[13:20:40] + Attempting to send results [January 11 13:20:40 UTC]
[13:20:40] - Reading file work/wuresults_03.dat from core
[13:20:40] (Read 1 bytes from disk)
[13:20:40] Connecting to http://171.64.65.20:8080/
[13:20:41] Posted data.
[13:20:41] Initial: 0000; + Could not connect to Work Server (results)
[13:20:41] (171.64.65.20:8080)
[13:20:41] + Retrying using alternative port
[13:20:41] Connecting to http://171.64.65.20:80/
[13:20:41] Posted data.
[13:20:41] Initial: 0000; + Could not connect to Work Server (results)
[13:20:41] (171.64.65.20:80)
[13:20:41] - Error: Could not transmit unit 03 (completed January 10) to work se
rver.
[13:20:41] - 46 failed uploads of this unit.
[13:20:41] + Attempting to send results [January 11 13:20:41 UTC]
[13:20:41] - Reading file work/wuresults_03.dat from core
[13:20:41] (Read 1 bytes from disk)
[13:20:41] Connecting to http://171.67.108.25:8080/
[13:20:42] - Couldn't send HTTP request to server
[13:20:42] (Got status 503)
[13:20:42] + Could not connect to Work Server (results)
[13:20:42] (171.67.108.25:8080)
[13:20:42] + Retrying using alternative port
[13:20:42] Connecting to http://171.67.108.25:80/
[13:20:42] - Couldn't send HTTP request to server
[13:20:42] (Got status 503)
[13:20:42] + Could not connect to Work Server (results)
[13:20:42] (171.67.108.25:80)
[13:20:42] Could not transmit unit 03 to Collection server; keeping in queue.
[13:20:42] + Sent 0 of 1 completed units to the server
[13:20:42] + Closed connections
[13:20:42]
Re: 171.64.65.20 and 171.67.108.25
Posted: Mon Jan 12, 2009 11:27 am
by eberlyml
I am also having trouble with this cs, but a different work server 171.67.108.12. Have a few wu's stacking up here since Jan 7 that have not been able to be sent in. Hopefully someone is/will look into this soon.
Re: 171.64.65.20 and 171.67.108.25
Posted: Mon Jan 12, 2009 11:34 am
by MtM
eberlyml wrote:I am also having trouble with this cs, but a different work server 171.67.108.12. Have a few wu's stacking up here since Jan 7 that have not been able to be sent in. Hopefully someone is/will look into this soon.
171.67.108.12 -> OK ' paste the url in a browser or check the server status page.
My issue was with a corrupted queue entry, not a server problem. Didn't notice the '1 byte read' in the log before I posted, and ninja edited that remark in ( could have deleted the post as well but I didn't
).
Re: 171.64.65.20 and 171.67.108.25
Posted: Mon Jan 12, 2009 10:05 pm
by eberlyml
Yeah, I've been watching that for days. But still not able to send wu's back for some days now. Been seeing the below:
Code: Select all
[17:19:12] + Attempting to send results [January 12 17:19:12 UTC]
[17:19:12] - Couldn't send HTTP request to server
[17:19:12] + Could not connect to Work Server (results)
[17:19:12] (171.67.108.12:8080)
[17:19:12] + Retrying using alternative port
[17:19:12] - Couldn't send HTTP request to server
[17:19:12] + Could not connect to Work Server (results)
[17:19:12] (171.67.108.12:80)
[17:19:12] - Error: Could not transmit unit 05 (completed January 7) to work server.
[17:19:12] + Attempting to send results [January 12 17:19:12 UTC]
[17:19:13] - Couldn't send HTTP request to server
[17:19:13] + Could not connect to Work Server (results)
[17:19:13] (171.67.108.25:8080)
[17:19:13] + Retrying using alternative port
[17:19:13] - Couldn't send HTTP request to server
[17:19:13] + Could not connect to Work Server (results)
[17:19:13] (171.67.108.25:80)
[17:19:13] Could not transmit unit 05 to Collection server; keeping in queue.
[17:19:13] Project: 5113 (Run 96, Clone 0, Gen 10)
[17:19:13] + Attempting to send results [January 12 17:19:13 UTC]
[17:19:13] - Couldn't send HTTP request to server
[17:19:13] + Could not connect to Work Server (results)
[17:19:13] (171.67.108.12:8080)
[17:19:13] + Retrying using alternative port
[17:19:13] - Couldn't send HTTP request to server
[17:19:13] + Could not connect to Work Server (results)
[17:19:13] (171.67.108.12:80)
[17:19:13] - Error: Could not transmit unit 06 (completed January 11) to work server.
[17:19:13] + Attempting to send results [January 12 17:19:13 UTC]
[17:19:13] - Couldn't send HTTP request to server
[17:19:13] + Could not connect to Work Server (results)
[17:19:13] (171.67.108.25:8080)
[17:19:13] + Retrying using alternative port
[17:19:13] - Couldn't send HTTP request to server
[17:19:13] + Could not connect to Work Server (results)
[17:19:13] (171.67.108.25:80)
[17:19:13] Could not transmit unit 06 to Collection server; keeping in queue.
Re: 171.64.65.20 and 171.67.108.25
Posted: Mon Jan 12, 2009 11:54 pm
by VijayPande
Thanks for the report. As discussed in other threads, the CS's need a code update, which is being beta tested right now with the new server.
As for 171.64.65.20, this looks to be ok at the moment.
Re: 171.64.65.20 and 171.67.108.25
Posted: Thu Jan 15, 2009 11:16 am
by eberlyml
Hello, any further progress on this cs? According to the stats page it looks like it should be ok now, but my wu's continue to pile up. I'm still getting the same as above every time the client tries to send them in.
Re: 171.64.65.20 and 171.67.108.25
Posted: Thu Jan 15, 2009 11:19 am
by paulwarden
Code: Select all
[09:36:54] + Attempting to send results [January 15 09:36:54 UTC]
[09:36:55] Working on queue slot 07 [January 15 09:36:55 UTC]
[09:36:55] + Working ...
[09:37:05]
[09:37:05] *------------------------------*
[09:37:05] Folding@Home GPU Core - Beta
[09:37:05] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
[09:37:05]
[09:37:05] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[09:37:05] Build host: amoeba
[09:37:05] Board Type: Nvidia
[09:37:05] Core :
[09:37:05] Preparing to commence simulation
[09:37:05] - Ensuring status. Please wait.
[09:37:14] - Looking at optimizations...
[09:37:14] - Working with standard loops on this execution.
[09:37:14] - Previous termination of core was improper.
[09:37:14] - Files status OK
[09:37:14] - Expanded 98881 -> 492276 (decompressed 497.8 percent)
[09:37:14] Called DecompressByteArray: compressed_data_size=98881 data_size=492276, decompressed_data_size=492276 diff=0
[09:37:14] - Digital signature verified
[09:37:14]
[09:37:14] Project: 5756 (Run 7, Clone 278, Gen 3)
[09:37:14]
[09:37:14] Entering M.D.
[09:37:20] Will resume from checkpoint file
[09:37:21] Working on Protein
[09:37:25] Client config found, loading data.
[09:37:25] Starting GUI Server
[09:37:26] Resuming from checkpoint
[09:37:26] Verified work/wudata_07.log
[09:37:26] Verified work/wudata_07.edr
[09:37:26] Verified work/wudata_07.xtc
[09:37:26] Completed 19%
[09:39:07] - Couldn't send HTTP request to server
[09:39:07] + Could not connect to Work Server (results)
[09:39:07] (171.64.65.20:8080)
[09:39:07] + Retrying using alternative port
[09:39:16] Opening
[09:40:49] Completed 20%
[09:41:18] - Couldn't send HTTP request to server
[09:41:18] + Could not connect to Work Server (results)
[09:41:18] (171.64.65.20:80)
[09:41:18] - Error: Could not transmit unit 06 (completed January 15) to work server.
[09:41:18] - Read packet limit of 540015616... Set to 524286976.
[09:41:18] + Attempting to send results [January 15 09:41:18 UTC]
[09:43:35] - Couldn't send HTTP request to server
[09:43:35] + Could not connect to Work Server (results)
[09:43:35] (171.67.108.25:8080)
[09:43:35] + Retrying using alternative port
[09:44:12] Completed 21%
[09:45:28] Opening
[09:45:46] - Couldn't send HTTP request to server
[09:45:46] + Could not connect to Work Server (results)
[09:45:46] (171.67.108.25:80)
[09:45:46] Could not transmit unit 06 to Collection server; keeping in queue.
i am not able to send my results to the servers either when will this be sorted please have completed 4 wu since the small hours this morning and only one has been sent
Re: 171.64.65.20 and 171.67.108.25
Posted: Thu Jan 15, 2009 10:16 pm
by dschief
171.67.108.25
causing trouble foe me also; several failed upload attempts as of 14:12 west Coast time
Re: 171.64.65.20 and 171.67.108.25
Posted: Fri Jan 16, 2009 2:33 am
by eberlyml
Well, it is over two weeks now and all the work units finished on this machine are not able to be sent. Seeing as it really has no purpose here anymore besides folding, I am going to shut it down tonight when it finishes it's current wu. Work server continues to send out work that no one will collect (171.67.108.12). The collection server (171.67.108.25) is apparently being worked on but as of tonight I can send none of the completed stuff back. Not frustrated, just waiting until things are working correctly again.
Cheers,
PME
Re: 171.64.65.20 and 171.67.108.25
Posted: Fri Jan 16, 2009 11:02 am
by eberlyml
Follow up: This morning the second machine joined in the fray. On this one 171.67.108.24 and 171.67.108.25 are involved. This is my big folder and I never had a problem sending wu's before. I'd be grateful for any ideas if there might be something wrong on my end, there have been no firewall changes or anything like that I'm aware of.
Cheers,
PME
Re: 171.64.65.20 and 171.67.108.25
Posted: Fri Jan 16, 2009 1:17 pm
by toTOW
Re: 171.64.65.20 and 171.67.108.25
Posted: Fri Jan 16, 2009 3:28 pm
by paulwarden
Re: 171.64.65.20 and 171.67.108.25
Posted: Fri Jan 16, 2009 3:35 pm
by Tobit
I can connect to both of these on both 8080 and 80 ports so there is probably a connectivity issue between you and that server.
Re: 171.64.65.20 and 171.67.108.25
Posted: Fri Jan 16, 2009 6:45 pm
by paulwarden
i am able to connect to them but only when i paste the address to the address bar but not when my pc tries to send the results from the last 10 or so wus
Re: 171.64.65.20 and 171.67.108.25
Posted: Fri Jan 16, 2009 10:22 pm
by eberlyml
I can connect to
http://171.67.108.24:8080/ but with
http://171.67.108.25:8080/ I can only about 50% of the time. However I am not able to send any work units back to either of them, believe me I've watched a lot of attempts. On my WinXP client it is
http://171.67.108.12:8080/ that has been causing me problems on the work server end for well over two weeks now, and I get an OK there too when connecting with my browser. Not sure what to do, but I don't think I will fold too many more until I can figure out why I'm having so much trouble.
Cheers,
PME