Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 05, 2008 11:16 pm
Thank you.toTOW wrote:I've notified the person in charge of this server.
Folding Forum
Community driven support forum for Folding@home
https://foldingforum.org/
171.64.65.56 not responding
Page 4 of 25
Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 05, 2008 11:20 pm
Ditto. I'm running a laptop right now and can't babysit this thing while I'm waiting for a WU to upload (and it's after midnight).
I hope somebody's on top of this. I know it's Sunday in Stanford, but maybe somebody could do a remote login and fix something.
Over and out ...
I hope somebody's on top of this. I know it's Sunday in Stanford, but maybe somebody could do a remote login and fix something.
Over and out ...
Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 05, 2008 11:54 pm
Woohoo, my WUs FINALLY uploaded to .65.56!
Re: 171.64.65.56 is in Reject status
Posted: Sun Oct 05, 2008 11:56 pm
Server is now up.
Re: 171.64.65.56 is in Reject status
Posted: Mon Oct 06, 2008 12:11 am
[23:42:24] + Attempting to send results [October 5 23:42:24 UTC]
[23:42:32] - Looking at optimizations...
[23:42:32] - Working with standard loops on this execution.
[23:42:32] - Files status OK
[23:42:34] - Expanded 229065 -> 1114469 (decompressed 486.5 percent)
[23:42:34] Called DecompressByteArray: compressed_data_size=229065 data_size=1114469, decompressed_data_size=1114469 diff=0
[23:42:34] - Digital signature verified
[23:42:34]
[23:42:34] Project: 4433 (Run 6, Clone 1, Gen 1)
[23:42:34]
[23:42:36] Entering M.D.
[23:42:42] Will resume from checkpoint file
[23:42:44] Node 2 initialized
[23:42:45] Resuming from checkpoint
[23:42:45] fcSaveRestoreState: I/O failed dir=0, var=0074C000, varsize=51336
[23:42:45] Verified work/wudata_01.log
[23:42:45] Verified work/wudata_01.trr
[23:42:45] Verified work/wudata_01.xtc
[23:42:45] Verified work/wudata_01.edr
[23:42:45] Completed 450010 out of 2500000 steps (18%)
[23:49:37] - Server does not have record of this unit. Will try again later.
[23:49:37] Could not transmit unit 00 to Collection server; keeping in queue.
[23:49:37] Project: 2669 (Run 14, Clone 155, Gen 8)
[23:49:37] + Attempting to send results [October 5 23:49:37 UTC]
[23:57:25] + Results successfully sent
[23:57:25] Thank you for your contribution to Folding@Home.
[23:57:25] + Number of Units Completed: 6
[23:59:20] Completed 475000 out of 2500000 steps (19%)
Well, with that last gasp (!), finally, my last "forsaken" SMP WU got uploaded, just a couple minutes ago. I did everything but send the Mini over to Death Row and back to get it to upload this sucker, which just would not go down the server's sweet little throat, I guess!
It had been in cue for more than 17 hours, even after the server got back up on its feet, as it didn't have a recollection of that one's existence, apparently, for the longest of times!
I restarted the Mini, ran AppleJack just to root out any bad crud in its little 10.5.5 system or caches, preferences, whatever, just really grasping for straws at why the SMP WU would not upload, and finally after this restart the above occurred. I am all caught up, some 5 SMP WU's now counted, and tallied in the Folding Stats pages, both mine and the overall stats. I wonder what was keeping that SMP from getting on board with the others, after the server came to life once again?
I am surely not a server expert, just wondering why that would occur...
Thanks so much to the great team at Folding, especially in Dr. Kasson's group, for getting to this server and fixing it before something bad happened, or something unforeseen were to happen. I must apologize for my reaction last post, but I was really stressed about those 5 SMP's that were not scored since 10/4/2008 @ about 3PM, when the server went down for the count.
A good resolution is always excellent, and it's appreciated by yours truly very much this time!
[23:42:32] - Looking at optimizations...
[23:42:32] - Working with standard loops on this execution.
[23:42:32] - Files status OK
[23:42:34] - Expanded 229065 -> 1114469 (decompressed 486.5 percent)
[23:42:34] Called DecompressByteArray: compressed_data_size=229065 data_size=1114469, decompressed_data_size=1114469 diff=0
[23:42:34] - Digital signature verified
[23:42:34]
[23:42:34] Project: 4433 (Run 6, Clone 1, Gen 1)
[23:42:34]
[23:42:36] Entering M.D.
[23:42:42] Will resume from checkpoint file
[23:42:44] Node 2 initialized
[23:42:45] Resuming from checkpoint
[23:42:45] fcSaveRestoreState: I/O failed dir=0, var=0074C000, varsize=51336
[23:42:45] Verified work/wudata_01.log
[23:42:45] Verified work/wudata_01.trr
[23:42:45] Verified work/wudata_01.xtc
[23:42:45] Verified work/wudata_01.edr
[23:42:45] Completed 450010 out of 2500000 steps (18%)
[23:49:37] - Server does not have record of this unit. Will try again later.
[23:49:37] Could not transmit unit 00 to Collection server; keeping in queue.
[23:49:37] Project: 2669 (Run 14, Clone 155, Gen 8)
[23:49:37] + Attempting to send results [October 5 23:49:37 UTC]
[23:57:25] + Results successfully sent
[23:57:25] Thank you for your contribution to Folding@Home.
[23:57:25] + Number of Units Completed: 6
[23:59:20] Completed 475000 out of 2500000 steps (19%)
Well, with that last gasp (!), finally, my last "forsaken" SMP WU got uploaded, just a couple minutes ago. I did everything but send the Mini over to Death Row and back to get it to upload this sucker, which just would not go down the server's sweet little throat, I guess!
It had been in cue for more than 17 hours, even after the server got back up on its feet, as it didn't have a recollection of that one's existence, apparently, for the longest of times!
I restarted the Mini, ran AppleJack just to root out any bad crud in its little 10.5.5 system or caches, preferences, whatever, just really grasping for straws at why the SMP WU would not upload, and finally after this restart the above occurred. I am all caught up, some 5 SMP WU's now counted, and tallied in the Folding Stats pages, both mine and the overall stats. I wonder what was keeping that SMP from getting on board with the others, after the server came to life once again?
I am surely not a server expert, just wondering why that would occur...
Thanks so much to the great team at Folding, especially in Dr. Kasson's group, for getting to this server and fixing it before something bad happened, or something unforeseen were to happen. I must apologize for my reaction last post, but I was really stressed about those 5 SMP's that were not scored since 10/4/2008 @ about 3PM, when the server went down for the count.
A good resolution is always excellent, and it's appreciated by yours truly very much this time!
Re: 171.64.65.56 is in Reject status
Posted: Mon Oct 06, 2008 12:32 am
I got a new work unit but results from the last one are still in waiting to be sent.
Re: 171.64.65.56 is in Reject status
Posted: Mon Oct 06, 2008 12:35 am
All of my clients have been sending and getting new WU's.
Thank you Thank you Thank you Thank you Thank you Thank you
Broken
Thank you Thank you Thank you Thank you Thank you Thank you
Broken
Re: 171.64.65.56 is in Reject status
Posted: Mon Oct 06, 2008 12:50 am
Thanx Paula and toTOW and ALL else who fixed or are fixing the servers
Peace
Peace
Re: 171.64.65.56 is in Reject status
Posted: Mon Oct 06, 2008 1:22 am
All my SMP clients are back, all SMP work sent off OK.
Thx to Paula et al..
Teddy
Thx to Paula et al..
Teddy
Re: 171.64.65.56 is in Reject status
Posted: Mon Oct 06, 2008 2:25 am
SMP WUs in queue uploaded while working on the next one. Thanks.
Re: 171.64.65.56 is in Reject status
Posted: Mon Oct 06, 2008 3:07 pm
As of 2 hours ago, still failing to upload, as is 171.64.122.86:
Code: Select all
[12:59:35] - Autosending finished units...
[12:59:35] Trying to send all finished work units
[12:59:35] + Attempting to send results
[12:59:35] - Reading file work/wuresults_01.dat from core
[12:59:35] (Read 49368307 bytes from disk)
[12:59:35] Connecting to http://171.64.65.56:8080/
[12:59:38] - Couldn't send HTTP request to server
[12:59:38] + Could not connect to Work Server (results)
[12:59:38] (171.64.65.56:8080)
[12:59:38] - Error: Could not transmit unit 01 (completed October 5) to work server.
[12:59:38] - 8 failed uploads of this unit.
[12:59:38] + Attempting to send results
[12:59:38] - Reading file work/wuresults_01.dat from core
[12:59:38] (Read 49368307 bytes from disk)
[12:59:38] Connecting to http://171.64.122.86:8080/
[12:59:41] - Couldn't send HTTP request to server
[12:59:41] + Could not connect to Work Server (results)
[12:59:41] (171.64.122.86:8080)
[12:59:41] Could not transmit unit 01 to Collection server; keeping in queue.
[12:59:41] + Sent 0 of 1 completed units to the server
[12:59:41] - Autosend completedRe: 171.64.65.56 is in Reject status
Posted: Wed Oct 15, 2008 8:33 am
Does not work again.
Re: 171.64.65.56 is in Reject status
Posted: Wed Oct 15, 2008 1:45 pm
I am having an issue this morning with a bunch of my clients trying to connect to send results and get new work. This server and 171.64.122.86:8080. When I connect to them in a browser from those client system I get an OK. When a client tried to connect though I get a chuck you farley.
Someone got a hammer?
Broken
*edit: mine are updating ok now. 2 of the clients had over 9 failed upload attempts and the other 4 had 2 failed uploads but then they finally connected. May have been a network issue (although the first 2 are on a straight internet connection while the 4 with issues are behind a proxy) but all is working now.
Thanks,
BW
Someone got a hammer?
Broken
*edit: mine are updating ok now. 2 of the clients had over 9 failed upload attempts and the other 4 had 2 failed uploads but then they finally connected. May have been a network issue (although the first 2 are on a straight internet connection while the 4 with issues are behind a proxy) but all is working now.
Thanks,
BW
Re: 171.64.65.56 is in Reject status
Posted: Wed Oct 15, 2008 2:38 pm
Seems up from what we can see here. Any one else seeing issues?
Re: 171.64.65.56 is in Reject status
Posted: Wed Oct 15, 2008 3:13 pm
Successfully sent 6 completed and queued WUs to this server this morning.
All appears well (and thank you Sir).
All appears well (and thank you Sir).