171.64.65.56
Posted: Tue Apr 21, 2009 9:59 am
Just running out the door at the moment, but haven't been able to conect to .65.56 for the past half hour, not even an OK on a ping.
Page 1 of 2
Re: .65.56
Posted: Tue Apr 21, 2009 10:03 am
Indeed, it's in Reject mode ...
Re: .65.56
Posted: Tue Apr 21, 2009 3:12 pm
restarted the code; it should be ready shortly
171.64.65.56
Posted: Mon Apr 27, 2009 11:26 pm
In Reject.
Re: 171.64.65.56
Posted: Tue Apr 28, 2009 12:15 am
Yes, it has been down for several hours for me. I restarted my client and it downloaded a new WU from a different server so at least it is doing something.
It would appear this server is overloaded. Hopefully they will look into setting up another one to split the load. As long as I can send my WU's before they expire I'm not too concerned but getting them in sooner is better for everyone.
It would appear this server is overloaded. Hopefully they will look into setting up another one to split the load. As long as I can send my WU's before they expire I'm not too concerned but getting them in sooner is better for everyone.
Re: 171.64.65.56
Posted: Tue Apr 28, 2009 12:28 am
Appears to be back up now, I just successfully uploaded and download some work.
Re: 171.64.65.56
Posted: Fri May 01, 2009 8:22 pm
Code: Select all
[18:50:22] Completed 245000 out of 250000 steps (98%)
[18:59:25] Completed 247500 out of 250000 steps (99%)
[19:08:28] Completed 250000 out of 250000 steps (100%)
[19:08:29] DynamicWrapper: Finished Work Unit: sleep=10000
[19:08:39]
[19:08:39] Finished Work Unit:
[19:08:39] - Reading up to 21147552 from "work/wudata_04.trr": Read 21147552
[19:08:40] trr file hash check passed.
[19:08:40] - Reading up to 4478024 from "work/wudata_04.xtc": Read 4478024
[19:08:40] xtc file hash check passed.
[19:08:40] edr file hash check passed.
[19:08:40] logfile size: 197033
[19:08:40] Leaving Run
[19:08:43] - Writing 25967361 bytes of core data to disk...
[19:08:44] ... Done.
[19:08:50] - Shutting down core
[19:08:50]
[19:08:50] Folding@home Core Shutdown: FINISHED_UNIT
[19:12:05] CoreStatus = 64 (100)
[19:12:05] Unit 4 finished with 74 percent of time to deadline remaining.
[19:12:05] Updated performance fraction: 0.759067
[19:12:05] Sending work to server
[19:12:05] Project: 2675 (Run 2, Clone 128, Gen 51)
[19:12:05] + Attempting to send results [May 1 19:12:05 UTC]
[19:12:05] - Reading file work/wuresults_04.dat from core
[19:12:05] (Read 25967361 bytes from disk)
[19:12:05] Connecting to http://171.64.65.56:8080/
[19:15:14] - Couldn't send HTTP request to server
[19:15:14] + Could not connect to Work Server (results)
[19:15:14] (171.64.65.56:8080)
[19:15:14] + Retrying using alternative port
[19:15:14] Connecting to http://171.64.65.56:80/
[19:18:23] - Couldn't send HTTP request to server
[19:18:23] + Could not connect to Work Server (results)
[19:18:23] (171.64.65.56:80)
[19:18:23] - Error: Could not transmit unit 04 (completed May 1) to work server.
[19:18:23] - 1 failed uploads of this unit.
[19:18:23] Keeping unit 04 in queue.
[19:18:23] Trying to send all finished work units
[19:18:23] Project: 2675 (Run 2, Clone 128, Gen 51)
[19:18:23] + Attempting to send results [May 1 19:18:23 UTC]
[19:18:23] - Reading file work/wuresults_04.dat from core
[19:18:23] (Read 25967361 bytes from disk)
[19:18:23] Connecting to http://171.64.65.56:8080/
[19:21:32] - Couldn't send HTTP request to server
[19:21:32] + Could not connect to Work Server (results)
[19:21:32] (171.64.65.56:8080)
[19:21:32] + Retrying using alternative port
[19:21:32] Connecting to http://171.64.65.56:80/
[19:24:41] - Couldn't send HTTP request to server
[19:24:41] + Could not connect to Work Server (results)
[19:24:41] (171.64.65.56:80)
[19:24:41] - Error: Could not transmit unit 04 (completed May 1) to work server.
[19:24:41] - 2 failed uploads of this unit.
[19:24:41] + Attempting to send results [May 1 19:24:41 UTC]
[19:24:41] - Reading file work/wuresults_04.dat from core
[19:24:41] (Read 25967361 bytes from disk)
[19:24:41] Connecting to http://171.67.108.25:8080/
[19:27:50] - Couldn't send HTTP request to server
[19:27:50] + Could not connect to Work Server (results)
[19:27:50] (171.67.108.25:8080)
[19:27:50] + Retrying using alternative port
[19:27:50] Connecting to http://171.67.108.25:80/
[19:30:59] - Couldn't send HTTP request to server
[19:30:59] + Could not connect to Work Server (results)
[19:30:59] (171.67.108.25:80)
[19:30:59] Could not transmit unit 04 to Collection server; keeping in queue.
[19:30:59] + Sent 0 of 1 completed units to the server
[19:30:59] - Preparing to get new work unit...
[19:30:59] + Attempting to get work packet
[19:30:59] - Will indicate memory of 563 MB
[19:30:59] - Connecting to assignment server
[19:30:59] Connecting to http://assign.stanford.edu:8080/
[19:34:09] - Couldn't send HTTP request to server
[19:34:09] + Could not connect to Assignment Server
[19:34:09] Connecting to http://assign2.stanford.edu:80/
[19:37:18] - Couldn't send HTTP request to server
[19:37:18] + Could not connect to Assignment Server 2
[19:37:18] + Couldn't get work instructions.
[19:37:18] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[19:37:24] + Attempting to get work packet
[19:37:24] - Will indicate memory of 563 MB
[19:37:24] - Connecting to assignment server
[19:37:24] Connecting to http://assign.stanford.edu:8080/
[19:40:33] - Couldn't send HTTP request to server
[19:40:33] + Could not connect to Assignment Server
[19:40:33] Connecting to http://assign2.stanford.edu:80/
[19:43:42] - Couldn't send HTTP request to server
[19:43:42] + Could not connect to Assignment Server 2
[19:43:42] + Couldn't get work instructions.
[19:43:42] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[19:43:55] + Attempting to get work packet
[19:43:55] - Will indicate memory of 563 MB
[19:43:55] - Connecting to assignment server
[19:43:55] Connecting to http://assign.stanford.edu:8080/
[19:47:04] - Couldn't send HTTP request to server
[19:47:04] + Could not connect to Assignment Server
[19:47:04] Connecting to http://assign2.stanford.edu:80/
[19:50:13] - Couldn't send HTTP request to server
[19:50:13] + Could not connect to Assignment Server 2
[19:50:13] + Couldn't get work instructions.
[19:50:13] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[19:50:36] + Attempting to get work packet
[19:50:36] - Will indicate memory of 563 MB
[19:50:36] - Connecting to assignment server
[19:50:36] Connecting to http://assign.stanford.edu:8080/
[19:53:45] - Couldn't send HTTP request to server
[19:53:45] + Could not connect to Assignment Server
[19:53:45] Connecting to http://assign2.stanford.edu:80/
[19:56:54] - Couldn't send HTTP request to server
[19:56:54] + Could not connect to Assignment Server 2
[19:56:54] + Couldn't get work instructions.
[19:56:54] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[19:57:47] + Attempting to get work packet
[19:57:47] - Will indicate memory of 563 MB
[19:57:47] - Connecting to assignment server
[19:57:47] Connecting to http://assign.stanford.edu:8080/
[20:00:56] - Couldn't send HTTP request to server
[20:00:56] + Could not connect to Assignment Server
[20:00:56] Connecting to http://assign2.stanford.edu:80/
[20:04:05] - Couldn't send HTTP request to server
[20:04:05] + Could not connect to Assignment Server 2
[20:04:05] + Couldn't get work instructions.
[20:04:05] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[20:05:30] + Attempting to get work packet
[20:05:30] - Will indicate memory of 563 MB
[20:05:30] - Connecting to assignment server
[20:05:30] Connecting to http://assign.stanford.edu:8080/
[20:08:39] - Couldn't send HTTP request to server
[20:08:39] + Could not connect to Assignment Server
[20:08:39] Connecting to http://assign2.stanford.edu:80/
[20:11:48] - Couldn't send HTTP request to server
[20:11:48] + Could not connect to Assignment Server 2
[20:11:48] + Couldn't get work instructions.
[20:11:48] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[20:14:31] + Attempting to get work packet
[20:14:31] - Will indicate memory of 563 MB
[20:14:31] - Connecting to assignment server
[20:14:31] Connecting to http://assign.stanford.edu:8080/
[20:17:40] - Couldn't send HTTP request to server
[20:17:40] + Could not connect to Assignment Server
[20:17:40] Connecting to http://assign2.stanford.edu:80/
[20:20:49] - Couldn't send HTTP request to server
[20:20:49] + Could not connect to Assignment Server 2
[20:20:49] + Couldn't get work instructions.
[20:20:49] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.Re: 171.64.65.56
Posted: Fri May 01, 2009 10:50 pm
Please verify whether the same addresses work in your browser:
http://171.64.65.56:8080/
http://171.64.65.56:80/
http://assign2.stanford.edu/
http://assign.stanford.edu:8080/
If none of them work, your ISP must be having a routing problem, because they work from here. If they do work and the FAH client can still not connect, the problem is in your internet security software which is blocking the client from connecting to the internet.
http://171.64.65.56:8080/
http://171.64.65.56:80/
http://assign2.stanford.edu/
http://assign.stanford.edu:8080/
If none of them work, your ISP must be having a routing problem, because they work from here. If they do work and the FAH client can still not connect, the problem is in your internet security software which is blocking the client from connecting to the internet.
Re: 171.64.65.56
Posted: Sun May 03, 2009 11:42 am
Thankssbruce wrote:Please verify whether the same addresses work in your browser:
http://171.64.65.56:8080/
http://171.64.65.56:80/
http://assign2.stanford.edu/
http://assign.stanford.edu:8080/
If none of them work, your ISP must be having a routing problem, because they work from here. If they do work and the FAH client can still not connect, the problem is in your internet security software which is blocking the client from connecting to the internet.
got it sorted out already
Re: 171.64.65.56
Posted: Mon May 04, 2009 5:09 am
In REJECT status again.
Please reset. Thanks!
Please reset. Thanks!
Re: 171.64.65.56
Posted: Mon May 04, 2009 5:29 am
When I try to reach 171.64.65.56 from my Macs, I get the "Failed to Connect" from Firefox for both the 8080 port and the 80 port. The "assign2.stanford.edu" URLs come back with "OK" like they're supposed to.bruce wrote:Please verify whether the same addresses work in your browser:
http://171.64.65.56:8080/
http://171.64.65.56:80/
http://assign2.stanford.edu/
http://assign.stanford.edu:8080/
If none of them work, your ISP must be having a routing problem, because they work from here. If they do work and the FAH client can still not connect, the problem is in your internet security software which is blocking the client from connecting to the internet.
I issued a Traceroute from my Mac Pro and got the following:
Code: Select all
Last login: Wed Apr 22 08:27:11 on console
Welcome to Darwin!
FoxMacPro266:~ Foxbat$ traceroute 171.64.65.56
traceroute to 171.64.65.56 (171.64.65.56), 64 hops max, 40 byte packets
1 10.40.41.1 (10.40.41.1) 2.657 ms 2.364 ms 2.394 ms
2 adsl-70-224-63-254.dsl.sbndin.ameritech.net (70.224.63.254) 19.074 ms 41.283 ms 18.810 ms
3 dist2-vlan50.sbndin.sbcglobal.net (65.43.5.227) 20.636 ms 21.425 ms 19.943 ms
4 bb1-g1-0.sbndin.sbcglobal.net (65.43.5.99) 19.889 ms 20.318 ms 108.010 ms
5 151.164.95.164 (151.164.95.164) 21.877 ms 21.703 ms 21.925 ms
6 te7-2.ccr02.ord03.atlas.cogentco.com (154.54.11.237) 22.013 ms 21.992 ms 24.027 ms
7 vl3499.mpd02.ord01.atlas.cogentco.com (154.54.5.9) 21.892 ms vl3491.ccr02.ord01.atlas.cogentco.com (154.54.6.209) 30.929 ms te3-4.mpd02.ord01.atlas.cogentco.com (154.54.25.69) 23.544 ms
8 te7-4.ccr02.mci01.atlas.cogentco.com (66.28.4.33) 54.386 ms te4-2.ccr02.mci01.atlas.cogentco.com (154.54.6.253) 50.504 ms te4-3.ccr02.mci01.atlas.cogentco.com (154.54.6.201) 49.471 ms
9 te2-4.ccr02.sfo01.atlas.cogentco.com (154.54.24.109) 72.287 ms 70.446 ms 75.271 ms
10 te9-1.mpd01.sjc04.atlas.cogentco.com (154.54.0.178) 74.749 ms 72.023 ms 93.351 ms
11 stanford_university2.demarc.cogentco.com (66.250.7.138) 74.356 ms 72.408 ms 73.884 ms
12 bbrb-isp.stanford.edu (171.64.1.155) 71.848 ms 74.110 ms 89.999 ms
13 * * *
14 * * *
15 vspg4.stanford.edu (171.64.65.56) 101.683 ms !<10> 93.222 ms !<10> 72.352 ms !<10>
FoxMacPro266:~ Foxbat$Re: .65.56
Posted: Mon May 04, 2009 5:34 am
Rejecting once again and has been for a while.
Are you awake kasson?
Need code restart please.
Thanks! (as usual)
Are you awake kasson?
Need code restart please.
Thanks! (as usual)
Re: .65.56
Posted: Mon May 04, 2009 7:10 am
All is now well. Thank you "server" or thank you PG member!
I hope that it remains well in about 5 hours when good old autosend does its trick.
I hope that it remains well in about 5 hours when good old autosend does its trick.
Re: 171.64.65.56
Posted: Sat May 09, 2009 7:34 pm
171.64.65.56 SMP vspg4 kasson full Reject
Re: 171.64.65.56
Posted: Sat May 09, 2009 7:41 pm
Somebody need to go over and kick it. I have 4 completed WU's waiting for it.