Cannot transmit to 171.64.65.111

Moderators: Site Moderators, FAHC Science Team

nk6002
Posts: 7
Joined: Sat Jan 17, 2009 5:25 am

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by nk6002 »

143 failed uploads of the WU according to the log file.

Code: Select all

[19:01:35] - Couldn't send HTTP request to server
[19:01:35] + Could not connect to Work Server (results)
[19:01:35]     (171.64.122.136:8080)
[19:01:35] + Retrying using alternative port
[19:01:35] Connecting to http://171.64.122.136:80/
[19:01:56] - Couldn't send HTTP request to server
[19:01:56] + Could not connect to Work Server (results)
[19:01:56]     (171.64.122.136:80)
[19:01:56] - Error: Could not transmit unit 09 (completed January 25) to work server.
[19:01:56] - 143 failed uploads of this unit.
VijayPande
Pande Group Member
Posts: 2058
Joined: Fri Nov 30, 2007 6:25 am
Location: Stanford

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by VijayPande »

These servers have been up for a while. I wonder if there is some other networking issue going on here?
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
7im
Posts: 10179
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by 7im »

nk6002 wrote:143 failed uploads of the WU according to the log file.
Please post more of your log file so we can see what is going on. Start with the first 35 lines of the fahlog.txt file. The text from the startup of the client answers about 10-12 questions that we won't have to ask individually, like what client, what version, what startup switches, etc. Thanks.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
nk6002
Posts: 7
Joined: Sat Jan 17, 2009 5:25 am

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by nk6002 »

Just checked the log file and found that the results/data was successfully transmitted about 2.5 hrs ago. :D
Desertfox80
Posts: 15
Joined: Sat Jan 24, 2009 6:29 pm
Location: California

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by Desertfox80 »

It's still not uploading, and now I have 3 WU's for this IP that are sitting and failing to upload. No issues with the other comps uploading to different servers, just this particular IP is simply not accepting uploads.

Here is the latest one completed Jan 27th that is going nowhere

[19:05:17] Project: 4102 (Run 83, Clone 1, Gen 22)
[19:05:17] - Read packet limit of 540015616... Set to 524286976.
[19:05:17] + Attempting to send results [January 27 19:05:17 UTC]
[19:05:24] - Couldn't send HTTP request to server
[19:05:24] + Could not connect to Work Server (results)
[19:05:24] (171.64.65.111:8080)
[19:05:24] + Retrying using alternative port
[19:05:32] - Couldn't send HTTP request to server
[19:05:32] + Could not connect to Work Server (results)
[19:05:32] (171.64.65.111:80)
[19:05:32] - Error: Could not transmit unit 00 (completed January 27) to work server.
[19:05:32] - Read packet limit of 540015616... Set to 524286976.
Desertfox80
Posts: 15
Joined: Sat Jan 24, 2009 6:29 pm
Location: California

Please fix 171.64.65.111 & 171.67.108.17

Post by Desertfox80 »

I now have four WU's for this server that are in an endless loop of failing to upload. Can someone please nudge whomever is responsible for the servers to reset this machine, fix it's refusal to accept uploads or something. Other WU's unrelated to this IP have sent just fine from this particular computer, so something is whacked back at the mothership.

This is the latest one to fail. They're all for Core:81
Project: 4102 (Run 83, Clone 1, Gen 22), Core: 81
Work server: 171.64.65.111:8080
Collection server: 171.67.108.17
Download date: January 25 18:13:16
Finished date: January 27 10:20:22

All I get in the logs for this is;

- Couldn't send HTTP request to server
+ Could not connect to Work Server (results)
(171.64.65.111:8080)
+ Could not connect to Work Server (results)
(171.67.108.17:80)
Could not transmit unit 00 to Collection server; keeping in queue.
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by bruce »

That server was down between 10:00 and 12:30 PST which includes the time you posted. It has been accepting between 100 and 150 uploads per hour since then. I presume your problem has been fixed.

