Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

171.64.65.56 not responding

https://foldingforum.org/viewtopic.php?t=12022

Page 14 of 25

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 12:50 am
by BrokenWolf
314159 wrote: @ BW: You've been putting up too many WUs recently so I personally disabled your clients. :mrgreen:
(Keep up the GREAT WORK) :!:
Sorry, I have to get all the WUs in that I can (got a few more systems for Noah as well). Some of my lab systems I will soon have to put into actual use so Noah and I will lose quite a bit of production. :( Gotta get in as much as we can while we can.

BW

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 4:07 am
by bruce
What do you mean "actual" use? FAH is actual use. :D

Perhaps you mean used for whatever was planned when the equipment was originally purchased. :eugeek: :ewink:

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 6:13 am
by BrokenWolf
Bruce,

That is it. Some projects just move so dang slow that the systems are in our lab for sometime and I get used to having them around. :)

BW

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 9:24 am
by Gemini Cricket
Both of my C2D Macs are now unable to connect to the work server (171.67.108.56:8080) to return their finished units, and the one that has tried was also unable to connect to the alternative work server (171.67.108.25:8080). The trouble started early this morning Japan time, and is still continuing more than 12 hours later. The first to experience problems was in my office in Tokyo, so I brought it home to Tsuchiura, and that didn't improve matters, so the problem certainly seems to be at Stanford.

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 1:22 pm
by weedacres
It's still down, can't upload or download any smp work. I get no response when trying http://171.64.65.56:8080/ from my browser.

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 3:26 pm
by 314159
Nope.
The server has been up since the binary was restarted. 171.64.65.56 has been pingable for the past 12 hours +.
The problem appears to be in the Netload that has consistently run between ~198 and 201, far above usual norms and for reasons unknown to me.
If you look at your logs, you will see a multitude of 503's (the server busy code) and perhaps the built-in client "send delays" per the example below.

I had only one that was sent successfully to the "typically useless" CS. I believe that it is in this example (of about 4 1/2 wasted hours):

Code: Select all

[08:54:56] Folding@home Core Shutdown: FINISHED_UNIT
[08:58:13] CoreStatus = 64 (100)

[08:58:13] Sending work to server
[08:58:13] Project: 2675 (Run 1, Clone 276, Gen 120)


[08:58:13] + Attempting to send results [August 1 08:58:13 UTC]
[08:58:13] - Reading file work/wuresults_05.dat from core
[08:58:14]   (Read 25947574 bytes from disk)
[08:58:14] Connecting to http://171.64.65.56:8080/
[08:58:14] - Couldn't send HTTP request to server
[08:58:14]   (Got status 503)
[08:58:14] + Could not connect to Work Server (results)
[08:58:14]     (171.64.65.56:8080)
[08:58:14] + Retrying using alternative port
[08:58:14] Connecting to http://171.64.65.56:80/
[08:58:14] - Couldn't send HTTP request to server
[08:58:14]   (Got status 503)
[08:58:14] + Could not connect to Work Server (results)
[08:58:14]     (171.64.65.56:80)
[08:58:14] - Error: Could not transmit unit 05 (completed August 1) to work server.
[08:58:14] - 1 failed uploads of this unit.
[08:58:14]   Keeping unit 05 in queue.
[08:58:14] Trying to send all finished work units
[08:58:14] Project: 2675 (Run 1, Clone 276, Gen 120)


[08:58:14] + Attempting to send results [August 1 08:58:14 UTC]
[08:58:14] - Reading file work/wuresults_05.dat from core
[08:58:14]   (Read 25947574 bytes from disk)
[08:58:14] Connecting to http://171.64.65.56:8080/
[08:58:15] - Couldn't send HTTP request to server
[08:58:15]   (Got status 503)
[08:58:15] + Could not connect to Work Server (results)
[08:58:15]     (171.64.65.56:8080)
[08:58:15] + Retrying using alternative port
[08:58:15] Connecting to http://171.64.65.56:80/
[08:58:15] - Couldn't send HTTP request to server
[08:58:15]   (Got status 503)
[08:58:15] + Could not connect to Work Server (results)
[08:58:15]     (171.64.65.56:80)
[08:58:15] - Error: Could not transmit unit 05 (completed August 1) to work server.
[08:58:15] - 2 failed uploads of this unit.


