Page 1 of 4
Can't connect 171.67.108.17 and 171.64.65.111
Posted: Sat Feb 20, 2010 9:58 am
by hisui
Both server can't be accessed via browser.171.64.65.111:8080 is time out,171.67.108.17:8080 is an blank page with no"OK"sign or
an error message returned from browser"The service is overloaded or offline. Please try again later."
According to server status page 171.64.65.111 is not accepting in standby mode but 171.67.108.17 is working
below is the error log form folding client
Code: Select all
Launch directory: E:\Folding@Home2
Arguments: -advmethods
[09:36:18] - Ask before connecting: No
[09:36:18] - Use IE connection settings: Yes
[09:36:18] - User name: Hisui (Team 0)
[09:36:18] - User ID: 5D4AFA2030185375
[09:36:18] - Machine ID: 1
[09:36:18]
[09:36:18] Loaded queue successfully.
[09:36:18] Initialization complete
[09:36:18] + Benchmarking ...
[09:36:22]
[09:36:22] + Processing work unit
[09:36:22] + Attempting to send results
[09:36:22] Core required: FahCore_78.exe
[09:36:22] Core found.
[09:36:22] Working on Unit 09 [February 20 09:36:22]
[09:36:22] + Working ...
[09:36:22]
[09:36:22] *------------------------------*
[09:36:22] Folding@Home Gromacs Core
[09:36:22] Version 1.90 (March 8, 2006)
[09:36:22]
[09:36:22] Preparing to commence simulation
[09:36:22] - Looking at optimizations...
[09:36:22] - Files status OK
[09:36:23] Couldn't send HTTP request to server (wininet)
[09:36:23] + Could not connect to Work Server (results)
[09:36:23] (171.64.65.111:8080)
[09:36:23] - Error: Could not transmit unit 08 (completed February 19) to work server.
[09:36:23] + Attempting to send results
[09:36:24] Error: Got status code 503 from server
[09:36:24] + Could not connect to Work Server (results)
[09:36:24] ()
[09:36:24] Could not transmit unit 08 to Collection server; keeping in queue.
[09:36:25] - Expanded 2964665 -> 15110909 (decompressed 509.7 percent)
Re: Can't connect 171.67.108.17 and 171.67.108.17
Posted: Sat Feb 20, 2010 2:56 pm
by JeansOn
I confirm the previous message.
Totaly I have two finished WUs waiting for upload
Code: Select all
[13:08:09] Completed 500000 out of 500000 steps (100%)
[13:08:10] Writing final coordinates.
[13:08:10] Past main M.D. loop
[13:09:10]
[13:09:10] Finished Work Unit:
[13:09:10] - Reading up to 362448 from "work/wudata_08.arc": Read 362448
[13:09:10] - Reading up to 3559332 from "work/wudata_08.xtc": Read 3559332
[13:09:10] goefile size: 0
[13:09:10] logfile size: 975442
[13:09:10] Leaving Run
[13:09:11] - Writing 6682634 bytes of core data to disk...
[13:09:13] Done: 6682122 -> 4794785 (compressed to 71.7 percent)
[13:09:13] ... Done.
[13:09:13] - Shutting down core
[13:09:13]
[13:09:13] Folding@home Core Shutdown: FINISHED_UNIT
[13:09:17] CoreStatus = 64 (100)
[13:09:17] Sending work to server
[13:09:17] Project: 6313 (Run 438, Clone 22, Gen 15)
[13:09:17] - Read packet limit of 540015616... Set to 524286976.
[13:09:17] + Attempting to send results [February 20 13:09:17 UTC]
[13:09:18] - Couldn't send HTTP request to server
[13:09:18] + Could not connect to Work Server (results)
[13:09:18] (171.64.65.111:8080)
[13:09:18] + Retrying using alternative port
[13:09:20] - Couldn't send HTTP request to server
[13:09:20] + Could not connect to Work Server (results)
[13:09:20] (171.64.65.111:80)
[13:09:20] - Error: Could not transmit unit 08 (completed February 20) to work server.
[13:09:20] Keeping unit 08 in queue.
[13:09:20] Project: 6313 (Run 438, Clone 22, Gen 15)
[13:09:20] - Read packet limit of 540015616... Set to 524286976.
[13:09:20] + Attempting to send results [February 20 13:09:20 UTC]
[13:09:21] - Couldn't send HTTP request to server
[13:09:21] + Could not connect to Work Server (results)
[13:09:21] (171.64.65.111:8080)
[13:09:21] + Retrying using alternative port
[13:09:22] - Couldn't send HTTP request to server
[13:09:22] + Could not connect to Work Server (results)
[13:09:22] (171.64.65.111:80)
[13:09:22] - Error: Could not transmit unit 08 (completed February 20) to work server.
[13:09:22] - Read packet limit of 540015616... Set to 524286976.
[13:09:22] + Attempting to send results [February 20 13:09:22 UTC]
[13:09:23] - Couldn't send HTTP request to server
[13:09:23] + Could not connect to Work Server (results)
[13:09:23] (171.67.108.17:8080)
[13:09:23] + Retrying using alternative port
[13:09:24] - Couldn't send HTTP request to server
[13:09:24] + Could not connect to Work Server (results)
[13:09:24] (171.67.108.17:80)
[13:09:24] Could not transmit unit 08 to Collection server; keeping in queue.
[13:09:24] - Preparing to get new work unit...
[13:09:24] + Attempting to get work packet
[13:09:24] - Connecting to assignment server
[13:09:25] - Successful: assigned to (171.67.108.13).
[13:09:25] + News From Folding@Home: Welcome to Folding@Home
[13:09:25] Loaded queue successfully.
[13:09:27] Project: 6313 (Run 438, Clone 22, Gen 15)
[13:09:27] - Read packet limit of 540015616... Set to 524286976.
[13:09:27] + Attempting to send results [February 20 13:09:27 UTC]
[13:09:29] - Couldn't send HTTP request to server
[13:09:29] + Could not connect to Work Server (results)
[13:09:29] (171.64.65.111:8080)
[13:09:29] + Retrying using alternative port
[13:09:30] - Couldn't send HTTP request to server
[13:09:30] + Could not connect to Work Server (results)
[13:09:30] (171.64.65.111:80)
[13:09:30] - Error: Could not transmit unit 08 (completed February 20) to work server.
[13:09:30] - Read packet limit of 540015616... Set to 524286976.
[13:09:30] + Attempting to send results [February 20 13:09:30 UTC]
[13:09:31] - Couldn't send HTTP request to server
[13:09:31] + Could not connect to Work Server (results)
[13:09:31] (171.67.108.17:8080)
[13:09:31] + Retrying using alternative port
[13:09:32] - Couldn't send HTTP request to server
[13:09:32] + Could not connect to Work Server (results)
[13:09:32] (171.67.108.17:80)
[13:09:32] Could not transmit unit 08 to Collection server; keeping in queue.
[13:09:32] + Closed connections
[13:09:32]
[13:09:32] + Processing work unit
[13:09:32] Core required: FahCore_78.exe
[13:09:32] Core found.
[13:09:32] Working on queue slot 09 [February 20 13:09:32 UTC]
[13:09:32] + Working ...
[13:09:32]
[13:09:32] *------------------------------*
[13:09:32] Folding@Home Gromacs Core
[13:09:32] Version 1.90 (March 8, 2006)
[13:09:32]
[13:09:32] Preparing to commence simulation
[13:09:32] - Looking at optimizations...
[13:09:32] - Created dyn
[13:09:32] - Files status OK
[13:09:32] - Expanded 238527 -> 1167721 (decompressed 489.5 percent)
[13:09:32] - Starting from initial work packet
[13:09:32]
[13:09:32] Project: 4441 (Run 795, Clone 2, Gen 48)
[13:09:32]
[13:09:32] Assembly optimizations on if available.
[13:09:32] Entering M.D.
[13:09:38] Protein: p4441_Seq42_Amber03
[13:09:38]
[13:09:38] Writing local files
[13:10:54] Extra SSE boost OK.
[13:10:54] Writing local files
[13:10:54] Completed 0 out of 1500000 steps (0%)
[13:12:45]
Re: Can't connect 171.67.108.17 and 71.64.65.111
Posted: Sat Feb 20, 2010 3:05 pm
by chrisretusn
Code: Select all
[05:06:04] Project: 6313 (Run 700, Clone 62, Gen 5)
[23:49:14] Completed 500000 out of 500000 steps (100%)
[23:50:22] Folding@home Core Shutdown: FINISHED_UNIT
[23:50:23] CoreStatus = 64 (100)
[23:50:23] Unit 4 finished with 97 percent of time to deadline remaining.
[23:50:23] Updated performance fraction: 0.967115
[23:50:23] Sending work to server
[23:50:23] + Attempting to send results
[23:50:23] - Reading file work/wuresults_04.dat from core
[23:50:23] (Read 4733421 bytes from disk)
[23:50:23] Connecting to http://171.64.65.111:8080/
[23:50:23] - Couldn't send HTTP request to server
[23:50:23] + Could not connect to Work Server (results)
[23:50:23] (171.64.65.111:8080)
[23:50:23] - Error: Could not transmit unit 04 (completed February 19) to work server.
[23:50:23] - 1 failed uploads of this unit.
[23:50:23] Keeping unit 04 in queue.
[23:50:23] Trying to send all finished work units
[23:50:23] + Attempting to send results
[23:50:23] - Reading file work/wuresults_04.dat from core
[23:50:23] (Read 4733421 bytes from disk)
[23:50:23] Connecting to http://171.64.65.111:8080/
[23:50:23] - Couldn't send HTTP request to server
[23:50:23] + Could not connect to Work Server (results)
[23:50:23] (171.64.65.111:8080)
[23:50:23] - Error: Could not transmit unit 04 (completed February 19) to work server.
[23:50:23] - 2 failed uploads of this unit.
[23:50:23] + Attempting to send results
[23:50:23] - Reading file work/wuresults_04.dat from core
[23:50:23] (Read 4733421 bytes from disk)
[23:50:23] Connecting to http://171.67.108.17:8080/
[23:50:24] - Couldn't send HTTP request to server
[23:50:24] + Could not connect to Work Server (results)
[23:50:24] (171.67.108.17:8080)
[23:50:24] Could not transmit unit 04 to Collection server; keeping in queue.
[23:50:24] + Sent 0 of 1 completed units to the server
[23:50:32] Trying to send all finished work units
[23:50:32] + Attempting to send results
[23:50:32] - Reading file work/wuresults_04.dat from core
[23:50:32] (Read 4733421 bytes from disk)
[23:50:32] Connecting to http://171.64.65.111:8080/
[23:50:32] - Couldn't send HTTP request to server
[23:50:32] + Could not connect to Work Server (results)
[23:50:32] (171.64.65.111:8080)
[23:50:32] - Error: Could not transmit unit 04 (completed February 19) to work server.
[23:50:32] - 3 failed uploads of this unit.
[23:50:32] + Attempting to send results
[23:50:32] - Reading file work/wuresults_04.dat from core
[23:50:32] (Read 4733421 bytes from disk)
[23:50:32] Connecting to http://171.67.108.17:8080/
[23:50:33] - Couldn't send HTTP request to server
[23:50:33] + Could not connect to Work Server (results)
[23:50:33] (171.67.108.17:8080)
[23:50:33] Could not transmit unit 04 to Collection server; keeping in queue.
[23:50:33] + Sent 0 of 1 completed units to the server
[23:50:33] + Closed connections
[05:27:14] - Autosending finished units...
[05:27:14] Trying to send all finished work units
[05:27:14] + Attempting to send results
[05:27:14] - Reading file work/wuresults_04.dat from core
[05:27:14] (Read 4733421 bytes from disk)
[05:27:14] Connecting to http://171.64.65.111:8080/
[05:27:14] - Couldn't send HTTP request to server
[05:27:14] + Could not connect to Work Server (results)
[05:27:14] (171.64.65.111:8080)
[05:27:14] - Error: Could not transmit unit 04 (completed February 19) to work server.
[05:27:14] - 4 failed uploads of this unit.
[05:27:14] + Attempting to send results
[05:27:14] - Reading file work/wuresults_04.dat from core
[05:27:14] (Read 4733421 bytes from disk)
[05:27:14] Connecting to http://171.67.108.17:8080/
[05:27:15] - Couldn't send HTTP request to server
[05:27:15] + Could not connect to Work Server (results)
[05:27:15] (171.67.108.17:8080)
[05:27:15] Could not transmit unit 04 to Collection server; keeping in queue.
[05:27:15] + Sent 0 of 1 completed units to the server
[05:27:15] - Autosend completed
[11:27:15] - Autosending finished units...
[11:27:15] Trying to send all finished work units
[11:27:15] + Attempting to send results
[11:27:15] - Reading file work/wuresults_04.dat from core
[11:27:15] (Read 4733421 bytes from disk)
[11:27:15] Connecting to http://171.64.65.111:8080/
[11:27:15] - Couldn't send HTTP request to server
[11:27:15] + Could not connect to Work Server (results)
[11:27:15] (171.64.65.111:8080)
[11:27:15] - Error: Could not transmit unit 04 (completed February 19) to work server.
[11:27:15] - 5 failed uploads of this unit.
[11:27:15] + Attempting to send results
[11:27:15] - Reading file work/wuresults_04.dat from core
[11:27:15] (Read 4733421 bytes from disk)
[11:27:15] Connecting to http://171.67.108.17:8080/
[11:27:16] - Couldn't send HTTP request to server
[11:27:16] + Could not connect to Work Server (results)
[11:27:16] (171.67.108.17:8080)
[11:27:16] Could not transmit unit 04 to Collection server; keeping in queue.
[11:27:16] + Sent 0 of 1 completed units to the server
[11:27:16] - Autosend completed
Re: Can't connect 171.67.108.17 and 171.67.108.17
Posted: Sat Feb 20, 2010 3:45 pm
by John_Weatherman
Use IE connection settings: Yes
Change this to No and it'll work better.
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Sat Feb 20, 2010 4:02 pm
by VijayPande
We'll take a look.
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Sun Feb 21, 2010 5:02 am
by chrisretusn
Success!
Code: Select all
[22:26:10] - Autosending finished units...
[22:26:10] Trying to send all finished work units
[22:26:10] + Attempting to send results
[22:26:10] - Reading file work/wuresults_04.dat from core
[22:26:10] (Read 4733421 bytes from disk)
[22:26:10] Connecting to http://171.64.65.111:8080/
[22:26:11] - Couldn't send HTTP request to server
[22:26:11] + Could not connect to Work Server (results)
[22:26:11] (171.64.65.111:8080)
[22:26:11] - Error: Could not transmit unit 04 (completed February 19) to work server.
[22:26:11] - 7 failed uploads of this unit.
[22:26:11] + Attempting to send results
[22:26:11] - Reading file work/wuresults_04.dat from core
[22:26:11] (Read 4733421 bytes from disk)
[22:26:11] Connecting to http://171.67.108.17:8080/
[22:29:48] Timered checkpoint triggered.
[22:30:18] Posted data.
[22:30:18] Initial: 0000; - Uploaded at ~18 kB/s
[22:30:18] - Averaged speed for that direction ~17 kB/s
[22:30:18] + Results successfully sent
[22:30:18] Thank you for your contribution to Folding@Home.
[22:30:18] + Number of Units Completed: 30
[22:30:18] Successfully sent unit 04 to Collection server.
[22:30:19] + Sent 1 of 1 completed units to the server
[22:30:19] - Autosend completed
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Sun Apr 04, 2010 8:36 am
by KroontjesPen
It is not going well for a while now.
There are several problems with sending and receiving work.
Because the off the last problems now I put the data here.
This PC has no work to do for the moment and that is for the 4th time in 2 days.
Code: Select all
[07:34:52] Completed 2500000 out of 2500000 steps (100%)
[07:34:52] Writing checkpoint files
[07:35:52]
[07:35:52] Finished Work Unit:
[07:35:52] Leaving Run
[07:35:55] - Writing 320792 bytes of core data to disk...
[07:35:55] ... Done.
[07:35:55] - Shutting down core
[07:35:55]
[07:35:55] Folding@home Core Shutdown: FINISHED_UNIT
[07:35:59] CoreStatus = 64 (100)
[07:35:59] Sending work to server
[07:35:59] Project: 4615 (Run 20, Clone 149, Gen 53)
[07:35:59] - Read packet limit of 540015616... Set to 524286976.
[07:35:59] + Attempting to send results [April 4 07:35:59 UTC]
[07:36:05] + Results successfully sent
[07:36:05] Thank you for your contribution to Folding@Home.
[07:36:05] + Number of Units Completed: 74
[07:36:09] Project: 4605 (Run 11, Clone 102, Gen 43)
[07:36:09] - Read packet limit of 540015616... Set to 524286976.
[07:36:09] + Attempting to send results [April 4 07:36:09 UTC]
[07:36:11] + Results successfully sent
[07:36:11] Thank you for your contribution to Folding@Home.
[07:36:11] Project: 4605 (Run 11, Clone 102, Gen 43)
[07:36:11] - Read packet limit of 540015616... Set to 524286976.
[07:36:11] + Attempting to send results [April 4 07:36:11 UTC]
[07:36:12] + Results successfully sent
[07:36:12] Thank you for your contribution to Folding@Home.
[07:36:12] Project: 4614 (Run 22, Clone 191, Gen 18)
[07:36:12] - Read packet limit of 540015616... Set to 524286976.
[07:36:12] + Attempting to send results [April 4 07:36:12 UTC]
[07:36:18] + Results successfully sent
[07:36:18] Thank you for your contribution to Folding@Home.
[07:36:18] + Number of Units Completed: 75
[07:36:18] Project: 6314 (Run 392, Clone 19, Gen 13)
[07:36:18] - Read packet limit of 540015616... Set to 524286976.
[07:36:18] + Attempting to send results [April 4 07:36:18 UTC]
[07:36:20] - Couldn't send HTTP request to server
[07:36:20] + Could not connect to Work Server (results)
[07:36:20] (171.64.65.111:8080)
[07:36:20] + Retrying using alternative port
[07:36:21] - Couldn't send HTTP request to server
[07:36:21] + Could not connect to Work Server (results)
[07:36:21] (171.64.65.111:80)
[07:36:21] - Error: Could not transmit unit 07 (completed April 3) to work server.
[07:36:21] - Read packet limit of 540015616... Set to 524286976.
[07:36:21] + Attempting to send results [April 4 07:36:21 UTC]
[07:51:36] - Couldn't send HTTP request to server
[07:51:36] + Could not connect to Work Server (results)
[07:51:36] (171.67.108.17:8080)
[07:51:36] + Retrying using alternative port
[07:51:37] - Couldn't send HTTP request to server
[07:51:37] (Got status 503)
[07:51:37] + Could not connect to Work Server (results)
[07:51:37] (171.67.108.17:80)
[07:51:37] Could not transmit unit 07 to Collection server; keeping in queue.
[07:51:37] - Preparing to get new work unit...
[07:51:37] + Attempting to get work packet
[07:51:37] - Connecting to assignment server
[07:51:39] + No appropriate work server was available; will try again in a bit.
[07:51:39] + Couldn't get work instructions.
[07:51:39] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[07:51:50] + Attempting to get work packet
[07:51:50] - Connecting to assignment server
[07:51:51] + No appropriate work server was available; will try again in a bit.
[07:51:51] + Couldn't get work instructions.
[07:51:51] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[07:52:09] + Attempting to get work packet
[07:52:09] - Connecting to assignment server
[07:52:10] + No appropriate work server was available; will try again in a bit.
[07:52:10] + Couldn't get work instructions.
[07:52:10] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[07:52:36] + Attempting to get work packet
[07:52:36] - Connecting to assignment server
[07:52:37] + No appropriate work server was available; will try again in a bit.
[07:52:37] + Couldn't get work instructions.
[07:52:37] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[07:53:23] + Attempting to get work packet
[07:53:23] - Connecting to assignment server
[07:53:24] - Successful: assigned to (169.230.26.30).
[07:53:24] + News From Folding@Home: Welcome to Folding@Home
[07:53:24] Loaded queue successfully.
[07:53:25] Project: 6314 (Run 392, Clone 19, Gen 13)
[07:53:25] - Read packet limit of 540015616... Set to 524286976.
[07:53:25] + Attempting to send results [April 4 07:53:25 UTC]
[07:53:27] - Couldn't send HTTP request to server
[07:53:27] + Could not connect to Work Server (results)
[07:53:27] (171.64.65.111:8080)
[07:53:27] + Retrying using alternative port
[07:53:28] - Couldn't send HTTP request to server
[07:53:28] + Could not connect to Work Server (results)
[07:53:28] (171.64.65.111:80)
[07:53:28] - Error: Could not transmit unit 07 (completed April 3) to work server.
[07:53:28] - Read packet limit of 540015616... Set to 524286976.
[07:53:28] + Attempting to send results [April 4 07:53:28 UTC]
[07:57:00] Opening http://foldingforum.org/...
To try to have new work I restarted the client.
Code: Select all
07:53:28] + Attempting to send results [April 4 07:53:28 UTC]
[07:57:00] Opening http://foldingforum.org/...
[08:27:43] Opening http://foldingforum.org/...
Folding@Home Client Shutdown.
--- Opening Log file [April 4 09:00:54 UTC]
# Windows CPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\admin\AppData\Roaming\Folding@home-x86
[09:00:54] - Ask before connecting: No
[09:00:54] - User name: KroontjesPen (Team 92)
[09:00:54] - User ID: xxxxxxxxxxxxxxxxxxxxx
[09:00:54] - Machine ID: 1
[09:00:54]
[09:00:54] Loaded queue successfully.
[09:00:54] Initialization complete
[09:00:54]
[09:00:54] + Processing work unit
[09:00:54] Project: 6314 (Run 392, Clone 19, Gen 13)
[09:00:54] - Read packet limit of 540015616... Set to 524286976.
[09:00:54] + Attempting to send results [April 4 09:00:54 UTC]
[09:00:54] Core required: FahCore_82.exe
[09:00:54] Core found.
[09:00:54] Working on queue slot 04 [April 4 09:00:54 UTC]
[09:00:54] + Working ...
[09:00:54]
[09:00:54] *------------------------------*
[09:00:54] Folding@Home PMD Core
[09:00:54] Version 1.03 (September 7, 2005)
[09:00:54]
[09:00:54] Preparing to commence simulation
[09:00:54] - Looking at optimizations...
[09:00:54] - Created dyn
[09:00:54] - Files status OK
[09:00:54] - Expanded 12157 -> 76006 (decompressed 625.2 percent)
[09:00:54]
[09:00:54] Project: 4605 (Run 9, Clone 194, Gen 5)
[09:00:54]
[09:00:54] Assembly optimizations on if available.
[09:00:54] Entering M.D.
[09:00:56] - Couldn't send HTTP request to server
[09:00:56] + Could not connect to Work Server (results)
[09:00:56] (171.64.65.111:8080)
[09:00:56] + Retrying using alternative port
[09:00:57] - Couldn't send HTTP request to server
[09:00:57] + Could not connect to Work Server (results)
[09:00:57] (171.64.65.111:80)
[09:00:57] - Error: Could not transmit unit 07 (completed April 3) to work server.
[09:00:57] - Read packet limit of 540015616... Set to 524286976.
[09:00:57] + Attempting to send results [April 4 09:00:57 UTC]
[09:01:00] Protein: p4605_T0_proA-8_minout
[09:01:00]
[09:01:00] Completed 0 out of 2500000 steps (0%)
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Sun Apr 04, 2010 1:13 pm
by endrik
hisui wrote:Both server can't be accessed via browser.171.64.65.111:8080 is time out,171.67.108.17:8080 is an blank page
This was written two years ago. How come exactly the same problem occurs nowadays (just checked)? I can't believe the problem could not be identified since 2008, or even last two weeks since Vijay wrote they'll look into this. I would think that once it is identified it should be also eliminated, sad to see it is not the case ...
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Sun Apr 04, 2010 1:25 pm
by AgrFan
endrik wrote:hisui wrote:Both server can't be accessed via browser.171.64.65.111:8080 is time out,171.67.108.17:8080 is an blank page
How come exactly the same problem occurs nowadays (just checked)?
Because these servers are a single point of failure .. this has been going on for quite some time now .. remember we are dealing with a academic institution and not a corporate entity .. PG doesn't have the ability to provide a constant flow of work to all platforms .. with a DC effort this big, I still don't understand why there is no adequate backup strategy in place for when servers go offline.. rolling over to collection servers when work servers go down isn't cutting it.
Stick with SMP2 and GPU2 clients .. work is always available and the servers are reliable.
It's a shame but the little guy with older machines doesn't get serviced properly .. if you have a quad or video card you're fine .. if you have machines older than a few years, forget it.
Can't connect 171.67.108.17 status 503
Posted: Sun Apr 04, 2010 8:20 pm
by noprob
Code: Select all
[20:55:26] + Attempting to send results [April 4 20:55:26 UTC]
[20:55:26] - Reading file work/wuresults_08.dat from core
[20:55:26] (Read 4779799 bytes from disk)
[20:55:26] Connecting to http://171.67.108.17:8080/
[20:55:27] - Couldn't send HTTP request to server
[20:55:27] (Got status 503)
[20:55:27] + Could not connect to Work Server (results)
[20:55:27] (171.67.108.17:8080)
[20:55:27] + Retrying using alternative port
[20:55:27] Connecting to http://171.67.108.17:80/
[20:55:30] - Couldn't send HTTP request to server
[20:55:30] (Got status 503)
[20:55:30] + Could not connect to Work Server (results)
[20:55:30] (171.67.108.17:80)
[20:55:30] Could not transmit unit 08 to Collection server; keeping in queue.
[20:55:30] + Sent 0 of 1 completed units to the server
[20:55:30] - Failed to send all units to server
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Sun Apr 04, 2010 10:49 pm
by preet.to
I am on Fedora 12 and cannot use GPU or SMP clients any more. Still waiting on an update to the client. So I downgraded to the classic client. Now all my machines have WU to upload and nothing to download. Total standstill. Happy Easter to my machines!
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Mon Apr 05, 2010 12:13 am
by codysluder
AgrFan wrote:endrik wrote:hisui wrote:Both server can't be accessed via browser.171.64.65.111:8080 is time out,171.67.108.17:8080 is an blank page
How come exactly the same problem occurs nowadays (just checked)?
Because these servers are a single point of failure .. this has been going on for quite some time now .. remember we are dealing with a academic institution and not a corporate entity .. PG doesn't have the ability to provide a constant flow of work to all platforms .. with a DC effort this big, I still don't understand why there is no adequate backup strategy in place for when servers go offline.. rolling over to collection servers when work servers go down isn't cutting it.
The whole point of the Collection servers was to provide the exact backup strategy that you suggest. It worked reasonably well but the server code was old and poorly written so they contracted for a complete rewrite of the server code. Apparently there are compatabilty issues between the new server code and the code on the collection servers because it was just about the time that they started rolling out the new server code that a number of new problems arose with the collection servers.
Unfortunately with a large number of servers, which limted staff, and with a need to keep FAH running 24x7x365 it's not possible to upgrade all the servers simultaneously so until they finish the roll-out of the new code, I expect that they'll keep having problems.
Another choice would be to shut down all of FAH for a week or two and update everything simultaneously, but that wouldn't make any of us happy, and it has the potential of shutting down FAH even longer if problems are discovered after all of the servers are upgraded. Even in a business environment where there are often a number of people with the responsibility to upgrade PCs, they don't switch all PCs from XP to Vista on a single weekend.
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Mon Apr 05, 2010 12:25 am
by endrik
AgrFan wrote:rolling over to collection servers when work servers go down isn't cutting it
Especially when the collection server doesn't work either (171.67.108.17 is listed as collection sever 4).
BTW thanks for the explanation codysluder, interesting though that you write "It worked reasonably well but the server code was old and poorly written so they contracted for a complete rewrite of the server code". Apparently it wasn't THAT poorly written since it worked well, so why change it? Out of aesthetic reasons? There is a couple of sayings on that, like "the better is the enemy of the good" or "you don't switch your horses in the middle of a ford":)
preet.to wrote:I downgraded to the classic client. Now all my machines have WU to upload and nothing to download. Total standstill. Happy Easter to my machines!
Now that's interesting, I downloaded today a 2613 without much fuss. Maybe try to play with your config some (for example change " -advmethods").
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Mon Apr 05, 2010 2:24 am
by Scooby
Can anyone confirm if 171.64.65.111 is offline/rejecting for good? - it's been offline all w/e by the looks of it - will the results still be uploaded okay if it does come back?
Cheers.
Re: Can't connect 171.67.108.17 and 171.64.65.111
Posted: Mon Apr 05, 2010 4:34 am
by amuro.ID
Still down i guess. Here's mine
[04:40:16] - Couldn't send HTTP request to server
[04:40:16] + Could not connect to Work Server (results)
[04:40:16] (171.64.65.111:8080)
[04:40:16] - Error: Could not transmit unit 06 (completed April 3) to work server.
[04:40:16] - 19 failed uploads of this unit.
Perhaps this is why.
http://folding.typepad.com/news/2010/04 ... or-so.html