If not, what happens when you click http://171.64.65.111:8080/ and http://171.64.65.111/ ?
Desertfox80
Posts: 15
Joined: Sat Jan 24, 2009 6:29 pm
Location: California

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by Desertfox80 »

No, the problem has not resolved itself. The last attempted uploads were January 30th at 12:45 am PDT and it failed as well. I get the same error messages as before.

If I click on the IP's you provided I get "OK" on both of them.
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by bruce »

Apparently nobody has asked you for the details of your installation.

Which OS?
How do you connect to the internet?
What router do you have, if any?
Which version of FAH are you running?
What does tracert 171.64.65.111 (or traceroute if you're Linux) show?
Desertfox80
Posts: 15
Joined: Sat Jan 24, 2009 6:29 pm
Location: California

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by Desertfox80 »

This particular machine is running Windows XP Pro SP3. This one is connected to a dedicated for FAH 3mbps DSL service, hardwired to a 2wire 2701HG-B DSL modem. I am using FAH version 6.23 built Nov 26, 2008. I don't have any other issues with different WU's that go to other IP's from this same computer, it's just the ones associated with this particular IP. The tracert results are below. I even tried moving this computer over to a 10mbps cable internet connection here to see if that might help, but it did nothing to resolve the upload failures. I ran the tracert from both internet connections in the house and it timed out both times at step 10 as seen below.



C:\>tracert 171.64.65.111
Tracing route to vspg5v2.Stanford.EDU [171.64.65.111]over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 13 ms 11 ms 11 ms adsl-76-246-63-254.dsl.scrm01.sbcglobal.net [76.246.63.254]
3 9 ms 9 ms 9 ms 64.171.154.65
4 11 ms 9 ms 11 ms 151.164.93.212
5 15 ms 13 ms 15 ms 151.164.38.58
6 14 ms 15 ms 13 ms po5-3.core01.sjc04.atlas.cogentco.com [154.54.13.97]
7 16 ms 15 ms 15 ms te3-2.mpd01.sjc04.atlas.cogentco.com [66.28.4.49]
8 17 ms 17 ms 15 ms Stanford_University2.demarc.cogentco.com [66.250.7.138]
9 16 ms 15 ms 15 ms bbrb-isp.Stanford.EDU [171.64.1.155]
10 * * * Request timed out.
11 17 ms 17 ms 15 ms vspg5v2.Stanford.EDU [171.64.65.111]

Trace complete.

C:\>
KroontjesPen
Posts: 50
Joined: Thu Oct 30, 2008 2:29 pm
Location: Spijkenisse, The Netherlands

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by KroontjesPen »

Both links in the start post give here blank pages now with NO ok. That's the same for server 171.67.108.17.

Code: Select all

[12:49:54] + Attempting to send results [February 3 12:49:54 UTC]
[12:49:54] Working on queue slot 06 [February 3 12:49:54 UTC]
[12:49:54] + Working ...
[12:49:54] 
[12:49:54] *------------------------------*
[12:49:54] Folding@Home Double Gromacs Core C
[12:49:54] Version 1.00 (Thu Apr 24 19:12:09 PDT 2008)
[12:49:54] 
[12:49:54] Preparing to commence simulation
[12:49:54] - Files status OK
[12:49:54] - Couldn't send HTTP request to server
[12:49:54]   (Got status 503)
[12:49:54] + Could not connect to Work Server (results)
[12:49:54]     (171.64.65.111:8080)
[12:49:54] + Retrying using alternative port
[12:49:55] - Couldn't send HTTP request to server
[12:49:55]   (Got status 503)
[12:49:55] + Could not connect to Work Server (results)
[12:49:55]     (171.64.65.111:80)
[12:49:55] - Error: Could not transmit unit 05 (completed February 2) to work server.


[12:49:55] + Attempting to send results [February 3 12:49:55 UTC]
[12:49:55] - Expanded 1253904 -> 3488501 (decompressed 278.2 percent)
[12:49:55] 
[12:49:55] Project: 3858 (Run 10181, Clone 0, Gen 24)
[12:49:55] 
[12:49:55] Assembly optimizations on if available.
[12:49:55] Entering M.D.
[12:49:55] - Couldn't send HTTP request to server
[12:49:55]   (Got status 503)
[12:49:55] + Could not connect to Work Server (results)
[12:49:55]     (171.67.108.17:8080)
[12:49:55] + Retrying using alternative port
[12:49:56] - Couldn't send HTTP request to server
[12:49:56]   (Got status 503)
[12:49:56] + Could not connect to Work Server (results)
[12:49:56]     (171.67.108.17:80)
[12:49:56]   Could not transmit unit 05 to Collection server; keeping in queue.
[12:50:01] Will resume from checkpoint file
Edit part.
Attempting to send results February 3 18:49:56 UTC

Code: Select all

[18:49:56] Project: 4103 (Run 35, Clone 16, Gen 21)


[18:49:56] + Attempting to send results [February 3 18:49:56 UTC]
[18:49:58] - Couldn't send HTTP request to server
[18:49:58] + Could not connect to Work Server (results)
[18:49:58]     (171.64.65.111:8080)
[18:49:58] + Retrying using alternative port
[18:49:59] - Couldn't send HTTP request to server
[18:49:59] + Could not connect to Work Server (results)
[18:49:59]     (171.64.65.111:80)
[18:49:59] - Error: Could not transmit unit 05 (completed February 2) to work server.


[18:49:59] + Attempting to send results [February 3 18:49:59 UTC]
[18:50:00] - Couldn't send HTTP request to server
[18:50:00]   (Got status 503)
[18:50:00] + Could not connect to Work Server (results)
[18:50:00]     (171.67.108.17:8080)
[18:50:00] + Retrying using alternative port
[18:50:00] - Couldn't send HTTP request to server
[18:50:00]   (Got status 503)
[18:50:00] + Could not connect to Work Server (results)
[18:50:00]     (171.67.108.17:80)
[18:50:00]   Could not transmit unit 05 to Collection server; keeping in queue.
[18:53:38] Timer requesting checkpoint
[18:58:04] Completed 150000 out of 200000 steps  (75%)
KroontjesPen
Posts: 50
Joined: Thu Oct 30, 2008 2:29 pm
Location: Spijkenisse, The Netherlands

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by KroontjesPen »

Problem solved.
First by retrying using alternative port for 171.64.65.111:8080.
Later on, a next result, without any problem at all.
Received new work packet from 171.67.108.13.

Happy folding. :)
Desertfox80
Posts: 15
Joined: Sat Jan 24, 2009 6:29 pm
Location: California

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by Desertfox80 »

