http://171.64.65.56:8080/ 503 status

[owbert]

ok something is happening with my f@h and it is becoming annoying. for the past 3 days on my computer ive not been hitting my ppd avg. barely 1WU in 24hours.

i am running 3 F@H (one client, one console, and one gpu2). they have been working final to my knowledge the past few months until recently.

skimming through the console i see that i am getting "Got status 503" in trying to return the finished work load. oddly enough it is able to DL a new workload when it has not finishied uploading the previous one. it states that it could not transmit unit 05 to collection server and it is keeping it in queue .

what could be the problem with uploading? does this mean i have 4 other units in queue waiting to be uploaded? will it eventually upload it at all? is there any commands to force it to try again?

it is one thing to not get points but another to have 3 processors working for the past few days and none of the work to be returned ... feels deflating.

is it my internet connection? ive havent changed anything. i do use opendns though.


p/s.: idk if this helps but the memory usage for all three clients have blown up to 200k per each f@H within the task manager which is something ive never seen the f@h taking up so much. and their folders in c:/ drive is a combined 80mbs of hard drive space now o_0

[Ultra Nexus]

Getting 503 errors myself too.

By checking the server status page I see server 171.64.65.56 is taking high cpu usage... can this be the cause?

[18:24:20] - Ask before connecting: No
[18:24:20] - Proxy: 192.168.50.200:8080
[18:24:20] - User name: _-_ThaNexus_-_ (Team 93)
[18:24:20] - User ID: 698E48C82A2BA81F
[18:24:20] - Machine ID: 1
[18:24:20]
[18:24:20] Loaded queue successfully.
[18:24:20] - Preparing to get new work unit...
[18:24:20] + Attempting to get work packet
[18:24:20] - Will indicate memory of 1004 MB
[18:24:20] - Connecting to assignment server
[18:24:20] Connecting to http://assign.stanford.edu:8080/
[18:24:20] - Autosending finished units... [February 10 18:24:20 UTC]
[18:24:20] Trying to send all finished work units
[18:24:20] + No unsent completed units remaining.
[18:24:20] - Autosend completed
[18:24:24] Posted data.
[18:24:24] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[18:24:24] + News From Folding@Home: Welcome to Folding@Home
[18:24:24] Loaded queue successfully.
[18:24:24] Connecting to http://171.64.65.56:8080/
[18:24:24] - Couldn't send HTTP request to server
[18:24:24] (Got status 503)
[18:24:24] + Could not connect to Work Server
[18:24:24] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[18:24:42] + Attempting to get work packet
[18:24:42] - Will indicate memory of 1004 MB
[18:24:42] - Connecting to assignment server
[18:24:42] Connecting to http://assign.stanford.edu:8080/
[18:24:46] Posted data.
[18:24:46] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[18:24:46] + News From Folding@Home: Welcome to Folding@Home
[18:24:46] Loaded queue successfully.
[18:24:46] Connecting to http://171.64.65.56:8080/
[18:24:46] - Couldn't send HTTP request to server
[18:24:46] (Got status 503)
[18:24:46] + Could not connect to Work Server
[18:24:46] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[18:25:09] + Attempting to get work packet
[18:25:09] - Will indicate memory of 1004 MB
[18:25:09] - Connecting to assignment server
[18:25:09] Connecting to http://assign.stanford.edu:8080/
[18:25:10] Posted data.
[18:25:10] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[18:25:10] + News From Folding@Home: Welcome to Folding@Home
[18:25:10] Loaded queue successfully.
[18:25:10] Connecting to http://171.64.65.56:8080/
[18:25:11] - Couldn't send HTTP request to server
[18:25:11] (Got status 503)
[18:25:11] + Could not connect to Work Server
[18:25:11] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.

[toTOW]

Server must be overloaded with all the requests from the clients that are now able to reach the Assignment Server ...

[slugbug]

http://171.64.65.56:8080/ seems to be down and is reporting a 503 status.

Code: Select all

[20:28:44] Finished Work Unit:
[20:28:44] - Reading up to 1873368 from "work/wudata_05.arc": Read 1873368
[20:28:44] - Reading up to 879404 from "work/wudata_05.xtc": Read 879404
[20:28:44] goefile size: 0
[20:28:44] logfile size: 56394
[20:28:44] Leaving Run
[20:28:48] - Writing 2844542 bytes of core data to disk...
[20:28:48]   ... Done.
[20:28:48] - Shutting down core
[20:28:48] 
[20:28:48] Folding@home Core Shutdown: FINISHED_UNIT
[20:28:53] CoreStatus = 64 (100)
[20:28:53] Unit 5 finished with 68 percent of time to deadline remaining.
[20:28:53] Updated performance fraction: 0.735851
[20:28:53] Sending work to server


