Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

171.64.65.56 not responding

https://foldingforum.org/viewtopic.php?t=12022

Page 19 of 25

Re: 171.64.65.56 is in Reject status

Posted: Tue Oct 20, 2009 5:43 pm
by Pick2
kasson wrote:Server restarted. A simple sentence is usually sufficient rather than pasting a stats line. If I were a perl script, I'd be able to process serverstat directly. :)
To us , kasson , you are a Pearl :P
He Who resets our servers :mrgreen:
Just need to work on the script part :lol:

Re: 171.64.65.56 is in Reject status

Posted: Wed Oct 21, 2009 7:40 am
by julio
kasson wrote:Server restarted. A simple sentence is usually sufficient rather than pasting a stats line. If I were a perl script, I'd be able to process serverstat directly. :)
Today 21 Oct I have this message

Code: Select all

Executable: ./FAH504-Linux.exe


[07:24:52] - Ask before connecting: No
[07:24:52] - User name: Julio (Team 0)
[07:24:52] - User ID: 66F189AA633DAEA1
[07:24:52] - Machine ID: 1
[07:24:52] 
[07:24:52] Loaded queue successfully.
[07:24:52] + Benchmarking ...
[07:24:57] - Preparing to get new work unit...
[07:24:57] + Attempting to get work packet
[07:24:57] - Connecting to assignment server
[07:25:03] - Successful: assigned to (171.67.108.13).
[07:25:03] + News From Folding@Home: Welcome to Folding@Home
[07:25:03] Loaded queue successfully.
[07:25:07] - Error: Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.

Re: 171.64.65.56 is in Reject status

Posted: Wed Oct 21, 2009 8:11 am
by toTOW
This is not the same server ...

Re: 171.64.65.56 is in Reject status

Posted: Sat Oct 24, 2009 4:11 pm
by ikerekes
171.64.65.56 in Reject status - Again

Re: 171.64.65.56 is in Reject status

Posted: Sat Oct 24, 2009 6:09 pm
by ikerekes
nwm it is up now, thanks Dr Kasson

Re: 171.64.65.56 is in Reject status

Posted: Sun Oct 25, 2009 2:46 am
by kasson
Ok--glad it's working for you again.

171.64.65.56 not responding

Posted: Sun Nov 01, 2009 12:34 am
by weedacres
Getting 503's. Service status shows ok and no response to browser query.

Code: Select all


--- Opening Log file [October 31 17:24:27] 


# SMP Client ##################################################################
###############################################################################

                       Folding@Home Client Version 6.02

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /etc/folding/1
Executable: ./fah6
Arguments: -local -forceasm -smp 4 

Warning:
 By using the -forceasm flag, you are overriding
 safeguards in the program. If you did not intend to
 do this, please restart the program without -forceasm.
 If work units are not completing fully (and particularly
 if your machine is overclocked), then please discontinue
 use of the flag.

[17:24:27] - Ask before connecting: No
[17:24:27] - User name: Meema (Team 52523)
[17:24:27] - User ID: CF3CE6B78BAA958
[17:24:27] - Machine ID: 1
[17:24:27] 
[17:24:28] Loaded queue successfully.


[17:24:28] + Attempting to send results
[17:24:28] - Preparing to get new work unit...
[17:24:28] + Attempting to get work packet
[17:24:28] - Connecting to assignment server
[17:24:28] - Couldn't send HTTP request to server
[17:24:28] + Could not connect to Work Server (results)
[17:24:28]     (171.64.65.56:8080)
[17:24:28] - Error: Could not transmit unit 01 (completed October 31) to work server.


