Page 1 of 1

171.64.65.102 rejecting [Resolved in about 2 hrs]

Posted: Wed Aug 04, 2010 6:59 pm
by Freaxy
As the topic title says, can't send my completed WU to the server 171.64.65.102.
Status in status list is on reject.

Code: Select all

[17:48:12] Completed 100%
[17:48:12] Successful run
[17:48:12] DynamicWrapper: Finished Work Unit: sleep=10000
[17:48:22] Reserved 154180 bytes for xtc file; Cosm status=0
[17:48:22] Allocated 154180 bytes for xtc file
[17:48:22] - Reading up to 154180 from "work/wudata_06.xtc": Read 154180
[17:48:22] Read 154180 bytes from xtc file; available packet space=786276284
[17:48:22] xtc file hash check passed.
[17:48:22] Reserved 23472 23472 786276284 bytes for arc file=<work/wudata_06.trr> Cosm status=0
[17:48:22] Allocated 23472 bytes for arc file
[17:48:22] - Reading up to 23472 from "work/wudata_06.trr": Read 23472
[17:48:22] Read 23472 bytes from arc file; available packet space=786252812
[17:48:22] trr file hash check passed.
[17:48:22] Allocated 560 bytes for edr file
[17:48:22] Read bedfile
[17:48:22] edr file hash check passed.
[17:48:22] Allocated 28865 bytes for logfile
[17:48:22] Read logfile
[17:48:22] GuardedRun: success in DynamicWrapper
[17:48:22] GuardedRun: done
[17:48:22] Run: GuardedRun completed.
[17:48:24] - Writing 207589 bytes of core data to disk...
[17:48:24] Done: 207077 -> 185558 (compressed to 89.6 percent)
[17:48:24]   ... Done.
[17:48:24] - Shutting down core 
[17:48:24] 
[17:48:24] Folding@home Core Shutdown: FINISHED_UNIT
[17:48:28] CoreStatus = 64 (100)
[17:48:28] Sending work to server
[17:48:28] Project: 5743 (Run 2, Clone 288, Gen 48)


[17:48:28] + Attempting to send results [August 4 17:48:28 UTC]
[17:48:30] - Couldn't send HTTP request to server
[17:48:30] + Could not connect to Work Server (results)
[17:48:30]     (171.64.65.102:8080)
[17:48:30] + Retrying using alternative port
[17:48:31] - Couldn't send HTTP request to server
[17:48:31] + Could not connect to Work Server (results)
[17:48:31]     (171.64.65.102:80)
[17:48:31] - Error: Could not transmit unit 06 (completed August 4) to work server.
[17:48:31]   Keeping unit 06 in queue.
[17:48:31] Project: 5743 (Run 2, Clone 288, Gen 48)


[17:48:31] + Attempting to send results [August 4 17:48:31 UTC]
[17:48:33] - Couldn't send HTTP request to server
[17:48:33] + Could not connect to Work Server (results)
[17:48:33]     (171.64.65.102:8080)
[17:48:33] + Retrying using alternative port
[17:48:35] - Couldn't send HTTP request to server
[17:48:35] + Could not connect to Work Server (results)
[17:48:35]     (171.64.65.102:80)
[17:48:35] - Error: Could not transmit unit 06 (completed August 4) to work server.


[17:48:35] + Attempting to send results [August 4 17:48:35 UTC]
[17:48:35] - Couldn't send HTTP request to server
[17:48:35]   (Got status 503)
[17:48:35] + Could not connect to Work Server (results)
[17:48:35]     (171.67.108.17:8080)
[17:48:35] + Retrying using alternative port
[17:48:36] - Couldn't send HTTP request to server
[17:48:36]   (Got status 503)
[17:48:36] + Could not connect to Work Server (results)
[17:48:36]     (171.67.108.17:80)
[17:48:36]   Could not transmit unit 06 to Collection server; keeping in queue.

Re: 171.64.65.102 rejecting

Posted: Wed Aug 04, 2010 7:49 pm
by bruce
Yes, the server was down about two hours.

Re: 171.64.65.102 rejecting

Posted: Wed Aug 04, 2010 7:57 pm
by Freaxy
Allright, just uploaded the 2 WU's.
Thanks.

Re: 171.64.65.102 rejecting

Posted: Tue Aug 31, 2010 6:24 am
by guest3412
server must be down again, rejecting, and can't get any more work either?

Code: Select all