It finally uploaded all the WU's off the various machines today. For now, my issue with these servers has resolved itself.
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by bruce »

KroontjesPen wrote:Both links in the start post give here blank pages now with NO ok. That's the same for server 171.67.108.17.
This has been reported elsewhere. The Pande Group made a small change to the servers to solve another problem and now the OK message wants to download rather than display (though it's actually still there). I don't know if the OK web-page will be back or not.
Amaruk
Posts: 254
Joined: Fri Jun 20, 2008 3:57 am
Location: Watching from the Woods

Re: 171.64.65.111 & 171.67.108.17 Not functional

Post by Amaruk »

Unable to return Project 4104 (Run 66, Clone 4, Gen 14). 171.64.65.111 is in REJECT (CPU load is 9.25) The collection server (171.67.108.17) won't take it either, but it's Net load is pretty high - probably busy trying to take in WUs rejected by 171.64.65.111

Here's the log between completion of 4104 and when I stopped the client.

Code: Select all

[22:39:54] Folding@home Core Shutdown: FINISHED_UNIT
[22:39:56] CoreStatus = 64 (100)
[22:39:56] Unit 5 finished with 96 percent of time to deadline remaining.
[22:39:56] Updated performance fraction: 0.958856
[22:39:56] Sending work to server
[22:39:56] Project: 4104 (Run 66, Clone 4, Gen 14)


[22:39:56] + Attempting to send results [February 6 22:39:56 UTC]
[22:39:56] - Reading file work/wuresults_05.dat from core
[22:39:56]   (Read 3244423 bytes from disk)
[22:39:56] Connecting to http://171.64.65.111:8080/
[22:39:57] - Couldn't send HTTP request to server
[22:39:57] + Could not connect to Work Server (results)
[22:39:57]     (171.64.65.111:8080)
[22:39:57] + Retrying using alternative port
[22:39:57] Connecting to http://171.64.65.111:80/
[22:39:58] - Couldn't send HTTP request to server
[22:39:58] + Could not connect to Work Server (results)
[22:39:58]     (171.64.65.111:80)
[22:39:58] - Error: Could not transmit unit 05 (completed February 6) to work server.
[22:39:58] - 1 failed uploads of this unit.
[22:39:58]   Keeping unit 05 in queue.
[22:39:58] Trying to send all finished work units
[22:39:58] Project: 4104 (Run 66, Clone 4, Gen 14)


[22:39:58] + Attempting to send results [February 6 22:39:58 UTC]
[22:39:58] - Reading file work/wuresults_05.dat from core
[22:39:58]   (Read 3244423 bytes from disk)
[22:39:58] Connecting to http://171.64.65.111:8080/
[22:40:00] - Couldn't send HTTP request to server
[22:40:00] + Could not connect to Work Server (results)
[22:40:00]     (171.64.65.111:8080)
[22:40:00] + Retrying using alternative port
[22:40:00] Connecting to http://171.64.65.111:80/
[22:40:01] - Couldn't send HTTP request to server
[22:40:01] + Could not connect to Work Server (results)
[22:40:01]     (171.64.65.111:80)
[22:40:01] - Error: Could not transmit unit 05 (completed February 6) to work server.
[22:40:01] - 2 failed uploads of this unit.


[22:40:01] + Attempting to send results [February 6 22:40:01 UTC]
[22:40:01] - Reading file work/wuresults_05.dat from core
[22:40:01]   (Read 3244423 bytes from disk)
[22:40:01] Connecting to http://171.67.108.17:8080/
[22:40:01] - Couldn't send HTTP request to server
[22:40:01] + Could not connect to Work Server (results)
[22:40:01]     (171.67.108.17:8080)
[22:40:01] + Retrying using alternative port
[22:40:01] Connecting to http://171.67.108.17:80/
[22:40:01] - Couldn't send HTTP request to server
[22:40:01] + Could not connect to Work Server (results)
[22:40:01]     (171.67.108.17:80)
[22:40:01]   Could not transmit unit 05 to Collection server; keeping in queue.
[22:40:01] + Sent 0 of 1 completed units to the server
[22:40:01] - Preparing to get new work unit...
[22:40:01] + Attempting to get work packet
[22:40:01] - Will indicate memory of 1023 MB
[22:40:01] - Connecting to assignment server
[22:40:01] Connecting to http://assign.stanford.edu:8080/
[22:40:02] Posted data.
[22:40:02] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[22:40:02] + News From Folding@Home: Welcome to Folding@Home
[22:40:02] Loaded queue successfully.
[22:40:02] Connecting to http://171.67.108.13:8080/
[22:40:02] Posted data.
[22:40:02] Initial: 0000; + Could not connect to Work Server
[22:40:02] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[22:40:11] + Attempting to get work packet
[22:40:11] - Will indicate memory of 1023 MB
[22:40:11] - Connecting to assignment server
[22:40:11] Connecting to http://assign.stanford.edu:8080/
[22:40:11] Posted data.
[22:40:11] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[22:40:11] + News From Folding@Home: Welcome to Folding@Home
[22:40:11] Loaded queue successfully.
[22:40:11] Connecting to http://171.67.108.13:8080/
[22:40:12] Posted data.
[22:40:12] Initial: 0000; + Could not connect to Work Server
[22:40:12] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[22:40:30] + Attempting to get work packet
[22:40:30] - Will indicate memory of 1023 MB
[22:40:30] - Connecting to assignment server
[22:40:30] Connecting to http://assign.stanford.edu:8080/
[22:40:30] Posted data.
[22:40:30] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[22:40:30] + News From Folding@Home: Welcome to Folding@Home
[22:40:30] Loaded queue successfully.
[22:40:30] Connecting to http://171.67.108.13:8080/
[22:40:31] Posted data.
[22:40:31] Initial: 0000; + Could not connect to Work Server
[22:40:31] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[22:40:55] + Attempting to get work packet
[22:40:55] - Will indicate memory of 1023 MB
[22:40:55] - Connecting to assignment server
[22:40:55] Connecting to http://assign.stanford.edu:8080/
[22:40:55] Posted data.
[22:40:55] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[22:40:55] + News From Folding@Home: Welcome to Folding@Home
[22:40:55] Loaded queue successfully.
[22:40:55] Connecting to http://171.67.108.13:8080/
[22:40:55] Posted data.
[22:40:55] Initial: 0000; + Could not connect to Work Server
[22:40:55] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[22:41:45] + Attempting to get work packet
[22:41:45] - Will indicate memory of 1023 MB
[22:41:45] - Connecting to assignment server
[22:41:45] Connecting to http://assign.stanford.edu:8080/
[22:41:45] Posted data.
[22:41:45] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[22:41:45] + News From Folding@Home: Welcome to Folding@Home
[22:41:45] Loaded queue successfully.
[22:41:45] Connecting to http://171.67.108.13:8080/
[22:41:45] Posted data.
[22:41:45] Initial: 0000; + Could not connect to Work Server
[22:41:45] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[22:43:15] + Attempting to get work packet
[22:43:15] - Will indicate memory of 1023 MB
[22:43:15] - Connecting to assignment server
[22:43:15] Connecting to http://assign.stanford.edu:8080/
[22:43:15] Posted data.
[22:43:15] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[22:43:15] + News From Folding@Home: Welcome to Folding@Home
[22:43:15] Loaded queue successfully.
[22:43:15] Connecting to http://171.67.108.13:8080/
[22:43:15] Posted data.
[22:43:16] Initial: 0000; + Could not connect to Work Server
[22:43:16] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[22:46:10] + Attempting to get work packet
[22:46:10] - Will indicate memory of 1023 MB
[22:46:10] - Connecting to assignment server
[22:46:10] Connecting to http://assign.stanford.edu:8080/
[22:46:11] Posted data.
[22:46:11] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[22:46:11] + News From Folding@Home: Welcome to Folding@Home
[22:46:11] Loaded queue successfully.
[22:46:11] Connecting to http://171.67.108.13:8080/
[22:46:11] Posted data.
[22:46:11] Initial: 0000; + Could not connect to Work Server
[22:46:11] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[22:51:42] + Attempting to get work packet
[22:51:42] - Will indicate memory of 1023 MB
[22:51:42] - Connecting to assignment server
[22:51:42] Connecting to http://assign.stanford.edu:8080/
[22:51:42] Posted data.
[22:51:42] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[22:51:42] + Couldn't get work instructions.
[22:51:42] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[23:02:26] + Attempting to get work packet
[23:02:26] - Will indicate memory of 1023 MB
[23:02:26] - Connecting to assignment server
[23:02:26] Connecting to http://assign.stanford.edu:8080/
[23:02:26] Posted data.
[23:02:26] Initial: 40AB; - Successful: assigned to (171.64.122.136).
[23:02:26] + News From Folding@Home: Welcome to Folding@Home
[23:02:26] Loaded queue successfully.
[23:02:26] Connecting to http://171.64.122.136:8080/
[23:02:26] Posted data.
[23:02:26] Initial: 0000; + Could not connect to Work Server
[23:02:26] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[23:23:47] + Attempting to get work packet
[23:23:47] - Will indicate memory of 1023 MB
[23:23:47] - Connecting to assignment server
[23:23:47] Connecting to http://assign.stanford.edu:8080/
[23:23:47] Posted data.
[23:23:47] Initial: 43AB; - Successful: assigned to (171.67.108.13).
[23:23:47] + News From Folding@Home: Welcome to Folding@Home
[23:23:47] Loaded queue successfully.
[23:23:47] Connecting to http://171.67.108.13:8080/
[23:23:51] Posted data.
[23:23:51] Initial: 0000; + Could not connect to Work Server
[23:23:51] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[23:33:35] ***** Got a SIGTERM signal (2)
[23:33:35] Killing all core threads

Folding@Home Client Shutdown.

This is restart. Got more work, but still unable to return 4104 WU yet.

Code: Select all

--- Opening Log file [February 6 23:33:43 UTC] 


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.20

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Documents and Settings\Chow\My Documents\Folding@Home
Executable: C:\Documents and Settings\Chow\My Documents\Folding@Home\Folding@home-Win32-x86.exe
Arguments: -verbosity 9 -local 

[23:33:43] - Ask before connecting: No
[23:33:43] - User name: Amaruk (Team 50625)
[23:33:43] - User ID: 2D76848C0220E162
[23:33:43] - Machine ID: 1
[23:33:43] 
[23:33:43] Loaded queue successfully.
[23:33:43] - Preparing to get new work unit...
[23:33:43] + Attempting to get work packet
[23:33:43] - Autosending finished units... [February 6 23:33:43 UTC]
[23:33:43] Trying to send all finished work units
[23:33:43] Project: 4104 (Run 66, Clone 4, Gen 14)
[23:33:43] - Will indicate memory of 1023 MB
[23:33:43] - Detect CPU. Vendor: AuthenticAMD, Family: 6, Model: 10, Stepping: 0
[23:33:43] - Connecting to assignment server


[23:33:43] + Attempting to send results [February 6 23:33:43 UTC]
[23:33:43] - Reading file work/wuresults_05.dat from core
[23:33:43]   (Read 3244423 bytes from disk)
[23:33:43] Connecting to http://assign.stanford.edu:8080/
[23:33:43] Connecting to http://171.64.65.111:8080/
[23:33:43] Posted data.
[23:33:43] Initial: 43AB; - Successful: assigned to (171.67.108.12).
[23:33:43] + News From Folding@Home: Welcome to Folding@Home
[23:33:43] Loaded queue successfully.
[23:33:43] Connecting to http://171.67.108.12:8080/
[23:33:44] - Couldn't send HTTP request to server
[23:33:44] + Could not connect to Work Server (results)
[23:33:44]     (171.64.65.111:8080)
[23:33:44] + Retrying using alternative port
[23:33:44] Connecting to http://171.64.65.111:80/
[23:33:45] - Couldn't send HTTP request to server
[23:33:45] + Could not connect to Work Server (results)
[23:33:45]     (171.64.65.111:80)
[23:33:45] - Error: Could not transmit unit 05 (completed February 6) to work server.
[23:33:45] - 3 failed uploads of this unit.


[23:33:45] + Attempting to send results [February 6 23:33:45 UTC]
[23:33:45] - Reading file work/wuresults_05.dat from core
[23:33:45]   (Read 3244423 bytes from disk)
[23:33:45] Connecting to http://171.67.108.17:8080/
[23:33:45] Posted data.
[23:33:45] Initial: 0000; - Receiving payload (expected size: 1158549)
[23:33:45] - Couldn't send HTTP request to server
[23:33:45] + Could not connect to Work Server (results)
[23:33:45]     (171.67.108.17:8080)
[23:33:45] + Retrying using alternative port
[23:33:45] Connecting to http://171.67.108.17:80/
[23:33:45] - Couldn't send HTTP request to server
[23:33:45] + Could not connect to Work Server (results)
[23:33:45]     (171.67.108.17:80)
[23:33:45]   Could not transmit unit 05 to Collection server; keeping in queue.
[23:33:45] + Sent 0 of 1 completed units to the server
[23:33:45] - Autosend completed
[23:33:47] - Downloaded at ~565 kB/s
[23:33:47] - Averaged speed for that direction ~467 kB/s
[23:33:47] + Received work.
[23:33:47] + Closed connections
[23:33:47] 
[23:33:47] + Processing work unit
[23:33:47] Core required: FahCore_a0.exe
[23:33:47] Core found.
[23:33:47] Working on queue slot 06 [February 6 23:33:47 UTC]
[23:33:47] + Working ...
[23:33:47] - Calling '.\FahCore_a0.exe -dir work/ -suffix 06 -checkpoint 15 -verbose -lifeline 1564 -version 620'

[23:33:47] 
[23:33:47] *------------------------------*
[23:33:47] Folding@Home Gromacs 3.3 Core
[23:33:47] Version 1.93 (July 23, 2008)
[23:33:47] 
[23:33:47] Preparing to commence simulation
[23:33:47] - Looking at optimizations...
[23:33:47] - Created dyn
[23:33:47] - Files status OK
[23:33:48] - Expanded 1158037 -> 6173133 (decompressed 533.0 percent)
[23:33:48] - Starting from initial work packet
[23:33:48] 
[23:33:48] Project: 5113 (Run 99, Clone 1, Gen 11)
[23:33:48] 
[23:33:48] Assembly optimizations on if available.
[23:33:48] Entering M.D.
[23:33:54] Rejecting checkpoint
[23:33:55] Protein: Calmodulin in water
[23:33:55] Writing local files
[23:33:58] Extra SSE boost OK.
[23:33:59] Writing local files
[23:33:59] Completed 0 out of 500000 steps  (0 percent)
[23:49:00] Timered checkpoint triggered.
[00:04:01] Timered checkpoint triggered.
[00:19:02] Timered checkpoint triggered.
[00:20:20] Writing local files
[00:20:20] Completed 5000 out of 500000 steps  (1 percent)
[00:35:21] Timered checkpoint triggered.
[00:50:22] Timered checkpoint triggered.
[01:05:23] Timered checkpoint triggered.
[01:06:42] Writing local files
[01:06:43] Completed 10000 out of 500000 steps  (2 percent)
[01:21:43] Timered checkpoint triggered.
[01:36:44] Timered checkpoint triggered.
[01:51:46] Timered checkpoint triggered.
[01:54:22] Writing local files
[01:54:22] Completed 15000 out of 500000 steps  (3 percent)
[02:09:23] Timered checkpoint triggered.
[02:24:23] Timered checkpoint triggered.
[02:41:31] Timered checkpoint triggered.
[02:45:50] Writing local files
[02:45:50] Completed 20000 out of 500000 steps  (4 percent)
[02:55:48] ***** Got a SIGTERM signal (2)
[02:55:48] Killing all core threads

Folding@Home Client Shutdown.


--- Opening Log file [February 7 02:55:54 UTC] 


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.20

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Documents and Settings\Chow\My Documents\Folding@Home
Executable: C:\Documents and Settings\Chow\My Documents\Folding@Home\Folding@home-Win32-x86.exe
Arguments: -verbosity 9 -local 

[02:55:54] - Ask before connecting: No
[02:55:54] - User name: Amaruk (Team 50625)
[02:55:54] - User ID: 2D76848C0220E162
[02:55:54] - Machine ID: 1
[02:55:54] 
[02:55:54] Loaded queue successfully.
[02:55:54] 
[02:55:54] + Processing work unit
[02:55:54] - Autosending finished units... [February 7 02:55:54 UTC]
[02:55:54] Trying to send all finished work units
[02:55:54] Project: 4104 (Run 66, Clone 4, Gen 14)


[02:55:54] + Attempting to send results [February 7 02:55:54 UTC]
[02:55:54] Core required: FahCore_a0.exe
[02:55:54] Core found.
[02:55:54] - Reading file work/wuresults_05.dat from core
[02:55:54]   (Read 3244423 bytes from disk)
[02:55:54] Connecting to http://171.64.65.111:8080/
[02:55:54] Working on queue slot 06 [February 7 02:55:54 UTC]
[02:55:54] + Working ...
[02:55:54] - Calling '.\FahCore_a0.exe -dir work/ -suffix 06 -checkpoint 15 -verbose -lifeline 1768 -version 620'

[02:55:54] 
[02:55:54] *------------------------------*
[02:55:54] Folding@Home Gromacs 3.3 Core
[02:55:54] Version 1.93 (July 23, 2008)
[02:55:54] 
[02:55:54] Preparing to commence simulation
[02:55:54] - Looking at optimizations...
[02:55:54] - Files status OK
[02:55:55] - Couldn't send HTTP request to server
[02:55:55] + Could not connect to Work Server (results)
[02:55:55]     (171.64.65.111:8080)
[02:55:55] + Retrying using alternative port
[02:55:55] Connecting to http://171.64.65.111:80/
[02:55:56] - Expanded 1158037 -> 6173133 (decompressed 533.0 percent)
[02:55:56] 
[02:55:56] Project: 5113 (Run 99, Clone 1, Gen 11)
[02:55:56] 
[02:55:56] Assembly optimizations on if available.
[02:55:56] Entering M.D.
[02:55:57] - Couldn't send HTTP request to server
[02:55:57] + Could not connect to Work Server (results)
[02:55:57]     (171.64.65.111:80)
[02:55:57] - Error: Could not transmit unit 05 (completed February 6) to work server.
[02:55:57] - 4 failed uploads of this unit.


[02:55:57] + Attempting to send results [February 7 02:55:57 UTC]
[02:55:57] - Reading file work/wuresults_05.dat from core
[02:55:57]   (Read 3244423 bytes from disk)
[02:55:57] Connecting to http://171.67.108.17:8080/
[02:55:57] - Couldn't send HTTP request to server
[02:55:57] + Could not connect to Work Server (results)
[02:55:57]     (171.67.108.17:8080)
[02:55:57] + Retrying using alternative port
[02:55:57] Connecting to http://171.67.108.17:80/
[02:55:57] - Couldn't send HTTP request to server
[02:55:57] + Could not connect to Work Server (results)
[02:55:57]     (171.67.108.17:80)
[02:55:57]   Could not transmit unit 05 to Collection server; keeping in queue.
[02:55:57] + Sent 0 of 1 completed units to the server
[02:55:57] - Autosend completed
[02:56:02] FAH Init
[02:56:02] Checkpoint file: 
[02:56:07] (Starting from checkpoint)
[02:56:07] Read checkpoint
[02:56:07] Protein: Calmodulin in water
[02:56:08] Writing local files
[02:56:10] Completed 20000 out of 500000 steps  (4 percent)
[02:56:10] Extra SSE boost OK.
[03:11:12] Timered checkpoint triggered.
Perhaps giving the server a 'gentle' nudge will help... :lol:



bruce wrote:
KroontjesPen wrote:Both links in the start post give here blank pages now with NO ok. That's the same for server 171.67.108.17.
This has been reported elsewhere. The Pande Group made a small change to the servers to solve another problem and now the OK message wants to download rather than display (though it's actually still there). I don't know if the OK web-page will be back or not.
I hope it comes back, since it provided positive feedback regarding one's ability to connect to the server.
Image
Post Reply