[17:24:28] + Attempting to send results
[17:24:28] - Successful: assigned to (171.64.65.56).
[17:24:28] + News From Folding@Home: Welcome to Folding@Home
[17:24:28] - Couldn't send HTTP request to server
[17:24:28] + Could not connect to Work Server (results)
[17:24:28]     (171.67.108.25:8080)
[17:24:28]   Could not transmit unit 01 to Collection server; keeping in queue.
[17:24:28] Loaded queue successfully.
[17:24:28] - Couldn't send HTTP request to server
[17:24:28]   (Got status 503)
[17:24:28] + Could not connect to Work Server
[17:24:28] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[17:24:42] + Attempting to get work packet
[17:24:42] - Connecting to assignment server
[17:24:42] - Successful: assigned to (171.64.65.56).
[17:24:42] + News From Folding@Home: Welcome to Folding@Home
[17:24:43] Loaded queue successfully.
[17:24:43] - Couldn't send HTTP request to server
[17:24:43]   (Got status 503)
[17:24:43] + Could not connect to Work Server
[17:24:43] - Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[17:25:00] + Attempting to get work packet
[17:25:00] - Connecting to assignment server
[17:25:00] - Successful: assigned to (171.64.65.56).
[17:25:00] + News From Folding@Home: Welcome to Folding@Home
[17:25:00] Loaded queue successfully.
[17:25:00] - Couldn't send HTTP request to server
[17:25:00]   (Got status 503)
[17:25:00] + Could not connect to Work Server
[17:25:00] - Attempt #3  to get work failed, and no other work to do.
             Waiting before retry.
[17:25:30] + Attempting to get work packet
[17:25:30] - Connecting to assignment server
[17:25:30] - Successful: assigned to (171.64.65.56).
[17:25:30] + News From Folding@Home: Welcome to Folding@Home
[17:25:30] Loaded queue successfully.
[17:25:31] - Couldn't send HTTP request to server
[17:25:31]   (Got status 503)
[17:25:31] + Could not connect to Work Server
[17:25:31] - Attempt #4  to get work failed, and no other work to do.
             Waiting before retry.
[17:26:15] + Attempting to get work packet
[17:26:15] - Connecting to assignment server
[17:26:16] - Successful: assigned to (171.64.65.56).
[17:26:16] + News From Folding@Home: Welcome to Folding@Home
[17:26:16] Loaded queue successfully.
[17:26:16] - Couldn't send HTTP request to server
[17:26:16]   (Got status 503)
[17:26:16] + Could not connect to Work Server
[17:26:16] - Attempt #5  to get work failed, and no other work to do.
             Waiting before retry.

Folding@Home Client Shutdown.


--- Opening Log file [October 31 17:27:12] 


# SMP Client ##################################################################
###############################################################################

                       Folding@Home Client Version 6.02

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: /etc/folding/1
Executable: ./fah6
Arguments: -smp 4 

[17:27:12] - Ask before connecting: No
[17:27:12] - User name: Meema (Team 52523)
[17:27:12] - User ID: CF3CE6B78BAA958
[17:27:12] - Machine ID: 1
[17:27:12] 
[17:27:12] Loaded queue successfully.
[17:27:12] Deleting incompletely fetched item (4) from queue position #2
[17:27:12] - Preparing to get new work unit...


[17:27:12] + Attempting to send results
[17:27:12] + Attempting to get work packet
[17:27:12] - Connecting to assignment server
[17:27:12] - Successful: assigned to (171.64.65.56).
[17:27:12] + News From Folding@Home: Welcome to Folding@Home
[17:27:13] Loaded queue successfully.
[17:27:13] - Couldn't send HTTP request to server
[17:27:13]   (Got status 503)
[17:27:13] + Could not connect to Work Server
[17:27:13] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[17:27:20] + Attempting to get work packet
[17:27:20] - Connecting to assignment server
[17:27:20] - Successful: assigned to (171.64.65.56).
[17:27:20] + News From Folding@Home: Welcome to Folding@Home
[17:27:20] Loaded queue successfully.
[17:27:20] - Couldn't send HTTP request to server
[17:27:20]   (Got status 503)
[17:27:20] + Could not connect to Work Server
[17:27:20] - Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[17:27:31] + Attempting to get work packet
[17:27:31] - Connecting to assignment server
[17:27:31] - Successful: assigned to (171.64.65.56).
[17:27:31] + News From Folding@Home: Welcome to Folding@Home
[17:27:31] Loaded queue successfully.
[17:27:31] - Couldn't send HTTP request to server
[17:27:31]   (Got status 503)
[17:27:31] + Could not connect to Work Server
[17:27:31] - Attempt #3  to get work failed, and no other work to do.
             Waiting before retry.