[08:58:15] + Attempting to send results [August 1 08:58:15 UTC]
[08:58:15] - Reading file work/wuresults_05.dat from core
[08:58:15]   (Read 25947574 bytes from disk)
[08:58:15] Connecting to http://171.67.108.25:8080/
[08:58:15] - Couldn't send HTTP request to server
[08:58:15]   (Got status 503)
[08:58:15] + Could not connect to Work Server (results)
[08:58:15]     (171.67.108.25:8080)
[08:58:15] + Retrying using alternative port
[08:58:15] Connecting to http://171.67.108.25:80/
[08:58:16] - Couldn't send HTTP request to server
[08:58:16]   (Got status 503)
[08:58:16] + Could not connect to Work Server (results)
[08:58:16]     (171.67.108.25:80)
[08:58:16]   Could not transmit unit 05 to Collection server; keeping in queue.
[08:58:16] + Sent 0 of 1 completed units to the server
[08:58:16] - Preparing to get new work unit...
[08:58:16] + Attempting to get work packet
[08:58:16] - Will indicate memory of 2013 MB
[08:58:16] - Connecting to assignment server
[08:58:16] Connecting to http://assign.stanford.edu:8080/
[08:58:16] Posted data.
[08:58:16] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[08:58:16] + News From Folding@Home: Welcome to Folding@Home
[08:58:16] Loaded queue successfully.
[08:58:16] Connecting to http://171.64.65.56:8080/
[08:58:16] - Couldn't send HTTP request to server
[08:58:16]   (Got status 503)
[08:58:16] + Could not connect to Work Server
[08:58:16] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[08:58:27] + Attempting to get work packet
[08:58:27] - Will indicate memory of 2013 MB
[08:58:27] - Connecting to assignment server
[08:58:27] Connecting to http://assign.stanford.edu:8080/
[08:58:27] Posted data.
[08:58:27] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[08:58:27] + News From Folding@Home: Welcome to Folding@Home
[08:58:27] Loaded queue successfully.
[08:58:27] Connecting to http://171.64.65.56:8080/
[08:58:28] - Couldn't send HTTP request to server
[08:58:28]   (Got status 503)
[08:58:28] + Could not connect to Work Server
[08:58:28] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[08:58:47] + Attempting to get work packet
[08:58:47] - Will indicate memory of 2013 MB
[08:58:47] - Connecting to assignment server
[08:58:47] Connecting to http://assign.stanford.edu:8080/
[08:58:48] Posted data.
[08:58:48] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[08:58:48] + News From Folding@Home: Welcome to Folding@Home
[08:58:48] Loaded queue successfully.
[08:58:48] Connecting to http://171.64.65.56:8080/
[08:58:48] - Couldn't send HTTP request to server
[08:58:48]   (Got status 503)
[08:58:48] + Could not connect to Work Server
[08:58:48] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[08:59:10] + Attempting to get work packet
[08:59:10] - Will indicate memory of 2013 MB
[08:59:10] - Connecting to assignment server
[08:59:10] Connecting to http://assign.stanford.edu:8080/
[08:59:11] Posted data.
[08:59:11] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[08:59:11] + News From Folding@Home: Welcome to Folding@Home
[08:59:11] Loaded queue successfully.
[08:59:11] Connecting to http://171.64.65.56:8080/
[08:59:11] - Couldn't send HTTP request to server
[08:59:11]   (Got status 503)
[08:59:11] + Could not connect to Work Server
[08:59:11] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[09:00:04] + Attempting to get work packet
[09:00:04] - Will indicate memory of 2013 MB
[09:00:04] - Connecting to assignment server
[09:00:04] Connecting to http://assign.stanford.edu:8080/
[09:00:04] Posted data.
[09:00:04] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[09:00:04] + News From Folding@Home: Welcome to Folding@Home
[09:00:04] Loaded queue successfully.
[09:00:04] Connecting to http://171.64.65.56:8080/
[09:00:04] - Couldn't send HTTP request to server
[09:00:04]   (Got status 503)
[09:00:04] + Could not connect to Work Server
[09:00:04] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[09:01:26] + Attempting to get work packet
[09:01:26] - Will indicate memory of 2013 MB
[09:01:26] - Connecting to assignment server
[09:01:26] Connecting to http://assign.stanford.edu:8080/
[09:01:26] Posted data.
[09:01:26] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[09:01:26] + News From Folding@Home: Welcome to Folding@Home
[09:01:26] Loaded queue successfully.
[09:01:26] Connecting to http://171.64.65.56:8080/
[09:01:26] - Couldn't send HTTP request to server
[09:01:26]   (Got status 503)
[09:01:26] + Could not connect to Work Server
[09:01:26] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[09:04:16] + Attempting to get work packet
[09:04:16] - Will indicate memory of 2013 MB
[09:04:16] - Connecting to assignment server
[09:04:16] Connecting to http://assign.stanford.edu:8080/
[09:04:16] Posted data.
[09:04:16] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[09:04:16] + News From Folding@Home: Welcome to Folding@Home
[09:04:16] Loaded queue successfully.
[09:04:16] Connecting to http://171.64.65.56:8080/
[09:04:17] - Couldn't send HTTP request to server
[09:04:17]   (Got status 503)
[09:04:17] + Could not connect to Work Server
[09:04:17] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[09:09:46] + Attempting to get work packet
[09:09:46] - Will indicate memory of 2013 MB
[09:09:46] - Connecting to assignment server
[09:09:46] Connecting to http://assign.stanford.edu:8080/
[09:09:46] Posted data.
[09:09:46] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[09:09:46] + News From Folding@Home: Welcome to Folding@Home
[09:09:46] Loaded queue successfully.
[09:09:46] Connecting to http://171.64.65.56:8080/
[09:09:47] - Couldn't send HTTP request to server
[09:09:47]   (Got status 503)
[09:09:47] + Could not connect to Work Server
[09:09:47] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[09:20:37] + Attempting to get work packet
[09:20:37] - Will indicate memory of 2013 MB
[09:20:37] - Connecting to assignment server
[09:20:37] Connecting to http://assign.stanford.edu:8080/
[09:20:37] Posted data.
[09:20:37] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[09:20:37] + News From Folding@Home: Welcome to Folding@Home
[09:20:38] Loaded queue successfully.
[09:20:38] Connecting to http://171.64.65.56:8080/
[09:20:38] - Couldn't send HTTP request to server
[09:20:38]   (Got status 503)
[09:20:38] + Could not connect to Work Server
[09:20:38] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[09:42:00] + Attempting to get work packet
[09:42:00] - Will indicate memory of 2013 MB
[09:42:00] - Connecting to assignment server
[09:42:00] Connecting to http://assign.stanford.edu:8080/
[09:42:02] Posted data.
[09:42:02] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[09:42:02] + News From Folding@Home: Welcome to Folding@Home
[09:42:02] Loaded queue successfully.
[09:42:02] Connecting to http://171.64.65.56:8080/
[09:42:03] - Couldn't send HTTP request to server
[09:42:03]   (Got status 503)
[09:42:03] + Could not connect to Work Server
[09:42:03] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[09:53:03] - Autosending finished units... [August 1 09:53:03 UTC]
[09:53:03] Trying to send all finished work units
[09:53:03] Project: 2675 (Run 1, Clone 276, Gen 120)


