Page 17 of 25
Re: 171.64.65.56 is in Reject status
Posted: Mon Aug 31, 2009 1:08 am
by susato
Thanks Tim and Nate for keeping an eye on this server - and thanks Dr. Kasson for the quick fixes every time the fool thing breaks.
Re: 171.64.65.56 is in Reject status
Posted: Fri Sep 18, 2009 3:37 pm
by Ragnar Dan
I'm having trouble uploading my completed WU to and downloading a new WU from this server on one of my machines.
Code: Select all
[17:20:14] Project: 2669 (Run 8, Clone 53, Gen 80)
[...]
[14:46:57] Completed 250000 out of 250000 steps (100%)
[14:46:58] DynamicWrapper: Finished Work Unit: sleep=10000
[14:47:08]
[14:47:08] Finished Work Unit:
[14:47:08] - Reading up to 21124656 from "work/wudata_02.trr": Read 21124656
[14:47:08] trr file hash check passed.
[14:47:08] - Reading up to 4429508 from "work/wudata_02.xtc": Read 4429508
[14:47:08] xtc file hash check passed.
[14:47:08] edr file hash check passed.
[14:47:08] logfile size: 191746
[14:47:08] Leaving Run
[14:47:10] - Writing 25896046 bytes of core data to disk...
[14:47:10] ... Done.
[14:47:10] - Shutting down core
[14:47:10]
[14:47:10] Folding@home Core Shutdown: FINISHED_UNIT
[14:50:30] CoreStatus = 64 (100)
[14:50:30] Sending work to server
[14:50:30] + Attempting to send results
[14:50:30] - Couldn't send HTTP request to server
[14:50:30] + Could not connect to Work Server (results)
[14:50:30] (171.64.65.56:8080)
[14:50:30] - Error: Could not transmit unit 02 (completed September 18) to work server.
[14:50:30] Keeping unit 02 in queue.
[14:50:30] + Attempting to send results
[14:50:30] - Couldn't send HTTP request to server
[14:50:30] + Could not connect to Work Server (results)
[14:50:30] (171.64.65.56:8080)
[14:50:30] - Error: Could not transmit unit 02 (completed September 18) to work server.
[14:50:30] + Attempting to send results
[14:50:31] - Couldn't send HTTP request to server
[14:50:31] + Could not connect to Work Server (results)
[14:50:31] (171.67.108.25:8080)
[14:50:31] Could not transmit unit 02 to Collection server; keeping in queue.
[14:50:31] - Preparing to get new work unit...
[14:50:31] + Attempting to get work packet
[14:50:31] - Connecting to assignment server
[14:50:31] - Successful: assigned to (171.64.65.56).
[14:50:31] + News From Folding@Home: Welcome to Folding@Home
[14:50:31] Loaded queue successfully.
[14:50:31] - Couldn't send HTTP request to server
[14:50:31] (Got status 503)
[14:50:31] + Could not connect to Work Server
[14:50:31] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[14:50:41] + Attempting to get work packet
[14:50:41] - Connecting to assignment server
[14:50:41] - Successful: assigned to (171.64.65.56).
[14:50:41] + News From Folding@Home: Welcome to Folding@Home
[14:50:41] Loaded queue successfully.
[14:50:42] - Couldn't send HTTP request to server
[14:50:42] (Got status 503)
[14:50:42] + Could not connect to Work Server
[14:50:42] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[14:50:54] + Attempting to get work packet
[14:50:54] - Connecting to assignment server
[14:50:54] - Successful: assigned to (171.64.65.56).
[14:50:54] + News From Folding@Home: Welcome to Folding@Home
[14:50:54] Loaded queue successfully.
[14:50:55] - Couldn't send HTTP request to server
[14:50:55] (Got status 503)
[14:50:55] + Could not connect to Work Server
[14:50:55] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[14:51:20] + Attempting to get work packet
[14:51:20] - Connecting to assignment server
[14:51:20] - Successful: assigned to (171.64.65.56).
[14:51:20] + News From Folding@Home: Welcome to Folding@Home
[14:51:20] Loaded queue successfully.
[14:51:21] - Couldn't send HTTP request to server
[14:51:21] (Got status 503)
[14:51:21] + Could not connect to Work Server
[14:51:21] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[14:52:03] + Attempting to get work packet
[14:52:03] - Connecting to assignment server
[14:52:04] - Successful: assigned to (171.64.65.56).
[14:52:04] + News From Folding@Home: Welcome to Folding@Home
[14:52:04] Loaded queue successfully.
[14:52:04] - Couldn't send HTTP request to server
[14:52:04] (Got status 503)
[14:52:04] + Could not connect to Work Server
[14:52:04] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[14:53:35] + Attempting to get work packet
[14:53:35] - Connecting to assignment server
[14:53:36] - Successful: assigned to (171.64.65.56).
[14:53:36] + News From Folding@Home: Welcome to Folding@Home
[14:53:36] Loaded queue successfully.
[14:53:36] - Couldn't send HTTP request to server
[14:53:36] (Got status 503)
[14:53:36] + Could not connect to Work Server
[14:53:36] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[14:56:19] + Attempting to get work packet
[14:56:19] - Connecting to assignment server
[14:56:20] - Successful: assigned to (171.64.65.56).
[14:56:20] + News From Folding@Home: Welcome to Folding@Home
[14:56:20] Loaded queue successfully.
[14:56:20] - Couldn't send HTTP request to server
[14:56:20] (Got status 503)
[14:56:20] + Could not connect to Work Server
[14:56:20] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[15:01:47] + Attempting to get work packet
[15:01:47] - Connecting to assignment server
[15:01:47] - Successful: assigned to (171.64.65.56).
[15:01:47] + News From Folding@Home: Welcome to Folding@Home
[15:01:47] Loaded queue successfully.
[15:01:48] - Couldn't send HTTP request to server
[15:01:48] (Got status 503)
[15:01:48] + Could not connect to Work Server
[15:01:48] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[15:12:42] + Attempting to get work packet
[15:12:42] - Connecting to assignment server
[15:12:42] - Successful: assigned to (171.64.65.56).
[15:12:42] + News From Folding@Home: Welcome to Folding@Home
[15:12:43] Loaded queue successfully.
[15:12:43] - Couldn't send HTTP request to server
[15:12:43] (Got status 503)
[15:12:43] + Could not connect to Work Server
[15:12:43] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[15:34:11] + Attempting to get work packet
[15:34:11] - Connecting to assignment server
[15:34:11] - Successful: assigned to (171.64.65.56).
[15:34:11] + News From Folding@Home: Welcome to Folding@Home
[15:34:11] Loaded queue successfully.
[15:34:11] - Couldn't send HTTP request to server
[15:34:11] (Got status 503)
[15:34:11] + Could not connect to Work Server
[15:34:11] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
Re: 171.64.65.56 is in Reject status
Posted: Fri Sep 18, 2009 4:09 pm
by kasson
The machine is assigning and accepting work right now. I see a number of active transactions, including several from you in the past few two days. The number of connections may be saturated, though.
Re: 171.64.65.56 is in Reject status
Posted: Fri Sep 18, 2009 4:30 pm
by Ragnar Dan
I killed the folding client and restarted it, and it got a new WU and then uploaded its completed one, so it looks like you're right. Thanks.
server 171.64.65.56 is in 503 mode
Posted: Fri Sep 18, 2009 4:45 pm
by slugbug
The assignment server 171.64.65.56 is in 503 mode.
Code: Select all
[12:01:28] Successfully sent unit 01 to Collection server.
[12:02:46] + Attempting to get work packet
[12:02:46] - Connecting to assignment server
[12:02:52] + Could not connect to Assignment Server
[12:03:23] - Successful: assigned to (171.64.65.56).
[12:03:23] + News From Folding@Home: Welcome to Folding@Home
[12:03:23] Loaded queue successfully.
[12:03:26] - Couldn't send HTTP request to server
[12:03:26] (Got status 503)
[12:03:26] + Could not connect to Work Server
[12:03:26] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.
Re: 171.64.65.56 is in Reject status
Posted: Sat Sep 26, 2009 10:50 am
by 314159
This server is in REJECT mode as of 3:48 AM PDT 9/26/09.
Please help!
Thanks.
Re: 171.64.65.56 is in Reject status
Posted: Sat Sep 26, 2009 2:35 pm
by Mactin
It looks like 171.64.65.56 is in Reject again...
client failled to upload a2 unit and downloaded a1 unit
Re: 171.64.65.56 is in Reject status
Posted: Sat Sep 26, 2009 4:30 pm
by 314159
Still showing REJECT on serverstats BUT is pingable and DL looks a LOT better.
Luckily, ALL of my C2D Linux machines completed prior to my earlier post when I noticed this situation OR will complete after 12:30 PM PST.
My bet is that Dr. Kasson (et al?) will have things back to normal by then.
Fingers are crossed.
Re: 171.64.65.56 is in Reject status
Posted: Sat Sep 26, 2009 10:14 pm
by kasson
It looks ok right now (and should have been ok since ~9am PDT). Thanks for the heads-up and let us know if there are further problems.
Re: 171.64.65.56 is in Reject status
Posted: Sat Sep 26, 2009 11:57 pm
by Mr.Nosmo
I have tried to upload a Project: 2669 (Run 12, Clone 164, Gen 151) WU from my 8-core system the last 90 min, but still no luck - is is because the server is busy with other up/down-loads?
Re: 171.64.65.56 is in Reject status
Posted: Sun Sep 27, 2009 2:14 am
by 314159
Well, I can tell you that all was Ok at 641 PM, 806 PM, 810 PM, and 815 PM (All Eastern Daylight Time) when I sent some up.
The server also looks fine now (2 hours later) and
WILL be fine for the balance of the weekend.
Check your FAHlog.txt file - a busy server returns a "503".
Good luck!
P.S. Thank you once again, Dr. Kasson.
One truly gets the feeling that you
care about the Project's
Volunteers, both in this Forum and elsewhere on this site.
Re: 171.64.65.56 is in Reject status
Posted: Wed Sep 30, 2009 2:09 pm
by DrBB1
It seems to be in reject status again. Note that 171.67.108.17 seems to be involved, at least indirectly.
Code: Select all
[03:01:27]
[03:01:27] Finished Work Unit:
[03:01:31] - Reading up to 362784 from "work/wudata_03.arc": Read 362784
[03:01:31] - Reading up to 3564620 from "work/wudata_03.xtc": Read 3564620
[03:01:37] goefile size: 0
[03:01:37] logfile size: 918838
[03:01:38] Leaving Run
[03:01:41] - Writing 6610534 bytes of core data to disk...
[03:01:53] Done: 6610022 -> 4802820 (compressed to 72.6 percent)
[03:01:57] ... Done.
[03:01:59] - Shutting down core
[03:01:59]
[03:01:59] Folding@home Core Shutdown: FINISHED_UNIT
[03:02:04] CoreStatus = 64 (100)
[03:02:04] Sending work to server
[03:02:04] Project: 6307 (Run 438, Clone 4, Gen 1)
[03:02:05] + Attempting to send results [September 30 03:02:05 UTC]
[03:02:08] - Couldn't send HTTP request to server
[03:02:08] + Could not connect to Work Server (results)
[03:02:08] (171.64.65.111:8080)
[03:02:08] + Retrying using alternative port
[03:02:11] - Couldn't send HTTP request to server
[03:02:11] + Could not connect to Work Server (results)
[03:02:11] (171.64.65.111:80)
[03:02:11] - Error: Could not transmit unit 03 (completed September 30) to work server.
[03:02:11] Keeping unit 03 in queue.
[03:02:11] Project: 6307 (Run 438, Clone 4, Gen 1)
[03:02:11] + Attempting to send results [September 30 03:02:11 UTC]
[03:02:12] - Couldn't send HTTP request to server
[03:02:12] + Could not connect to Work Server (results)
[03:02:12] (171.64.65.111:8080)
[03:02:12] + Retrying using alternative port
[03:02:14] - Couldn't send HTTP request to server
[03:02:14] + Could not connect to Work Server (results)
[03:02:14] (171.64.65.111:80)
[03:02:14] - Error: Could not transmit unit 03 (completed September 30) to work server.
[03:02:14] + Attempting to send results [September 30 03:02:14 UTC]
[03:02:15] - Couldn't send HTTP request to server
[03:02:15] + Could not connect to Work Server (results)
[03:02:15] (171.67.108.17:8080)
[03:02:15] + Retrying using alternative port
[03:02:16] - Couldn't send HTTP request to server
[03:02:16] + Could not connect to Work Server (results)
[03:02:16] (171.67.108.17:80)
[03:02:16] Could not transmit unit 03 to Collection server; keeping in queue.
[03:02:16] - Preparing to get new work unit...
[03:02:16] + Attempting to get work packet
[03:02:16] - Connecting to assignment server
[03:02:18] - Successful: assigned to (171.67.108.13).
[03:02:18] + News From Folding@Home: Welcome to Folding@Home
[03:02:18] Loaded queue successfully.
[03:02:23] Project: 6307 (Run 438, Clone 4, Gen 1)
[03:02:23] + Attempting to send results [September 30 03:02:23 UTC]
[03:02:24] - Couldn't send HTTP request to server
[03:02:24] + Could not connect to Work Server (results)
[03:02:24] (171.64.65.111:8080)
[03:02:24] + Retrying using alternative port
[03:02:25] - Couldn't send HTTP request to server
[03:02:25] + Could not connect to Work Server (results)
[03:02:25] (171.64.65.111:80)
[03:02:25] - Error: Could not transmit unit 03 (completed September 30) to work server.
[03:02:25] + Attempting to send results [September 30 03:02:25 UTC]
[03:05:35] - Couldn't send HTTP request to server
[03:05:35] + Could not connect to Work Server (results)
[03:05:35] (171.67.108.17:8080)
[03:05:35] + Retrying using alternative port
[03:08:44] - Couldn't send HTTP request to server
[03:08:44] + Could not connect to Work Server (results)
[03:08:44] (171.67.108.17:80)
[03:08:44] Could not transmit unit 03 to Collection server; keeping in queue.
[03:08:44] + Closed connections
[03:08:44]
[03:08:44] + Processing work unit
[03:08:44] Core required: FahCore_78.exe
[03:08:44] Core found.
[03:08:44] Working on queue slot 04 [September 30 03:08:44 UTC]
[03:08:44] + Working ...
[03:08:46]
[03:08:46] *------------------------------*
[03:08:46] Folding@Home Gromacs Core
[03:08:46] Version 1.90 (March 8, 2006)
[03:08:46]
[03:08:46] Preparing to commence simulation
[03:08:46] - Looking at optimizations...
[03:08:46] - Created dyn
[03:08:46] - Files status OK
[03:08:46] - Expanded 238679 -> 1167721 (decompressed 489.2 percent)
[03:08:46] - Starting from initial work packet
[03:08:46]
[03:08:46] Project: 4440 (Run 884, Clone 2, Gen 37)
[03:08:46]
[03:08:46] Assembly optimizations on if available.
[03:08:46] Entering M.D.
[03:08:52] Protein: p4440_Seq42_Amber03
[03:08:52]
[03:08:52] Writing local files
[03:10:22] Extra 3DNow boost OK.
[03:10:22] Writing local files
[03:10:22] Completed 0 out of 1500000 steps (0%)
[04:14:14] Writing local files
[04:14:16] Completed 15000 out of 1500000 steps (1%)
[05:16:59] Writing local files
[05:16:59] Completed 30000 out of 1500000 steps (2%)
[06:20:29] Writing local files
[06:20:29] Completed 45000 out of 1500000 steps (3%)
[07:23:30] Writing local files
[07:23:30] Completed 60000 out of 1500000 steps (4%)
[08:26:23] Writing local files
[08:26:23] Completed 75000 out of 1500000 steps (5%)
[08:59:43] Project: 6307 (Run 438, Clone 4, Gen 1)
[08:59:43] + Attempting to send results [September 30 08:59:43 UTC]
[08:59:45] - Couldn't send HTTP request to server
[08:59:45] + Could not connect to Work Server (results)
[08:59:45] (171.64.65.111:8080)
[08:59:45] + Retrying using alternative port
[08:59:46] - Couldn't send HTTP request to server
[08:59:46] + Could not connect to Work Server (results)
[08:59:46] (171.64.65.111:80)
[08:59:46] - Error: Could not transmit unit 03 (completed September 30) to work server.
[08:59:46] + Attempting to send results [September 30 08:59:46 UTC]
[09:02:55] - Couldn't send HTTP request to server
[09:02:55] + Could not connect to Work Server (results)
[09:02:55] (171.67.108.17:8080)
[09:02:55] + Retrying using alternative port
[09:06:05] - Couldn't send HTTP request to server
[09:06:05] + Could not connect to Work Server (results)
[09:06:05] (171.67.108.17:80)
[09:06:05] Could not transmit unit 03 to Collection server; keeping in queue.
[09:06:05] + Working...
[09:29:27] Writing local files
[09:29:27] Completed 90000 out of 1500000 steps (6%)
[10:32:15] Writing local files
[10:32:15] Completed 105000 out of 1500000 steps (7%)
[11:35:11] Writing local files
[11:35:11] Completed 120000 out of 1500000 steps (8%)
[12:37:58] Writing local files
[12:37:58] Completed 135000 out of 1500000 steps (9%)
[13:40:53] Writing local files
[13:40:53] Completed 150000 out of 1500000 steps (10%)
Re: 171.64.65.56 is in Reject status
Posted: Wed Sep 30, 2009 2:59 pm
by kasson
Please note that your log refers to a completely different server. Server 171.64.65.56 is up and functioning. I would suggest posting in a thread for the appropriate server. Thanks!
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 03, 2009 1:43 pm
by Olorin
Hi.
I have quite a lot of WUs ready for upload with my SMP client for 171.64.65.56 as well (as for the 171.67.108.24 I've posted there as well) and they keep bouncing. Here is (one of) the message I get:
[13:33:40] - Ask before connecting: No
[13:33:40] - User name: Olorin (Team 12713)
[13:33:40] - User ID: 13C443F049E6F016
[13:33:40] - Machine ID: 1
[13:33:40]
[13:33:40] Loaded queue successfully.
[13:33:40] Attempting to return result(s) to server...
[13:33:40] - Read packet limit of 540015616... Set to 524286976.
[13:33:40] + Attempting to send results
[13:33:45] - Couldn't send HTTP request to server
[13:33:45] + Could not connect to Work Server (results)
[13:33:45] (171.64.65.56:8080)
[13:33:45] - Error: Could not transmit unit 07 (completed October 1) to work server.
[13:33:45] - Read packet limit of 540015616... Set to 524286976.
[13:33:45] + Attempting to send results
[13:33:46] - Couldn't send HTTP request to server
[13:33:46] + Could not connect to Work Server (results)
[13:33:46] (171.67.108.25:8080)
[13:33:46] Could not transmit unit 07 to Collection server; keeping in queue.
[13:33:46] - Failed to send unit 07 to server
Folding@Home Client Shutdown.
Can you do something about it? Thank you.
Re: 171.64.65.56 is in Reject status
Posted: Sat Oct 03, 2009 9:30 pm
by kasson
You're trying to return work with an outdated core. Those results are invalid. Sorry.
We set the servers to require a core update quite some time ago. Current versions of the core and client auto-update correctly, but it looks like you're using rather old versions (6.02 client & 2.01 core). You'll have to manually delete the core, and you probably want to upgrade your client as well.