[17:28:05] + Attempting to get work packet
[17:28:05] - Connecting to assignment server
[17:28:05] - Successful: assigned to (171.64.65.56).
[17:28:05] + News From Folding@Home: Welcome to Folding@Home
[17:28:05] Loaded queue successfully.
[17:28:05] - Couldn't send HTTP request to server
[17:28:05]   (Got status 503)
[17:28:05] + Could not connect to Work Server
[17:28:05] - Attempt #4  to get work failed, and no other work to do.
             Waiting before retry.
[17:28:59] + Attempting to get work packet
[17:28:59] - Connecting to assignment server
[17:28:59] - Successful: assigned to (171.64.65.56).
[17:28:59] + News From Folding@Home: Welcome to Folding@Home
[17:29:00] Loaded queue successfully.
[17:29:00] - Couldn't send HTTP request to server
[17:29:00]   (Got status 503)
[17:29:00] + Could not connect to Work Server
[17:29:00] - Attempt #5  to get work failed, and no other work to do.
             Waiting before retry.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 2:09 am
by Grandpa_01
Same here

Code: Select all

[18:39:37] + Attempting to send results
[18:55:42] - Couldn't send HTTP request to server
[18:55:42] + Could not connect to Work Server (results)
[18:55:42]     (171.64.65.56:8080)
[18:55:42] - Error: Could not transmit unit 07 (completed October 31) to work server.
[18:55:42]   Keeping unit 07 in queue.


[18:55:42] + Attempting to send results

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 2:11 am
by weedacres
I guess I wasn't clear in the previous post.
This server seems to be down although server status would indicate otherwise.
It won't send or receive any workunits. I currently have 2 smp clients waiting for work with several more nearing completion.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 2:24 am
by weedacres
Grandpa_01 wrote:Same here

Code: Select all

[18:39:37] + Attempting to send results
[18:55:42] - Couldn't send HTTP request to server
[18:55:42] + Could not connect to Work Server (results)
[18:55:42]     (171.64.65.56:8080)
[18:55:42] - Error: Could not transmit unit 07 (completed October 31) to work server.
[18:55:42]   Keeping unit 07 in queue.


[18:55:42] + Attempting to send results
Well misery loves company as they say. :e?:

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 2:37 am
by Viper666
[02:01:25] - Couldn't send HTTP request to server
[02:01:25] (Got status 503)
[02:01:25] + Could not connect to Work Server (results)
[02:01:25] (171.64.65.56:80)

HTTP Error 503 - Service unavailable

Introduction

The Web server (running the Web site) 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 the Web server:

* Obtain an IP address from the IP name of the site (the 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 the 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'.

Fixing 503 errors

The 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. the 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 the 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 the 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.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 2:45 am
by weedacres
Please contact the system operators of the 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.
You wouldn't happen to have their number would you? :mrgreen:

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 3:09 am
by 7im
weedacres wrote:You wouldn't happen to have their number would you? :mrgreen:

Why, yes, I do. ;) Ringing...

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 3:22 am
by 7im
Try it now... 8-)

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 3:32 am
by weedacres
7im wrote:Try it now... 8-)
WOW,, I am impressed :eo

4 smp's back in operation :D

Thanks :!:
All times are UTC
Page 19 of 25

Powered by phpBB® Forum Software © phpBB Limited