Thanks, next time I'll be aware of thisanko1 wrote:PS - It's also helpful when you're posting log to use the code button to condense it (highlight the log and click "code", or type "code" at start in brackets and "[/code]" at end, w/o the quote marks.).
Cannot transmit to 171.64.65.111
Moderators: Site Moderators, FAHC Science Team
Re: 503 error on 171.67.108.17 and 171.64.65.111
--
I'm counting for science.
Points just make me sick.
I'm counting for science.
Points just make me sick.
-
- Posts: 4
- Joined: Mon Dec 22, 2008 6:19 pm
Re: Server Status Page - Which server for which client ?
I am getting the same thing on the following servers171.64.65.111, 171.67.108.17, the oldest WU being completed on Dec 22nd. There are a total of 6 WU waiting to be sent. It is not going through a proxy and it was working before. Any ideas? (log below)
Edit by Mod: Added code tags.
-b
Code: Select all
[03:01:23] + Attempting to send results
[03:01:54] Couldn't send HTTP request to server (wininet)
[03:01:54] + Could not connect to Work Server (results)
[03:01:54] (171.64.65.111:80)
[03:01:54] - Error: Could not transmit unit 02 (completed December 30) to work server.
[03:01:54] + Attempting to send results
[03:01:54] Couldn't send HTTP request to server (wininet)
[03:01:54] + Could not connect to Work Server (results)
[03:01:54] (171.67.108.17:80)
[03:01:54] Could not transmit unit 02 to Collection server; keeping in queue.
[03:01:54] + Attempting to send results
[03:02:25] Couldn't send HTTP request to server (wininet)
[03:02:25] + Could not connect to Work Server (results)
[03:02:25] (171.64.65.111:80)
[03:02:25] - Error: Could not transmit unit 03 (completed December 22) to work server.
[03:02:25] + Attempting to send results
[03:02:25] Couldn't send HTTP request to server (wininet)
[03:02:25] + Could not connect to Work Server (results)
[03:02:25] (171.67.108.17:80)
[03:02:25] Could not transmit unit 03 to Collection server; keeping in queue.
[03:02:25] + Attempting to send results
[03:02:56] Couldn't send HTTP request to server (wininet)
[03:02:56] + Could not connect to Work Server (results)
[03:02:56] (171.64.65.111:80)
[03:02:56] - Error: Could not transmit unit 09 (completed December 26) to work server.
[03:02:56] + Attempting to send results
[03:02:57] Couldn't send HTTP request to server (wininet)
[03:02:57] + Could not connect to Work Server (results)
[03:02:57] (171.67.108.17:80)
[03:02:57] Could not transmit unit 09 to Collection server; keeping in queue.
-b
Re: 503 error on 171.67.108.17 and 171.64.65.111
Welcome to the fold, CaregiverJimAL
I see three WUs which have not uploaded, not 6. Each WU tries to upload to a primary server (171.64.65.111, in this case) and if that fails, it then goes to a collection server (171.67.108.17, in this case). If both attempts fail, the upload is retried later.
In this case, both servers are quite busy. This is a known problem which is being addressed by a total rewrite of the server code. The campus is currently closed for the holidays and school resumes next week. Although there are some folks monitoring the servers, staffing is down and the Pande Group did not want to roll this new code out to the servers before the holidays. It seems better to wait until all of the staff are available, in case some unexpected issues are encountered which need immediate attention.
What version of the FAH client are you running? In addition to the possibility that you're encountering busy servers each time your client tries to upload, there are some other issues that have been fixed in v6.23.
I see three WUs which have not uploaded, not 6. Each WU tries to upload to a primary server (171.64.65.111, in this case) and if that fails, it then goes to a collection server (171.67.108.17, in this case). If both attempts fail, the upload is retried later.
In this case, both servers are quite busy. This is a known problem which is being addressed by a total rewrite of the server code. The campus is currently closed for the holidays and school resumes next week. Although there are some folks monitoring the servers, staffing is down and the Pande Group did not want to roll this new code out to the servers before the holidays. It seems better to wait until all of the staff are available, in case some unexpected issues are encountered which need immediate attention.
What version of the FAH client are you running? In addition to the possibility that you're encountering busy servers each time your client tries to upload, there are some other issues that have been fixed in v6.23.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 4
- Joined: Mon Dec 22, 2008 6:19 pm
Re: 503 error on 171.67.108.17 and 171.64.65.111
Sorry, you are right, there are only three. I am using 5.04 Beta, I guess it is time to upgrade. I thought it was odd that there are results waiting to upload that have been completed on 22-DEC-08, seems like that it would have gotten through at least once since then. I will be patient and wait and see. Can I upgrade while I have WU waiting to be sent?
Thanks for your help!
Thanks for your help!
-
- Posts: 357
- Joined: Mon Dec 03, 2007 4:36 pm
- Hardware configuration: Q9450 OC @ 3.2GHz (Win7 Home Premium) - SMP2
E7500 OC @ 3.66GHz (Windows Home Server) - SMP2
i5-3750k @ 3.8GHz (Win7 Pro) - SMP2 - Location: University of Birmingham, UK
Re: 503 error on 171.67.108.17 and 171.64.65.111
You can upgrade while you have results waiting. Just stop the client, drop in the new version, and start it again. However if you have the client installed as a service you will need to uninstall the service created by v5.04 and create a new service using 6.23, as there have been some significant changes to the service monitoring code.
Folding whatever I'm sent since March 2006 Beta testing since October 2006. www.FAH-Addict.net Administrator since August 2009.
-
- Posts: 4
- Joined: Mon Dec 22, 2008 6:19 pm
Re: 503 error on 171.67.108.17 and 171.64.65.111
All is good. I upgraded and they all got uploaded. Had to copy the subdirectories (/work) since it is a different directory structure with the new version. Life is good at folding again! Thanks for your help!
-
- Posts: 15
- Joined: Sat Jan 24, 2009 6:29 pm
- Location: California
Cannot transmit to 171.64.65.111
FAH has not been able to send completed work back to the server since Friday night. Entering those IP #'s manually into my browser allows me to connect with no problem, so there is not an issue I can find on my end.
Any ideas?
[13:31:43] + Attempting to send results [January 24 13:31:43 UTC]
[13:31:51] - Couldn't send HTTP request to server
[13:31:51] + Could not connect to Work Server (results)
[13:31:51] (171.64.65.111:8080)
[13:31:51] + Retrying using alternative port
[13:31:58] - Couldn't send HTTP request to server
[13:31:58] + Could not connect to Work Server (results)
[13:31:58] (171.64.65.111:80)
[13:31:58] - Error: Could not transmit unit 08 (completed January 24) to work server.
[13:31:58] - Read packet limit of 540015616... Set to 524286976.
[13:31:58] + Attempting to send results [January 24 13:31:58 UTC]
[13:32:06] - Couldn't send HTTP request to server
[13:32:06] + Could not connect to Work Server (results)
[13:32:06] (171.67.108.17:8080)
[13:32:06] + Retrying using alternative port
[13:32:13] - Couldn't send HTTP request to server
[13:32:13] + Could not connect to Work Server (results)
[13:32:13] (171.67.108.17:80)
Any ideas?
[13:31:43] + Attempting to send results [January 24 13:31:43 UTC]
[13:31:51] - Couldn't send HTTP request to server
[13:31:51] + Could not connect to Work Server (results)
[13:31:51] (171.64.65.111:8080)
[13:31:51] + Retrying using alternative port
[13:31:58] - Couldn't send HTTP request to server
[13:31:58] + Could not connect to Work Server (results)
[13:31:58] (171.64.65.111:80)
[13:31:58] - Error: Could not transmit unit 08 (completed January 24) to work server.
[13:31:58] - Read packet limit of 540015616... Set to 524286976.
[13:31:58] + Attempting to send results [January 24 13:31:58 UTC]
[13:32:06] - Couldn't send HTTP request to server
[13:32:06] + Could not connect to Work Server (results)
[13:32:06] (171.67.108.17:8080)
[13:32:06] + Retrying using alternative port
[13:32:13] - Couldn't send HTTP request to server
[13:32:13] + Could not connect to Work Server (results)
[13:32:13] (171.67.108.17:80)
-
- Posts: 15
- Joined: Sat Jan 24, 2009 6:29 pm
- Location: California
Re: 171.64.65.111 & 171.67.108.17 Not functional
It has tried two additional times now to connect and send, but has failed both times. But as I stated before, if I enter the IP #'s into the browser, I get "ok" when the browser connects.
Re: 171.64.65.111 & 171.67.108.17 Not functional
What does this mean?
"- Server does not have record of this unit. Will try again later."
"- Server does not have record of this unit. Will try again later."
Code: Select all
[21:28:07] + Attempting to send results [January 25 21:28:07 UTC]
[21:28:07] - Reading file work/wuresults_09.dat from core
[21:28:07] (Read 385391 bytes from disk)
[21:28:07] Connecting to http://171.67.108.17:8080/
[21:28:20] Posted data.
[21:28:21] Initial: 0000; - Uploaded at ~26 kB/s
[21:28:21] - Averaged speed for that direction ~46 kB/s
[21:28:21] - Server does not have record of this unit. Will try again later.
[21:28:21] Could not transmit unit 09 to Collection server; keeping in queue.
[21:28:21] + Sent 0 of 1 completed units to the server
[21:28:51] Trying to send all finished work units
[21:28:51] Project: 2527 (Run 87, Clone 47, Gen 20)
Re: 171.64.65.111 & 171.67.108.17 Not functional
That usually means the server has stopped/crashed whatever before the details of the proteins have been sent to the collection server, hence it doesn't have a record of the unit.
ie it looks like it was an unplanned outage....
Teddy
ie it looks like it was an unplanned outage....
Teddy
Re: 171.64.65.111 & 171.67.108.17 Not functional
Ok. Thanks. I guess, I will try sending tomorrow. I need to shut this machine down for maintenance/upgrade.
Teddy wrote:That usually means the server has stopped/crashed whatever before the details of the proteins have been sent to the collection server, hence it doesn't have a record of the unit.
ie it looks like it was an unplanned outage....
Teddy
Re: 171.64.65.111 & 171.67.108.17 Not functional
Any mods reading this thread?
-
- Posts: 15
- Joined: Sat Jan 24, 2009 6:29 pm
- Location: California
Re: 171.64.65.111 & 171.67.108.17 Not functional
Still no results. Both IP's now reporting error 503 when attempting to upload. 13 failed attempts to upload.
[18:13:30] - Couldn't send HTTP request to server
[18:13:30] (Got status 503)
[18:13:30] - Couldn't send HTTP request to server
[18:13:30] (Got status 503)
-
- Site Moderator
- Posts: 6359
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: 171.64.65.111 & 171.67.108.17 Not functional
"- Server does not have record of this unit. Will try again later." is an error message issued by Collection Servers : http://fahwiki.net/index.php/Common_Err ... _this_unit
Status 503 is a standard HTTP error that means the server is to busy to handle your request.
171.64.65.111 has 143 simultaneous connection at the time I write this message, it's rather high.
Status 503 is a standard HTTP error that means the server is to busy to handle your request.
171.64.65.111 has 143 simultaneous connection at the time I write this message, it's rather high.
Re: 171.64.65.111 & 171.67.108.17 Not functional
Can any1 at F@H team look in to this server and see if it needs to be rebooted?