[20:28:53] + Attempting to send results
[20:28:53] - Reading file work/wuresults_05.dat from core
[20:28:53]   (Read 2844542 bytes from disk)
[20:28:53] Connecting to http://171.64.65.64:8080/
[20:29:20] Posted data.
[20:29:20] Initial: 0000; - Uploaded at ~99 kB/s
[20:29:21] - Averaged speed for that direction ~86 kB/s
[20:29:21] + Results successfully sent
[20:29:21] Thank you for your contribution to Folding@Home.
[20:29:21] + Number of Units Completed: 25

[20:33:26] - Warning: Could not delete all work unit files (5): Core returned invalid code
[20:33:26] Trying to send all finished work units
[20:33:26] + No unsent completed units remaining.
[20:33:26] - Preparing to get new work unit...
[20:33:26] + Attempting to get work packet
[20:33:26] - Will indicate memory of 500 MB
[20:33:26] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 8
[20:33:26] - Connecting to assignment server
[20:33:26] Connecting to http://assign.stanford.edu:8080/
[20:33:26] Posted data.
[20:33:26] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:33:26] + News From Folding@Home: Welcome to Folding@Home
[20:33:26] Loaded queue successfully.
[20:33:26] Connecting to http://171.64.65.56:8080/
[20:33:26] - Couldn't send HTTP request to server
[20:33:26]   (Got status 503)
[20:33:26] + Could not connect to Work Server
[20:33:26] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[20:33:41] + Attempting to get work packet
[20:33:41] - Will indicate memory of 500 MB
[20:33:41] - Connecting to assignment server
[20:33:41] Connecting to http://assign.stanford.edu:8080/
[20:33:41] Posted data.
[20:33:41] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:33:41] + News From Folding@Home: Welcome to Folding@Home
20:33:41] Loaded queue successfully.
[20:33:41] Connecting to http://171.64.65.56:8080/
[20:33:41] - Couldn't send HTTP request to server
[20:33:41]   (Got status 503)
[20:33:41] + Could not connect to Work Server
[20:33:41] - Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[20:33:56] + Attempting to get work packet
[20:33:56] - Will indicate memory of 500 MB
[20:33:56] - Connecting to assignment server
[20:33:56] Connecting to http://assign.stanford.edu:8080/
[20:33:57] Posted data.
[20:33:57] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:33:57] + News From Folding@Home: Welcome to Folding@Home
[20:33:57] Loaded queue successfully.
[20:33:57] Connecting to http://171.64.65.56:8080/
[20:33:57] - Couldn't send HTTP request to server
[20:33:57]   (Got status 503)
[20:33:57] + Could not connect to Work Server
[20:33:57] - Attempt #3  to get work failed, and no other work to do.
             Waiting before retry.
[20:34:28] + Attempting to get work packet
[20:34:28] - Will indicate memory of 500 MB
[20:34:28] - Connecting to assignment server
[20:34:28] Connecting to http://assign.stanford.edu:8080/
[20:34:28] Posted data.
[20:34:28] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:34:28] + News From Folding@Home: Welcome to Folding@Home
[20:34:28] Loaded queue successfully.
[20:34:28] Connecting to http://171.64.65.56:8080/
[20:34:28] - Couldn't send HTTP request to server
[20:34:28]   (Got status 503)
[20:34:28] + Could not connect to Work Server
[20:34:28] - Attempt #4  to get work failed, and no other work to do.
             Waiting before retry.
[20:35:14] + Attempting to get work packet
[20:35:14] - Will indicate memory of 500 MB
[20:35:14] - Connecting to assignment server
[20:35:14] Connecting to http://assign.stanford.edu:8080/
[20:35:14] Posted data.
[20:35:14] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:35:14] + News From Folding@Home: Welcome to Folding@Home
[20:35:14] Loaded queue successfully.
[20:35:14] Connecting to http://171.64.65.56:8080/
[20:35:15] - Couldn't send HTTP request to server
[20:35:15]   (Got status 503)
[20:35:15] + Could not connect to Work Server
[20:35:15] - Attempt #5  to get work failed, and no other work to do.
             Waiting before retry.
[20:36:40] + Attempting to get work packet
[20:36:40] - Will indicate memory of 500 MB
[20:36:40] - Connecting to assignment server
[20:36:40] Connecting to http://assign.stanford.edu:8080/
[20:36:40] Posted data.
[20:36:40] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:36:40] + News From Folding@Home: Welcome to Folding@Home
[20:36:41] Loaded queue successfully.
[20:36:41] Connecting to http://171.64.65.56:8080/
[20:36:41] - Couldn't send HTTP request to server
[20:36:41]   (Got status 503)
[20:36:41] + Could not connect to Work Server
[20:36:41] - Attempt #6  to get work failed, and no other work to do.
             Waiting before retry.
[20:39:34] + Attempting to get work packet
[20:39:34] - Will indicate memory of 500 MB
[20:39:34] - Connecting to assignment server
[20:39:34] Connecting to http://assign.stanford.edu:8080/
[20:39:35] Posted data.
[20:39:35] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:39:35] + News From Folding@Home: Welcome to Folding@Home
[20:39:35] Loaded queue successfully.
[20:39:35] Connecting to http://171.64.65.56:8080/
[20:39:35] - Couldn't send HTTP request to server
[20:39:35]   (Got status 503)
[20:39:35] + Could not connect to Work Server
[20:39:35] - Attempt #7  to get work failed, and no other work to do.
             Waiting before retry.