[06:17:26] + Attempting to send results [August 31 06:17:26 UTC]
[06:17:26] - Reading file work/wuresults_01.dat from core
[06:17:26]   (Read 187309 bytes from disk)
[06:17:26] Connecting to http://171.64.65.102:8080/
[06:17:26] Posted data.
[06:17:26] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[06:17:26] + Couldn't get work instructions.
[06:17:26] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[06:17:27] - Couldn't send HTTP request to server
[06:17:27] + Could not connect to Work Server (results)
[06:17:27]     (171.64.65.102:8080)
[06:17:27] + Retrying using alternative port
[06:17:27] Connecting to http://171.64.65.102:80/
[06:17:28] - Couldn't send HTTP request to server
[06:17:28] + Could not connect to Work Server (results)
[06:17:28]     (171.64.65.102:80)
[06:17:28] - Error: Could not transmit unit 01 (completed August 31) to work server.
[06:17:28] - 5 failed uploads of this unit.
[06:17:28] - Read packet limit of 540015616... Set to 524286976.


[06:17:28] + Attempting to send results [August 31 06:17:28 UTC]
[06:17:28] - Reading file work/wuresults_01.dat from core
[06:17:28]   (Read 187309 bytes from disk)
[06:17:28] Connecting to http://171.67.108.17:8080/
[06:17:29] - Couldn't send HTTP request to server
[06:17:29] + Could not connect to Work Server (results)
[06:17:29]     (171.67.108.17:8080)
[06:17:29] + Retrying using alternative port
[06:17:29] Connecting to http://171.67.108.17:80/
[06:17:29] - Couldn't send HTTP request to server
[06:17:29]   (Got status 503)
[06:17:29] + Could not connect to Work Server (results)
[06:17:29]     (171.67.108.17:80)
[06:17:29]   Could not transmit unit 01 to Collection server; keeping in queue.
[06:17:29] + Sent 0 of 1 completed units to the server
[06:17:29] - Autosend completed
[06:17:34] + Attempting to get work packet
[06:17:34] - Will indicate memory of 2048 MB
[06:17:34] - Connecting to assignment server
[06:17:34] Connecting to http://assign-GPU.stanford.edu:8080/
[06:17:34] Posted data.
[06:17:34] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[06:17:34] + Couldn't get work instructions.
[06:17:34] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[06:17:45] + Attempting to get work packet
[06:17:45] - Will indicate memory of 2048 MB
[06:17:45] - Connecting to assignment server
[06:17:45] Connecting to http://assign-GPU.stanford.edu:8080/
[06:17:46] Posted data.
[06:17:46] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[06:17:46] + Couldn't get work instructions.
[06:17:46] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[06:18:10] + Attempting to get work packet
[06:18:10] - Will indicate memory of 2048 MB
[06:18:10] - Connecting to assignment server
[06:18:10] Connecting to http://assign-GPU.stanford.edu:8080/
[06:18:10] Posted data.
[06:18:10] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[06:18:10] + Couldn't get work instructions.
[06:18:10] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[06:18:51] + Attempting to get work packet
[06:18:51] - Will indicate memory of 2048 MB
[06:18:51] - Connecting to assignment server
[06:18:51] Connecting to http://assign-GPU.stanford.edu:8080/
[06:18:51] Posted data.
[06:18:51] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[06:18:51] + Couldn't get work instructions.
[06:18:51] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[06:20:11] + Attempting to get work packet
[06:20:11] - Will indicate memory of 2048 MB
[06:20:11] - Connecting to assignment server
[06:20:11] Connecting to http://assign-GPU.stanford.edu:8080/
[06:20:12] Posted data.
[06:20:12] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[06:20:12] + Couldn't get work instructions.
[06:20:12] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[06:22:59] + Attempting to get work packet
[06:22:59] - Will indicate memory of 2048 MB
[06:22:59] - Connecting to assignment server
[06:22:59] Connecting to http://assign-GPU.stanford.edu:8080/
[06:23:00] Posted data.
[06:23:00] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[06:23:00] + Couldn't get work instructions.
[06:23:00] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.


Re: 171.64.65.102 rejecting

Posted: Tue Aug 31, 2010 7:42 am
by bruce
At this time, 171.64.65.102 looks completely normal and it's issuing a reasonable percentage of the new WUs being sent out. An hour ago, when you posted, it was, indeed, having troubles, with "Reject" in the CONNECT column.

Re: 171.64.65.102 rejecting

Posted: Sun Oct 17, 2010 9:44 pm
by Eugenitor
Whatever the problem was, it's back again; the log for 102 is showing the intermittent rejection streaks.