[09:53:03] + Attempting to send results [August 1 09:53:03 UTC]
[09:53:03] - Reading file work/wuresults_05.dat from core
[09:53:04]   (Read 25947574 bytes from disk)
[09:53:04] Connecting to http://171.64.65.56:8080/
[09:53:04] - Couldn't send HTTP request to server
[09:53:04]   (Got status 503)
[09:53:04] + Could not connect to Work Server (results)
[09:53:04]     (171.64.65.56:8080)
[09:53:04] + Retrying using alternative port
[09:53:04] Connecting to http://171.64.65.56:80/
[09:53:04] - Couldn't send HTTP request to server
[09:53:04]   (Got status 503)
[09:53:04] + Could not connect to Work Server (results)
[09:53:04]     (171.64.65.56:80)
[09:53:04] - Error: Could not transmit unit 05 (completed August 1) to work server.
[09:53:04] - 3 failed uploads of this unit.


[09:53:04] + Attempting to send results [August 1 09:53:04 UTC]
[09:53:04] - Reading file work/wuresults_05.dat from core
[09:53:04]   (Read 25947574 bytes from disk)
[09:53:04] Connecting to http://171.67.108.25:8080/
[09:55:25] Posted data.
[09:55:26] Initial: 0000; - Uploaded at ~178 kB/s
[09:55:26] - Averaged speed for that direction ~160 kB/s
[09:55:26] + Results successfully sent
[09:55:26] Thank you for your contribution to Folding@Home.
[09:55:26] + Number of Units Completed: 93

