Cannot transmit to 171.64.65.111
Moderators: Site Moderators, FAHC Science Team
-
- 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
This one has been very troublesome. We will likely have to do something major to overhaul it. For now, it's up again, but I am expecting it will go down in a day or two and we will have to get it back up then.
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Re: 171.64.65.111 & 171.67.108.17 Not functional
Project 4104 (Run 66, Clone 4, Gen 14) was accepted by 171.64.65.111 last night.
Code: Select all
[14:45:18] Writing local files
[14:45:19] Completed 95000 out of 500000 steps (19 percent)
[14:51:52] - Autosending finished units... [February 7 14:51:52 UTC]
[14:51:52] Trying to send all finished work units
[14:51:52] Project: 4104 (Run 66, Clone 4, Gen 14)
[14:51:52] + Attempting to send results [February 7 14:51:52 UTC]
[14:51:52] - Reading file work/wuresults_05.dat from core
[14:51:52] (Read 3244423 bytes from disk)
[14:51:52] Connecting to http://171.64.65.111:8080/
[14:52:01] Posted data.
[14:52:01] Initial: 0000; - Uploaded at ~288 kB/s
[14:52:03] - Averaged speed for that direction ~233 kB/s
[14:52:03] + Results successfully sent
[14:52:03] Thank you for your contribution to Folding@Home.
-
- Posts: 59
- Joined: Mon Dec 03, 2007 2:28 am
- Hardware configuration: PC: AMD Sempron(tm) Processor 2800+, 1024 MB RAM, Microsoft Windows XP (Home Edition) SP3
Laptop: Mobile AMD Sempron(tm) Processor 3500+, 896 MB RAM, Microsoft Windows Vista (Home Premium) - Location: Blaine, MN
Re: 171.64.65.111 & 171.67.108.17 Not functional
It's not working for me though. (4100 (Run 109, Clone 15, Gen 13))
Been at it for 5 hours.
Code: Select all
[22:09:19] + Attempting to send results [February 10 22:09:19 UTC]
[22:09:21] - Couldn't send HTTP request to server
[22:09:21] + Could not connect to Work Server (results)
[22:09:21] (171.64.65.111:8080)
[22:09:21] + Retrying using alternative port
[22:09:23] - Couldn't send HTTP request to server
[22:09:23] + Could not connect to Work Server (results)
[22:09:23] (171.64.65.111:80)
[22:09:23] - Error: Could not transmit unit 01 (completed February 10) to work server.
[22:09:23] - Read packet limit of 540015616... Set to 524286976.
[22:09:23] + Attempting to send results [February 10 22:09:23 UTC]
[22:09:23] - Couldn't send HTTP request to server
[22:09:23] + Could not connect to Work Server (results)
[22:09:23] (171.67.108.17:8080)
[22:09:23] + Retrying using alternative port
[22:09:23] + Could not connect to Work Server (results)
[22:09:23] (171.67.108.17:80)
[22:09:23] Could not transmit unit 01 to Collection server; keeping in queue.
-
- 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
This is a known issue and we're working on it. As I mentioned in a previous thread, this one is more tricky.
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Re: 171.64.65.111 & 171.67.108.17 Not functional
I note this topic is a couple of weeks old, but I've been encountering the same issue. Today I removed the 5.04 Console exe and set up the 6.23 Console version, which immediately found new work and is happily working away. Still, even with the automatic switch to attempt sending to the alternative port, I get no play on 171.64.65.111 or 171.65.108.17.
Here's the relevant snip from my FAHlog:
I'm in a corporate environement, but had no firewall issues in the past; this is all a recent development.
IF the issue is at my end, is there a past topic addressing how to transfer completed results from my work folder, to the work folder on another machine for successful upload??
Here's the relevant snip from my FAHlog:
Code: Select all
[23:45:35] - Couldn't send HTTP request to server
[23:45:35] + Could not connect to Work Server (results)
[23:45:35] (171.64.65.111:80)
[23:45:35] + Retrying using alternative port
[23:45:56] - Couldn't send HTTP request to server
[23:45:56] + Could not connect to Work Server (results)
[23:45:56] (171.64.65.111:8080)
[23:45:56] - Error: Could not transmit unit 07 (completed February 9) to work server.
[23:45:56] + Attempting to send results [February 11 23:45:56 UTC]
[23:45:56] - Couldn't send HTTP request to server
[23:45:56] (Got status 503)
[23:45:56] + Could not connect to Work Server (results)
[23:45:56] (171.67.108.17:80)
[23:45:56] + Retrying using alternative port
[23:46:17] - Couldn't send HTTP request to server
[23:46:17] + Could not connect to Work Server (results)
[23:46:17] (171.67.108.17:8080)
[23:46:17] Could not transmit unit 07 to Collection server; keeping in queue.
IF the issue is at my end, is there a past topic addressing how to transfer completed results from my work folder, to the work folder on another machine for successful upload??
Re: 171.64.65.111 & 171.67.108.17 Not functional
ADDENDUM:
Addressing 171.67.108.17 from my browser returns "Cannot find server or DNS error" on ports 80 and 8080.
Addressing 171.64.65.111 from my browser returns "OK" on port 80, but "Cannot find server or DNS error" on port 8080.
tracert data shows a timeout to both servers that may be a contributing factor to these connection failures:
Addressing 171.67.108.17 from my browser returns "Cannot find server or DNS error" on ports 80 and 8080.
Addressing 171.64.65.111 from my browser returns "OK" on port 80, but "Cannot find server or DNS error" on port 8080.
tracert data shows a timeout to both servers that may be a contributing factor to these connection failures:
Code: Select all
16 21 ms 25 ms 24 ms bbra-rtr.Stanford.EDU [171.64.1.134]
17 * * * Request timed out.
18 16 ms 14 ms 14 ms vsp09v.Stanford.EDU [171.67.108.17]
16 147 ms 177 ms 223 ms bbra-rtr.Stanford.EDU [171.64.1.134]
17 * * * Request timed out.
18 163 ms 161 ms 158 ms vspg5v2.Stanford.EDU [171.64.65.111]
-
- Posts: 15
- Joined: Sat Jan 24, 2009 6:29 pm
- Location: California
Re: 171.64.65.111 & 171.67.108.17 Not functional (again)
I'm getting a backlog of WU's for this server once again. 02/01, 02/03, 02/06, 02/07. All of which fail to upload with the same messages as before when I started this thread. "Couldn't send HTTP request to server"
I've tried all the tricks once again, even tried to get those machines to send over a different internet connection than their dedicated line, but no luck. Tracert always get the same result at step 10, that being "10 * * * Request timed out." It's getting close to two weeks on these Wu's inability to go home. Can someone feed the mice on the wheel in that machine again?
I've tried all the tricks once again, even tried to get those machines to send over a different internet connection than their dedicated line, but no luck. Tracert always get the same result at step 10, that being "10 * * * Request timed out." It's getting close to two weeks on these Wu's inability to go home. Can someone feed the mice on the wheel in that machine again?
Re: 171.64.65.111 & 171.67.108.17 Not functional
Same here several WU waiting for days. They should monitor it more closely since we are doing the research for free! I mean why send it out if it can't come back seems stupid from a research point of view! Get with the program please----would you like the farms of system crunching for little green men instead!
-
- 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
I am sure they understand your concern. And I am sure they are aware of the situation and doing everything they can to fix the problem even if they don't post as such. For us, it might seem like a few wasted CPU cycles, but they are NOT wasted if the work units are uploaded after the server is fixed. No points or science is lost until those work units expire, and the server should be fixed long before then.
And if a few work units do eventually expire, it's more than just a few wasted CPU cycles to Stanford. Those researchers can't finish their degree programs and graduate if they don't finish the science they sent out. So for them, the stakes are much higher to get the servers working as best they can.
P.S. Welcome to the forum, step2000.
And if a few work units do eventually expire, it's more than just a few wasted CPU cycles to Stanford. Those researchers can't finish their degree programs and graduate if they don't finish the science they sent out. So for them, the stakes are much higher to get the servers working as best they can.
P.S. Welcome to the forum, step2000.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: 171.64.65.111 & 171.67.108.17 Not functional
Error 503 is not something that you can fix. It means a server is too busy to handle your request. That might be the server at hop 17, but it's not uncommon for the problem to be the actual work server, itself, at hop 18. Dr. Pande has mentioned the newly rewritten server code that's being tested in his news blog. When it's ready to be used, that will alleviate much of the server congestion that's producing most of the 503 errors.
Microsoft's "Cannot find server or DNS error" isn't a particularly helpful message. It's better to check http://fah-web.stanford.edu/serverstat.html
Both http://171.64.65.111 and http://171.64.65.111:8080 both give me "OK" right now in spite of a CPU LOAD of 2.41 and a NET LOAD of 71. At this moment, it should be able to handle your request without difficulty.
Both http://171.67.108.17 and http://171.67.108.17:8080 return nothing and it has a CPU LOAD of 3.16 and a NET LOAD of 249. This collection server seems to keep it's NETLOAD between 248 and 253 so it's constantly doing everything it can -- with somebody establishing a new connection within seconds of when somebody releases one. WE DO NEED THAT NEW SERVER CODE.
Microsoft's "Cannot find server or DNS error" isn't a particularly helpful message. It's better to check http://fah-web.stanford.edu/serverstat.html
Both http://171.64.65.111 and http://171.64.65.111:8080 both give me "OK" right now in spite of a CPU LOAD of 2.41 and a NET LOAD of 71. At this moment, it should be able to handle your request without difficulty.
Both http://171.67.108.17 and http://171.67.108.17:8080 return nothing and it has a CPU LOAD of 3.16 and a NET LOAD of 249. This collection server seems to keep it's NETLOAD between 248 and 253 so it's constantly doing everything it can -- with somebody establishing a new connection within seconds of when somebody releases one. WE DO NEED THAT NEW SERVER CODE.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 120
- Joined: Fri Jan 25, 2008 3:20 am
- Hardware configuration: Q6600 | P35-DQ6 | Crucial 2 x 1 GB ram | VisionTek 3870
GPU2 Version 6.20| CPU three 6.20 Clients
171.64.65.111 in Reject
171.64.65.111 in Reject
Down about 4 hours before restarting the client got new work.
Down about 4 hours before restarting the client got new work.
Re: 171.64.65.111 in Reject
I already have reported it. Port 80 is disabled, too.
My guess is that it will reset itself in about 4.5 hrs whether or not anybody responds promptly.
My guess is that it will reset itself in about 4.5 hrs whether or not anybody responds promptly.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
171.64.65.111
Edit my Mod: This post was previously part of a discussion on the subject: Re: 130.49.240.81 and 130.49.240.77 and it has been split into a separate topic.
So this problem has been going on for months. I do occasionally get some work returned but I loose more than I return. I reinstalled and have processed four more units. None of which will upload.
So this problem has been going on for months. I do occasionally get some work returned but I loose more than I return. I reinstalled and have processed four more units. None of which will upload.
Code: Select all
[14:27:24] Killing all core threads
Folding@Home Client Shutdown.
--- Opening Log file [August 8 14:28:16 UTC]
# Windows CPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: D:\Documents and Settings\jim\Application Data\Folding@home-x86
Arguments: -verbosity 9 -advmethods
[14:28:16] - Ask before connecting: No
[14:28:16] - User name: edsguy-lp (Team 42263)
[14:28:16] - User ID: 5514B7EE6EECB65D
[14:28:16] - Machine ID: 1
[14:28:16]
[14:28:16] Loaded queue successfully.
[14:28:16] Initialization complete
[14:28:17]
[14:28:17] + Processing work unit
[14:28:17] Core required: FahCore_78.exe
[14:28:17] - Autosending finished units... [August 8 14:28:17 UTC]
[14:28:17] Trying to send all finished work units
[14:28:17] Project: 5114 (Run 219, Clone 31, Gen 3)
[14:28:17] Core found.
[14:28:17] + Attempting to send results [August 8 14:28:17 UTC]
[14:28:17] - Reading file work/wuresults_01.dat from core
[14:28:17] (Read 2340807 bytes from disk)
[14:28:17] Connecting to http://171.67.108.12:8080/
[14:28:17] Working on queue slot 05 [August 8 14:28:17 UTC]
[14:28:17] + Working ...
[14:28:17] - Calling '.\FahCore_78.exe -dir work/ -suffix 05 -cpu 96 -checkpoint 15 -verbose -lifeline 5796 -version 623'
[14:28:18] - Couldn't send HTTP request to server
[14:28:18] + Could not connect to Work Server (results)
[14:28:18] (171.67.108.12:8080)
[14:28:18] + Retrying using alternative port
[14:28:18] Connecting to http://171.67.108.12:80/
[14:28:18] - Couldn't send HTTP request to server
[14:28:18] + Could not connect to Work Server (results)
[14:28:18] (171.67.108.12:80)
[14:28:18] - Error: Could not transmit unit 01 (completed August 1) to work server.
[14:28:18] - 39 failed uploads of this unit.
[14:28:18] + Attempting to send results [August 8 14:28:18 UTC]
[14:28:18] - Reading file work/wuresults_01.dat from core
[14:28:18] (Read 2340807 bytes from disk)
[14:28:18] Connecting to http://171.67.108.25:8080/
[14:28:18] - Couldn't send HTTP request to server
[14:28:18] + Could not connect to Work Server (results)
[14:28:18] (171.67.108.25:8080)
[14:28:18] + Retrying using alternative port
[14:28:18] Connecting to http://171.67.108.25:80/
[14:28:18] - Couldn't send HTTP request to server
[14:28:18] + Could not connect to Work Server (results)
[14:28:18] (171.67.108.25:80)
[14:28:18] Could not transmit unit 01 to Collection server; keeping in queue.
[14:28:18] Project: 6304 (Run 297, Clone 2, Gen 16)
[14:28:18] + Attempting to send results [August 8 14:28:18 UTC]
[14:28:18] - Reading file work/wuresults_02.dat from core
[14:28:18] (Read 4810070 bytes from disk)
[14:28:18] Connecting to http://171.64.65.111:8080/
[14:28:18]
[14:28:18] *------------------------------*
[14:28:18] Folding@Home Gromacs Core
[14:28:18] Version 1.90 (March 8, 2006)
[14:28:18]
[14:28:18] Preparing to commence simulation
[14:28:18] - Looking at optimizations...
[14:28:18] - Files status OK
[14:28:18] - Couldn't send HTTP request to server
[14:28:18] + Could not connect to Work Server (results)
[14:28:18] (171.64.65.111:8080)
[14:28:18] + Retrying using alternative port
[14:28:18] Connecting to http://171.64.65.111:80/
[14:28:18] - Couldn't send HTTP request to server
[14:28:18] + Could not connect to Work Server (results)
[14:28:18] (171.64.65.111:80)
[14:28:18] - Error: Could not transmit unit 02 (completed August 3) to work server.
[14:28:18] - 28 failed uploads of this unit.
[14:28:18] + Attempting to send results [August 8 14:28:18 UTC]
[14:28:18] - Reading file work/wuresults_02.dat from core
[14:28:18] (Read 4810070 bytes from disk)
[14:28:18] Connecting to http://171.67.108.17:8080/
[14:28:18] - Couldn't send HTTP request to server
[14:28:18] + Could not connect to Work Server (results)
[14:28:18] (171.67.108.17:8080)
[14:28:18] + Retrying using alternative port
[14:28:18] Connecting to http://171.67.108.17:80/
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.67.108.17:80)
[14:28:19] Could not transmit unit 02 to Collection server; keeping in queue.
[14:28:19] Project: 6301 (Run 585, Clone 3, Gen 18)
[14:28:19] + Attempting to send results [August 8 14:28:19 UTC]
[14:28:19] - Reading file work/wuresults_03.dat from core
[14:28:19] (Read 4741307 bytes from disk)
[14:28:19] Connecting to http://171.64.65.111:8080/
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.64.65.111:8080)
[14:28:19] + Retrying using alternative port
[14:28:19] Connecting to http://171.64.65.111:80/
[14:28:19] - Expanded 454169 -> 2247321 (decompressed 494.8 percent)
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.64.65.111:80)
[14:28:19] - Error: Could not transmit unit 03 (completed August 6) to work server.
[14:28:19] - 17 failed uploads of this unit.
[14:28:19] + Attempting to send results [August 8 14:28:19 UTC]
[14:28:19] - Reading file work/wuresults_03.dat from core
[14:28:19] (Read 4741307 bytes from disk)
[14:28:19] Connecting to http://171.67.108.17:8080/
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.67.108.17:8080)
[14:28:19] + Retrying using alternative port
[14:28:19] Connecting to http://171.67.108.17:80/
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.67.108.17:80)
[14:28:19] Could not transmit unit 03 to Collection server; keeping in queue.
[14:28:19] Project: 6301 (Run 81, Clone 1, Gen 15)
[14:28:19] + Attempting to send results [August 8 14:28:19 UTC]
[14:28:19] - Reading file work/wuresults_04.dat from core
[14:28:19] (Read 4729622 bytes from disk)
[14:28:19] Connecting to http://171.64.65.111:8080/
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.64.65.111:8080)
[14:28:19] + Retrying using alternative port
[14:28:19] Connecting to http://171.64.65.111:80/
[14:28:19]
[14:28:19] Project: 6304 (Run 15, Clone 5, Gen 9)
[14:28:19]
[14:28:19] Assembly optimizations on if available.
[14:28:19] Entering M.D.
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.64.65.111:80)
[14:28:19] - Error: Could not transmit unit 04 (completed August 8) to work server.
[14:28:19] - 7 failed uploads of this unit.
[14:28:19] + Attempting to send results [August 8 14:28:19 UTC]
[14:28:19] - Reading file work/wuresults_04.dat from core
[14:28:19] (Read 4729622 bytes from disk)
[14:28:19] Connecting to http://171.67.108.17:8080/
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.67.108.17:8080)
[14:28:19] + Retrying using alternative port
[14:28:19] Connecting to http://171.67.108.17:80/
[14:28:19] - Couldn't send HTTP request to server
[14:28:19] + Could not connect to Work Server (results)
[14:28:19] (171.67.108.17:80)
[14:28:19] Could not transmit unit 04 to Collection server; keeping in queue.
[14:28:19] + Sent 0 of 4 completed units to the server
[14:28:19] - Autosend completed
[14:28:39] (Starting from checkpoint)
[14:28:39] Protein: p6304_sh3_with_TYR_frags
[14:28:39]
[14:28:39] Writing local files
[14:28:40] Completed 107997 out of 500000 steps (22%)
[14:28:40] Extra SSE boost OK.
[14:41:02] Writing local files
[14:41:03] Completed 110000 out of 500000 steps (22%)
[14:48:49] ***** Got a SIGTERM signal (2)
[14:48:49] Killing all core threads
Folding@Home Client Shutdown.
--- Opening Log file [August 8 14:49:16 UTC]
# Windows CPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: D:\Documents and Settings\jim\Application Data\Folding@home-x86
Arguments: -verbosity 9 -advmethods
[14:49:16] - Ask before connecting: No
[14:49:16] - User name: edsguy-lp (Team 42263)
[14:49:16] - User ID: 5514B7EE6EECB65D
[14:49:16] - Machine ID: 1
[14:49:16]
[14:49:16] Loaded queue successfully.
[14:49:16] Initialization complete
[14:49:17]
[14:49:17] + Processing work unit
[14:49:17] Core required: FahCore_78.exe
[14:49:17] - Autosending finished units... [August 8 14:49:17 UTC]
[14:49:17] Trying to send all finished work units
[14:49:17] Project: 5114 (Run 219, Clone 31, Gen 3)
[14:49:17] Core found.
[14:49:17] + Attempting to send results [August 8 14:49:17 UTC]
[14:49:17] - Reading file work/wuresults_01.dat from core
[14:49:17] (Read 2340807 bytes from disk)
[14:49:17] Connecting to http://171.67.108.12:8080/
[14:49:17] Working on queue slot 05 [August 8 14:49:17 UTC]
[14:49:17] + Working ...
[14:49:17] - Calling '.\FahCore_78.exe -dir work/ -suffix 05 -cpu 96 -checkpoint 15 -verbose -lifeline 5724 -version 623'
[14:49:18] - Couldn't send HTTP request to server
[14:49:18] + Could not connect to Work Server (results)
[14:49:18] (171.67.108.12:8080)
[14:49:18] + Retrying using alternative port
[14:49:18] Connecting to http://171.67.108.12:80/
[14:49:18] - Couldn't send HTTP request to server
[14:49:18] + Could not connect to Work Server (results)
[14:49:18] (171.67.108.12:80)
[14:49:18] - Error: Could not transmit unit 01 (completed August 1) to work server.
[14:49:18] - 40 failed uploads of this unit.
[14:49:18] + Attempting to send results [August 8 14:49:18 UTC]
[14:49:18] - Reading file work/wuresults_01.dat from core
[14:49:18] (Read 2340807 bytes from disk)
[14:49:18] Connecting to http://171.67.108.25:8080/
[14:49:18] - Couldn't send HTTP request to server
[14:49:18] + Could not connect to Work Server (results)
[14:49:18] (171.67.108.25:8080)
[14:49:18] + Retrying using alternative port
[14:49:18] Connecting to http://171.67.108.25:80/
[14:49:18]
[14:49:18] *------------------------------*
[14:49:18] Folding@Home Gromacs Core
[14:49:18] Version 1.90 (March 8, 2006)
[14:49:18]
[14:49:18] Preparing to commence simulation
[14:49:18] - Looking at optimizations...
[14:49:18] - Files status OK
[14:49:18] - Couldn't send HTTP request to server
[14:49:18] + Could not connect to Work Server (results)
[14:49:18] (171.67.108.25:80)
[14:49:18] Could not transmit unit 01 to Collection server; keeping in queue.
[14:49:18] Project: 6304 (Run 297, Clone 2, Gen 16)
[14:49:18] + Attempting to send results [August 8 14:49:18 UTC]
[14:49:18] - Reading file work/wuresults_02.dat from core
[14:49:18] (Read 4810070 bytes from disk)
[14:49:18] Connecting to http://171.64.65.111:8080/
[14:49:19] - Expanded 454169 -> 2247321 (decompressed 494.8 percent)
[14:49:19]
[14:49:19] Project: 6304 (Run 15, Clone 5, Gen 9)
[14:49:19]
[14:49:19] Assembly optimizations on if available.
[14:49:19] Entering M.D.
[14:49:21] - Couldn't send HTTP request to server
[14:49:21] + Could not connect to Work Server (results)
[14:49:21] (171.64.65.111:8080)
[14:49:21] + Retrying using alternative port
[14:49:21] Connecting to http://171.64.65.111:80/
[14:49:21] - Couldn't send HTTP request to server
[14:49:21] + Could not connect to Work Server (results)
[14:49:21] (171.64.65.111:80)
[14:49:21] - Error: Could not transmit unit 02 (completed August 3) to work server.
[14:49:21] - 29 failed uploads of this unit.
[14:49:21] + Attempting to send results [August 8 14:49:21 UTC]
[14:49:21] - Reading file work/wuresults_02.dat from core
[14:49:21] (Read 4810070 bytes from disk)
[14:49:21] Connecting to http://171.67.108.17:8080/
[14:49:21] - Couldn't send HTTP request to server
[14:49:21] + Could not connect to Work Server (results)
[14:49:21] (171.67.108.17:8080)
[14:49:21] + Retrying using alternative port
[14:49:21] Connecting to http://171.67.108.17:80/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.67.108.17:80)
[14:49:22] Could not transmit unit 02 to Collection server; keeping in queue.
[14:49:22] Project: 6301 (Run 585, Clone 3, Gen 18)
[14:49:22] + Attempting to send results [August 8 14:49:22 UTC]
[14:49:22] - Reading file work/wuresults_03.dat from core
[14:49:22] (Read 4741307 bytes from disk)
[14:49:22] Connecting to http://171.64.65.111:8080/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.64.65.111:8080)
[14:49:22] + Retrying using alternative port
[14:49:22] Connecting to http://171.64.65.111:80/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.64.65.111:80)
[14:49:22] - Error: Could not transmit unit 03 (completed August 6) to work server.
[14:49:22] - 18 failed uploads of this unit.
[14:49:22] + Attempting to send results [August 8 14:49:22 UTC]
[14:49:22] - Reading file work/wuresults_03.dat from core
[14:49:22] (Read 4741307 bytes from disk)
[14:49:22] Connecting to http://171.67.108.17:8080/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.67.108.17:8080)
[14:49:22] + Retrying using alternative port
[14:49:22] Connecting to http://171.67.108.17:80/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.67.108.17:80)
[14:49:22] Could not transmit unit 03 to Collection server; keeping in queue.
[14:49:22] Project: 6301 (Run 81, Clone 1, Gen 15)
[14:49:22] + Attempting to send results [August 8 14:49:22 UTC]
[14:49:22] - Reading file work/wuresults_04.dat from core
[14:49:22] (Read 4729622 bytes from disk)
[14:49:22] Connecting to http://171.64.65.111:8080/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.64.65.111:8080)
[14:49:22] + Retrying using alternative port
[14:49:22] Connecting to http://171.64.65.111:80/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.64.65.111:80)
[14:49:22] - Error: Could not transmit unit 04 (completed August 8) to work server.
[14:49:22] - 8 failed uploads of this unit.
[14:49:22] + Attempting to send results [August 8 14:49:22 UTC]
[14:49:22] - Reading file work/wuresults_04.dat from core
[14:49:22] (Read 4729622 bytes from disk)
[14:49:22] Connecting to http://171.67.108.17:8080/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.67.108.17:8080)
[14:49:22] + Retrying using alternative port
[14:49:22] Connecting to http://171.67.108.17:80/
[14:49:22] - Couldn't send HTTP request to server
[14:49:22] + Could not connect to Work Server (results)
[14:49:22] (171.67.108.17:80)
[14:49:22] Could not transmit unit 04 to Collection server; keeping in queue.
[14:49:22] + Sent 0 of 4 completed units to the server
[14:49:22] - Autosend completed
[14:49:39] (Starting from checkpoint)
[14:49:39] Protein: p6304_sh3_with_TYR_frags
[14:49:39]
[14:49:39] Writing local files
[14:49:39] Completed 110000 out of 500000 steps (22%)
[14:49:39] Extra SSE boost OK.
Re: 130.49.240.81 and 130.49.240.77
I really do not understand why people waste their time uninstalling/reinstalling the FAH software when they're having a problem with a specific server. Have you read Do this first which is locked at the top of this forum?dsmguy wrote:So this problem has been going on for months. I do occasionally get some work returned but I loose more than I return. I reinstalled and have processed four more units. None of which will upload.
I suppose that you realize that the log that you've posted won't get any serious attention when you post it here. This is a discussion of problems with servers 130.49.240.81 and 130.49.240.77 and neither of those servers have anything to do with the information in your log so you really can't say the problem has been going on for "months".
You're having troubles with four different servers and they're discussed elsewhere:
WU 01
http://171.67.108.12
http://171.67.108.25
Those servers are both accepting uploads at the present time. The Work Server isn't working very hard although the Collection Server is pretty busy. I see no other reports of people having troubles with 171.67.108.12 so there's a good chance the problem is your security software.
WUs 02, 03, 04
http://171.64.65.111
http://171.67.108.17
Both of those servers seem to be under quite a bit of load right now. There was a problem reported with 171.64.65.111 last week, but it has been resolved. See viewtopic.php?t=10769
Have you tried temporarily disabling your security software to confirm it isn't blocking a connection to these servers? Can you open those URLs in your browser? When were those WUs downloaded?
I'm happy to move your post to one of the discussions of those servers -- and to contact the people responsible for them if appropriate, but I'll need to do a little more research first.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 171.64.65.111
Sorry if I'm posting in the wrong location. I had started the post under the client. I believe you moved it to the server side.
I have tried sleeping my virus checker and disabling my firewall. No help. I use CA Internet Security Suite. I can see the outbound traffic allowed in the firewall log. I see no blocked traffic.
This morning I'm getting "OK" back from all the servers except http://171.67.108.17 This one just comes back blank. No broken connection or anything.
You asked when the WUs were downloaded. If the dates from the files logfile_0x.txt give that info. Then they are as follows:
01.txt 8/1
02.txt 8/3
03.txt 8/5
04.txt 8/7
Stats are showing that I uploaded 10 completed units. At the time I reinstalled I had 5 units that were waiting to upload. They were getting old enough that I think they were dropping off of the queue. I couldn't see waiting for more wasted work, so I reinstalled hoping for better results.
Any help you can give would be greatly appreciated.
I have tried sleeping my virus checker and disabling my firewall. No help. I use CA Internet Security Suite. I can see the outbound traffic allowed in the firewall log. I see no blocked traffic.
This morning I'm getting "OK" back from all the servers except http://171.67.108.17 This one just comes back blank. No broken connection or anything.
You asked when the WUs were downloaded. If the dates from the files logfile_0x.txt give that info. Then they are as follows:
01.txt 8/1
02.txt 8/3
03.txt 8/5
04.txt 8/7
Stats are showing that I uploaded 10 completed units. At the time I reinstalled I had 5 units that were waiting to upload. They were getting old enough that I think they were dropping off of the queue. I couldn't see waiting for more wasted work, so I reinstalled hoping for better results.
Any help you can give would be greatly appreciated.