[20:44:59] + Attempting to get work packet
[20:44:59] - Will indicate memory of 500 MB
[20:44:59] - Connecting to assignment server
[20:44:59] Connecting to http://assign.stanford.edu:8080/
[20:45:00] Posted data.
[20:45:00] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[20:45:00] + News From Folding@Home: Welcome to Folding@Home
[20:45:00] Loaded queue successfully.
[20:45:00] Connecting to http://171.64.65.56:8080/
[20:45:00] - Couldn't send HTTP request to server
[20:45:00]   (Got status 503)
[20:45:00] + Could not connect to Work Server
[20:45:00] - Attempt #8  to get work failed, and no other work to do.
             Waiting before retry.

[kasson]

Things seem a bit clogged there--I'm restarting the server code.

[owbert]

@kasson, thank you.

[joshH]

Still have been getting this error for the past 5 hours on 171.64.65.56 trying to download a WU. My friend has also been getting the same error trying to upload a wu.

[Shadowtester]

Still getting the 503 status here trying to upload a completed smp wu and no new work available.

[ikerekes]

[02:06:49] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[02:06:49] + News From Folding@Home: Welcome to Folding@Home
[02:06:49] Loaded queue successfully.
[02:06:49] Connecting to http://171.64.65.56:8080/
[02:06:49] - Couldn't send HTTP request to server
[02:06:49] (Got status 503)
[02:06:49] + Could not connect to Work Server
[02:06:49] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[02:07:36] + Attempting to get work packet
[02:07:36] - Will indicate memory of 2004 MB
[02:07:36] - Connecting to assignment server
[02:07:36] Connecting to http://assign.stanford.edu:8080/
[02:07:36] Posted data.
[02:07:36] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[02:07:36] + News From Folding@Home: Welcome to Folding@Home
[02:07:37] Loaded queue successfully.
[02:07:37] Connecting to http://171.64.65.56:8080/
[02:07:37] - Couldn't send HTTP request to server
[02:07:37] + Could not connect to Work Server
[02:07:37] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.

[Ultra Nexus]

Much better now! Got a new WU. Thanks.

[PlayLoud]

I'm still getting 503 status

[joshH]

Everything's fine now for me. Restarted the clients.

[BrokenWolf]

I am still getting the 503 error on most of my Linux folding systems. I have restarted them, let them fail up to #10, stopped and started them again to no avail.

I did some searching and this is what I found for the 503 error. This is from a company wanting to sell you monitoring service but the technicial part still applies.

HTTP Error 503 - Service unavailable

Introduction

Your Web server is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.

503 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

* Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
* Open an IP socket connection to that IP address.
* Write an HTTP data stream through that socket.
* Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '503'.

Resolving 503 errors

Your Web server is effectively 'closed for repair'. It is still functioning minimally because it can at least respond with a 503 status code, but full service is impossible i.e. your Web site is simply unavailable. There are a myriad possible reasons for this, but generally it is because of some human intervention by the operators of your Web server machine. You can usually expect that someone is working on the problem, and normal service will resume as soon as possible.

Please contact the system operators of your Web site (e.g. your ISP) to determine why the service is down. They will be in a much better position to help you than we are for this type of error.
@ http://www.checkupdown.com/status/E503.html

Thanks,

BrokenWolf

[kasson]

Two things:
#1: I can pull up the server from my computer (currently at home, not on the stanford net) right now, so you should be able to connect at this time.

#2: Each server allows a maximum # of simultaneous connections. If that # is reached, the server will return a 503 on additional requests. So when a server is heavily loaded, you can get 503's (particularly for an SMP server, where the work units take a lot of memory and we can't allow as many simultaneous connections as servers with small work units).

Hope this helps.

[314159]

I am sitting here with 12 queued WUs from xx.56, all from this afternoon (fairly large folding farm in my home).

Fortunately, all have plenty of time remaining before their preferred deadlines.

It seems to me that restarting the client, rather than letting the client attempt a send at the built-in 6 hour interval, simply serves to increase the server overload. I saw nothing but 503's a couple of hours ago when WUs from xx.56 completed.

Rather than getting a connection to the assigned server at WU completion, xx.56 in ALL cases with its a2 core Linux WUs (THANKS KASSON), I was stuck with a1's from xx.64. <-- sad, not mad, and not kasson's fault........

BUT, I ABSOLUTELY force a send attempt, usually with -send xx, if the "preferred deadline" ever gets even close to 2 hours of remaining time.

In the many years that I have been involved in this project, and with 44k plus WUs completed, I only recall losing credit for one due to deadline issues - using the client's normal send attempt subroutines.

Fold on! (but please don't contribute to server overload)

John

Edit: apparently our SMP guru was posting at the same time that I was writing this.
I do, however, stick with the recommendation of letting the client "do its thing" vs. forcing a send to an already overloaded server.....