[09:55:26]   Successfully sent unit 05 to Collection server.
[09:55:26] + Sent 1 of 1 completed units to the server
[09:55:26] - Autosend completed
[10:24:51] + Attempting to get work packet
[10:24:51] - Will indicate memory of 2013 MB
[10:24:51] - Connecting to assignment server
[10:24:51] Connecting to http://assign.stanford.edu:8080/
[10:24:51] Posted data.
[10:24:51] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[10:24:51] + News From Folding@Home: Welcome to Folding@Home
[10:24:51] Loaded queue successfully.
[10:24:51] Connecting to http://171.64.65.56:8080/
[10:24:51] - Couldn't send HTTP request to server
[10:24:51]   (Got status 503)
[10:24:51] + Could not connect to Work Server
[10:24:51] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[11:12:55] + Attempting to get work packet
[11:12:55] - Will indicate memory of 2013 MB
[11:12:55] - Connecting to assignment server
[11:12:55] Connecting to http://assign.stanford.edu:8080/
[11:13:03] Posted data.
[11:13:03] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[11:13:03] + News From Folding@Home: Welcome to Folding@Home
[11:13:03] Loaded queue successfully.
[11:13:03] Connecting to http://171.64.65.56:8080/
[11:13:04] - Couldn't send HTTP request to server
[11:13:04]   (Got status 503)
[11:13:04] + Could not connect to Work Server
[11:13:04] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[12:01:06] + Attempting to get work packet
[12:01:06] - Will indicate memory of 2013 MB
[12:01:06] - Connecting to assignment server
[12:01:06] Connecting to http://assign.stanford.edu:8080/
[12:01:07] Posted data.
[12:01:07] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[12:01:07] + News From Folding@Home: Welcome to Folding@Home
[12:01:07] Loaded queue successfully.
[12:01:07] Connecting to http://171.64.65.56:8080/
[12:01:07] - Couldn't send HTTP request to server
[12:01:07]   (Got status 503)
[12:01:07] + Could not connect to Work Server
[12:01:07] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[12:49:18] + Attempting to get work packet
[12:49:18] - Will indicate memory of 2013 MB
[12:49:18] - Connecting to assignment server
[12:49:18] Connecting to http://assign.stanford.edu:8080/
[12:49:21] Posted data.
[12:49:21] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[12:49:21] + News From Folding@Home: Welcome to Folding@Home
[12:49:21] Loaded queue successfully.
[12:49:21] Connecting to http://171.64.65.56:8080/
[12:49:22] - Couldn't send HTTP request to server
[12:49:22]   (Got status 503)
[12:49:22] + Could not connect to Work Server
[12:49:22] - Attempt #14  to get work failed, and no other work to do.
Waiting before retry.
[13:37:34] + Attempting to get work packet
[13:37:34] - Will indicate memory of 2013 MB
[13:37:34] - Connecting to assignment server
[13:37:34] Connecting to http://assign.stanford.edu:8080/
[13:37:34] Posted data.
[13:37:34] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[13:37:34] + News From Folding@Home: Welcome to Folding@Home
[13:37:35] Loaded queue successfully.
[13:37:35] Connecting to http://171.64.65.56:8080/
[13:37:41] Posted data.
[13:37:41] Initial: 0000; - Receiving payload (expected size: 4844533)
[13:37:45] - Downloaded at ~1182 kB/s
[13:37:45] - Averaged speed for that direction ~1084 kB/s
[13:37:45] + Received work.
[13:37:45] Trying to send all finished work units
[13:37:45] + No unsent completed units remaining.
[13:37:45] + Closed connections
[13:37:45] 
[13:37:45] + Processing work unit
[13:37:45] At least 4 processors must be requested.Core required: FahCore_a2.exe
[13:37:45] Core found.
[13:37:45] Working on queue slot 06 [August 1 13:37:45 UTC]
[13:37:45] + Working ...
[13:37:45] - Calling './mpiexec -np 4 -host 127.0.0.1 ./FahCore_a2.exe -dir work/ -suffix 06 -checkpoint 15 -forceasm -verbose -lifeline 18375 -version 624'

