Thank You23:59:10] Project: 5506 (Run 4, Clone 1, Gen 16)
[23:59:10] - Read packet limit of 540015616... Set to 524286976.
[23:59:10] + Attempting to send results [August 6 23:59:10 UTC]
[23:59:11] - Couldn't send HTTP request to server
[23:59:11] + Could not connect to Work Server (results)
[23:59:11] (171.64.65.106:8080)
[23:59:11] + Retrying using alternative port
[23:59:13] - Couldn't send HTTP request to server
[23:59:13] + Could not connect to Work Server (results)
[23:59:13] (171.64.65.106:80)
[23:59:13] - Error: Could not transmit unit 02 (completed August 6) to work server.
[23:59:13] - Read packet limit of 540015616... Set to 524286976.
171.64.65.106 in REJECT
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 70
- Joined: Thu Jul 31, 2008 3:26 pm
- Hardware configuration: PC1//C2Q-Q9450,GA-X48-DS5-NinjaMini,GTX285,2x160GB Western Sata2,2x1GB Geil800,Tagan 800W;XP Pro SP3-32Bit;
PC2//C2Q-Q2600k.GB-P67UD4-Freezer 7Pro,GTX285Leadtek,260 GB Western Sata2,4x2GB GeilPC3,OCZ600W;Win7-64Bit;Siemens 22" - Location: Deutschland
171.64.65.106 in REJECT
1
PC1//C2Q-Q9450,GA-X48-DS5-,2xGTX285,2x160GB Western Sata2,2x1GB Geil800,Tagan 800W;XP Pro SP3-32Bit
PC2//C2Q-Q2600k.GB-P67UD4-Freezer 7Pro,GTX285Leadtek,260 GB WeSata2,4x2GB GeilPC3,OCZ600W;Win7-64Bit;Siemens 22"stern
PC2//C2Q-Q2600k.GB-P67UD4-Freezer 7Pro,GTX285Leadtek,260 GB WeSata2,4x2GB GeilPC3,OCZ600W;Win7-64Bit;Siemens 22"stern
-
- Pande Group Member
- Posts: 2058
- Joined: Fri Nov 30, 2007 6:25 am
- Location: Stanford
Re: 171.64.65.106 in REJEKT
Should be fixed now.
Re: 171.64.65.106 in REJEKT
Needs to befixed again!VijayPande wrote:Should be fixed now.
171.64.65.106 vspg4v2 densign full Reject 1.33
Re: 171.64.65.106 in REJECT
Confirmed rejecting as of 0600 PDT. It has been that way for some hours now. I don't think anything will be done until Monday AM, though.
-
- Pande Group Member
- Posts: 2058
- Joined: Fri Nov 30, 2007 6:25 am
- Location: Stanford
Re: 171.64.65.106 in REJECT
It's up now. We're looking into why it's periodically going down.
Re: 171.64.65.106 in REJECT
Thanks, just got my queue emtied - 6 WU's straight out.VijayPande wrote:It's up now. We're looking into why it's periodically going down.
Re: 171.64.65.106 in REJECT
Here we go again - reject
-
- Pande Group Member
- Posts: 2058
- Joined: Fri Nov 30, 2007 6:25 am
- Location: Stanford
Re: 171.64.65.106 in REJECT
It's up now.
We have new server code that should help this issue, but it's still in QA. We'll roll it out shortly.
We have new server code that should help this issue, but it's still in QA. We'll roll it out shortly.
Re: 171.64.65.106 in REJECT
This one is REJECT mode again and has been for quite some time today. I have 4 GPU WU's completed that cannot be sent back as the alternate server being tried as shown below is not even listed in the server list
Code: Select all
[04:35:59] Project: 5506 (Run 0, Clone 186, Gen 37)
[04:35:59] - Read packet limit of 540015616... Set to 524286976.
[04:35:59] + Attempting to send results [August 17 04:35:59 UTC]
[04:36:01] - Couldn't send HTTP request to server
[04:36:01] + Could not connect to Work Server (results)
[04:36:01] (171.64.65.106:8080)
[04:36:01] + Retrying using alternative port
[04:36:02] - Couldn't send HTTP request to server
[04:36:02] + Could not connect to Work Server (results)
[04:36:02] (171.64.65.106:80)
[04:36:02] - Error: Could not transmit unit 06 (completed August 17) to work server.
[04:36:02] - Read packet limit of 540015616... Set to 524286976.
[04:36:02] + Attempting to send results [August 17 04:36:02 UTC]
[04:36:02] - Couldn't send HTTP request to server
[04:36:02] (Got status 503)
[04:36:02] + Could not connect to Work Server (results)
[04:36:02] (171.64.122.76:8080)
[04:36:02] + Retrying using alternative port
[04:36:02] - Couldn't send HTTP request to server
[04:36:02] + Could not connect to Work Server (results)
[04:36:02] (171.64.122.76:80)
[04:36:02] Could not transmit unit 06 to Collection server; keeping in queue.
[04:36:02] - Preparing to get new work unit...
[04:36:02] + Attempting to get work packet
[04:36:02] - Connecting to assignment server
[04:36:02] - Successful: assigned to (171.64.65.20).
[04:36:02] + News From Folding@Home: GPU folding beta
[04:36:03] Loaded queue successfully.
[04:36:03] Project: 5506 (Run 0, Clone 186, Gen 37)
[04:36:03] - Read packet limit of 540015616... Set to 524286976.
[04:36:03] + Attempting to send results [August 17 04:36:03 UTC]
[04:36:04] - Couldn't send HTTP request to server
[04:36:04] + Could not connect to Work Server (results)
[04:36:04] (171.64.65.106:8080)
[04:36:04] + Retrying using alternative port
[04:36:06] - Couldn't send HTTP request to server
[04:36:06] + Could not connect to Work Server (results)
[04:36:06] (171.64.65.106:80)
[04:36:06] - Error: Could not transmit unit 06 (completed August 17) to work server.
[04:36:06] - Read packet limit of 540015616... Set to 524286976.
[04:36:06] + Attempting to send results [August 17 04:36:06 UTC]
[04:36:06] - Couldn't send HTTP request to server
[04:36:06] (Got status 503)
[04:36:06] + Could not connect to Work Server (results)
[04:36:06] (171.64.122.76:8080)
[04:36:06] + Retrying using alternative port
[04:36:06] - Couldn't send HTTP request to server
[04:36:06] (Got status 503)
[04:36:06] + Could not connect to Work Server (results)
[04:36:06] (171.64.122.76:80)
[04:36:06] Could not transmit unit 06 to Collection server; keeping in queue.
[04:36:06] + Closed connections
-
- Pande Group Member
- Posts: 2058
- Joined: Fri Nov 30, 2007 6:25 am
- Location: Stanford
Re: 171.64.65.106 in REJECT
Thanks for the feedbackup. It's up now.
Re: 171.64.65.106 in REJECT
And collection server not collecting.
Code: Select all
--- Opening Log file [August 22 14:16:16 UTC]
# Windows GPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.20r1
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\Bollix\AppData\Roaming\Folding@home-gpu
Arguments: -verbosity 9
[14:16:16] - Ask before connecting: No
[14:16:16] - User name: bollix47 (Team 39340)
Code: Select all
[14:16:16] + Attempting to send results [August 22 14:16:16 UTC]
[14:16:16] Core required: FahCore_11.exe
[14:16:16] Core found.
[14:16:16] - Reading file work/wuresults_04.dat from core
[14:16:16] Working on queue slot 05 [August 22 14:16:16 UTC]
[14:16:16] + Working ...
[14:16:16] (Read 1153898 bytes from disk)
[14:16:16] - Calling '.\FahCore_11.exe -dir work/ -suffix 05 -priority 96 -checkpoint 15 -verbose -lifeline 2972 -version 620'
[14:16:16] Connecting to http://171.64.65.106:8080/
[14:16:16]
[14:16:16] *------------------------------*
[14:16:16] Folding@Home GPU Core - Beta
[14:16:16] Version 1.09 (Fri Aug 1 11:46:54 PDT 2008)
[14:16:16]
[14:16:16] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[14:16:16] Build host: amoeba
[14:16:16] Board Type: Nvidia
[14:16:16] Core :
[14:16:16] Preparing to commence simulation
[14:16:16] - Looking at optimizations...
[14:16:16] - Files status OK
[14:16:16] - Expanded 43954 -> 244433 (decompressed 556.1 percent)
[14:16:16] Called DecompressByteArray: compressed_data_size=43954 data_size=244433, decompressed_data_size=244433 diff=0
[14:16:16] - Digital signature verified
[14:16:16]
[14:16:16] Project: 5006 (Run 7, Clone 21, Gen 114)
[14:16:16]
[14:16:16] Assembly optimizations on if available.
[14:16:16] Entering M.D.
[14:16:17] - Couldn't send HTTP request to server
[14:16:17] + Could not connect to Work Server (results)
[14:16:17] (171.64.65.106:8080)
[14:16:17] + Retrying using alternative port
[14:16:17] Connecting to http://171.64.65.106:80/
[14:16:18] - Couldn't send HTTP request to server
[14:16:18] + Could not connect to Work Server (results)
[14:16:18] (171.64.65.106:80)
[14:16:18] - Error: Could not transmit unit 04 (completed August 22) to work server.
[14:16:18] - 4 failed uploads of this unit.
[14:16:18] + Attempting to send results [August 22 14:16:18 UTC]
[14:16:18] - Reading file work/wuresults_04.dat from core
[14:16:18] (Read 1153898 bytes from disk)
[14:16:18] Connecting to http://171.64.122.76:8080/
[14:16:19] - Couldn't send HTTP request to server
[14:16:19] (Got status 503)
[14:16:19] + Could not connect to Work Server (results)
[14:16:19] (171.64.122.76:8080)
[14:16:19] + Retrying using alternative port
[14:16:19] Connecting to http://171.64.122.76:80/
[14:16:19] - Couldn't send HTTP request to server
[14:16:19] (Got status 503)
[14:16:19] + Could not connect to Work Server (results)
[14:16:19] (171.64.122.76:80)
[14:16:19] Could not transmit unit 04 to Collection server; keeping in queue.
[14:16:19] + Sent 0 of 1 completed units to the server
[14:16:19] - Autosend completed
-
- Pande Group Member
- Posts: 2058
- Joined: Fri Nov 30, 2007 6:25 am
- Location: Stanford
Re: 171.64.65.106 in REJECT
Fixed now. We have code that should do this automatically when it looks like it's in REJECT, but apparently that's not kicking in. We'll look into why.
Re: 171.64.65.106 in REJECT
Needs fixing again.
Re: 171.64.65.106 in REJECT
I've restarted the server. Thanks for the notification.
Dan
Dan