[13:37:45] 
[13:37:45] *------------------------------*
[13:37:45] Folding@Home Gromacs SMP Core
[13:37:45] Version 2.07 (Sun Apr 19 14:51:09 PDT 2009)
[13:37:45] 
[13:37:45] Preparing to commence simulation
[13:37:45] - Ensuring status. Please wait.
[13:37:46] Called DecompressByteArray: compressed_data_size=4844021 data_size=24003985, decompressed_data_size=24003985 diff=0
[13:37:46] - Digital signature verified
[13:37:46] 
[13:37:46] Project: 2672 (Run 0, Clone 157, Gen 192)
[13:37:46] 
[13:37:46] Assembly optimizations on if available.
[13:37:46] Entering M.D.
[13:37:57]  on if available.
[13:37:57] Entering M.D.
[13:38:06]  (0%)
[13:52:13] Completed 2500 out of 250000 steps  (1%)
HELP!

[off topic]
@ bruce: How do I report extraneous "offtopic" behavior by a Site Admin in an active and important thread - and to whom? :D :mrgreen: :ewink:
We took a vote and are banning you for 20 nanoseconds.
(I just could not resist posting this) :)
[/off topic]

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 5:48 pm
by bollix47
Same problem continues here. This server has been giving "503" status on and off for a couple days now and for some reason the assignment server isn't switching to another work server. :roll:

Code: Select all

[17:43:26] + Attempting to get work packet
[17:43:26] - Connecting to assignment server
[17:43:27] - Successful: assigned to (171.64.65.56).
[17:43:27] + News From Folding@Home: Welcome to Folding@Home
[17:43:27] Loaded queue successfully.
[17:43:27] - Couldn't send HTTP request to server
[17:43:27]   (Got status 503)
[17:43:27] + Could not connect to Work Server
[17:43:27] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 6:24 pm
by 314159
Update 10:46 PST:
Server Netload = 200
WU completed.
New work assigned by 171.64.65.56 after three quick 503's.
Completed WU was then sent to the CS and properly acknowledged. 8-)
Total elapsed time was a bit over 10 minutes (vs. my typical <3-4 minutes here).

BTW: I would MUCH prefer to deal with this situation than to be assigned to another server!!
You may enjoy running a1's. I definitely do not. :!:

When the P.G. completes their "little experiment" with PDC, I would love to see them assign ALL remaining Linux and OSX a1's to PDC and get them (the a1's) the heck out of here. :ewink: (they are presently "needed" for the Windoze SMP client only)

Our computers become obsolete over time. The a1 WUs for Linux and OSX became obsolete months ago...............

That said, I note that the P.G. has done a very commendable job in adjusting the "Weight" on the servers involved over a several month period and thank all concerned for doing this! (Special kudos to Dr. Kasson) :!:

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 6:31 pm
by ArVee
@bollix, I can report that I had the same thing going on for 8 hours today, but finally hit about an hour ago, so hang in.

@pi, I'm not quite as hospitable as you I guess because I think it's deplorable that situations such as this should be allowed not only to persist but recur. I'm not looking for a debate, just stating my opinion. If this were a business it'd have gone under months ago. It's not a business, it's a charity relying on goodwill so double the emphasis. Imagine a Goodwill with no doors for donors to enter.

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 6:38 pm
by bollix47
BTW: I would MUCH prefer to deal with this situation than to be assigned to another server!!
You may enjoy running a1's. I definitely do not. :!:
171.64.65.56 is not the only a2 server. Most of my rigs are getting their a2 WUs from 171.67.108.24.

It just seems that once you're assigned to 171.64.65.56 you get stuck there for a while. :e?:

p.s. I certainly don't want a1 core WUs either. :wink:

171.67.108.25

Posted: Sat Aug 01, 2009 6:50 pm
by markp1989
Im having trouble getting wus from this server to day, on 2 (the first 1 was earlier, and after about 5 hours of trying, it successfully downloaded a WU) different computers, both SMP client I tried connecting to that sever in firefox, and all i see is a white page, no "OK" as expected, how do i change servers? as currently i have 1 wu that needs uploading, and have no tasks for my desktop pc?

Thanks Markp1989

Re: 171.67.108.25

Posted: Sat Aug 01, 2009 6:53 pm
by markp1989

Code: Select all

[18:53:07] + Attempting to send results
[18:53:07] - Reading file work/wuresults_02.dat from core
[18:53:07]   (Read 26053139 bytes from disk)
[18:53:07] Connecting to http://171.67.108.25:8080/
[18:53:07] Posted data.
[18:53:07] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[18:53:07] + News From Folding@Home: Welcome to Folding@Home
[18:53:07] Loaded queue successfully.
[18:53:07] Connecting to http://171.64.65.56:8080/
[18:53:08] - Couldn't send HTTP request to server
[18:53:08]   (Got status 503)
[18:53:08] + Could not connect to Work Server
[18:53:08] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
Its trying to connect to another server now, but still failing :S

edit: Its now downloaded a wu from http://171.64.65.56:8080 but still hasnt uploaded the finished 1.

Re: 171.67.108.25

Posted: Sat Aug 01, 2009 7:05 pm
by 314159
171.67.108.25 is a "Collection Server" that accepts WUs when the issuing WORK server is busy or down (if it has a record of the WU).
Your WORK server for the completed project is 171.64.65.56.

Please see the last few posts to the thread concerning "171.64.65.56 in Reject Mode" that should explain this situation for you.
Your completed WU will/should be send via the autosend feature of the client in 6 hours or less.

Relax. Over a 6-7 year period, I have only lost one or two WUs in situations like this. (out of 50,000++) :ewink:

If you happen to be near the final deadline (only!), the -send all argument should work eventually.
If you have plenty of time remaining please do not use -send all since it will only contribute to the current server overload situation.

Fold on!

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 7:26 pm
by 314159
171.67.108.24 is "reserved" for Quad processors (which most of mine are).
I may be wrong on this if the client arguments (or overclocking issues) make a difference. :?:

Dual Core machines and C2D's have never been assigned to 171.67.108.24 to my knowledge although it's not a bad idea if xx.56 is down.
(kasson cringes) :ewink:

If 171.67.108.24 goes down, the Quads are assigned to 171.644.65.56 due to the present server weighting.
If they are both down at the same time (like a few days ago) we get screwed.

Bottom line: We DEFINITELY think alike - at least with respect to the a1's!

Edit: Umm? Someone deleted a post above this from another volunteer....... perhaps an (appropriate) thread consolidation omitting the initial post to which I responded?

Re: 171.64.65.56 is in Reject status

Posted: Sat Aug 01, 2009 7:48 pm
by BrokenWolf
I just checked my systems @ work and a few of them are barfing away on a1 WUs as well. One of them was a dual quad core (1.6GHz and 2GB ram so not powerful enough for -bigadv) so it has 4 cores just twiddling their electrons. It does great work on a2 WUs though. It goes thru ~3.5 of them a day. a2 WUs take ~2 to 3 days each. :(

Might there be a way to have the a1's set not go to Linux/OS X systems? Especially if there is a -smp 8 flag set on the client? Maybe this could be something to add to the new server code?

Thanks,

BW
All times are UTC
Page 14 of 25

Powered by phpBB® Forum Software © phpBB Limited