Page 1 of 5

171.67.108.20 Could not connect to Work Server

Posted: Mon Aug 03, 2009 12:06 am
by Nobleatreides
[23:56:22] + Attempting to get work packet
[23:56:22] - Connecting to assignment server
[23:56:23] - Successful: assigned to (171.67.108.20).
[23:56:23] + News From Folding@Home: Welcome to Folding@Home
[23:56:23] Loaded queue successfully.
[23:56:23] - Couldn't send HTTP request to server
[23:56:23] + Could not connect to Work Server
[23:56:23] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.

I just installed FAH v6.23, am i missing somethiong? do i need to port forward anything to get this to work?

Re: 171.67.108.20 Could not connect to Work Server

Posted: Mon Aug 03, 2009 12:23 am
by bruce
Welcome to the foldingforum.org community forum, Nobleatreides.

You should not need port forwarding, but you do need to make sure that you don't have a firewall that's blocking the FAH program from connecting to the internet.

I am able to open both http://171.67.108.20:8080/ and http://171.67.108.20/ in my browser and the server status page indicates that this server is functioning normally. The folding client acts like an alternative browser but many firewalls block it until you grant it an exception.

Re: 171.67.108.20 Could not connect to Work Server

Posted: Tue Aug 04, 2009 4:13 pm
by Pette Broad
Looking at the server itself it seems to be stuck at 10,000 available units, seen this before and its a sign that somethings wrong.
Tue Aug 4 08:00:11 PDT 2009 171.67.108.20 classic vsp11v gbowman accept Accepting 0.29 0 0 999 26812 8572 0 0 10000 10000 10000 - - - - 397 0 - - 1 - 171.67.108.26 0 1 - - - - - - - ; - - - - - - 0 gbowman 1 vsp11v
Tue Aug 4 08:15:10 PDT 2009 171.67.108.20 classic vsp11v gbowman accept Accepting 0.22 0 0 999 26812 8572 1 0 10000 10000 10000 - - - - 422 0 - - 1 - 171.67.108.26 0 1 - - - - - - - ; - - - - - - 0 gbowman 1 vsp11v
Tue Aug 4 08:30:10 PDT 2009 171.67.108.20 classic vsp11v gbowman accept Accepting 0.20 0 0 999 26812 8572 0 0 10000 10000 10000 - - - - 474 0 - - 1 - 171.67.108.26 0 1 - - - - - - - ; - - - - - - 0 gbowman 1 vsp11v
Tue Aug 4 08:45:10 PDT 2009 171.67.108.20 classic vsp11v gbowman accept Accepting 0.25 0 0 999 26812 8572 0 0 10000 10000 10000 - - - - 519 0 - - 1 - 171.67.108.26 0 1 - - - - - - - ; - - - - - - 0 gbowman 1 vsp11v
Has been like this from the top of the server status log!!

Pete

Re: 171.67.108.20 Could not connect to Work Server

Posted: Tue Aug 04, 2009 8:26 pm
by scruzerdude
I just downloaded the console client (zip file) and am seeing "Couldn't send HTTP request to server". I can visit the IP address in Firefox and see a page with "OK". But the client repeatedly fails to connect.

Perhaps the server needs a reboot :roll:

Re: 171.67.108.20 Could not connect to Work Server

Posted: Tue Aug 04, 2009 10:44 pm
by bruce
I agree that the 10000 numbers look suspicious, but look at WUs RCV which clearly indicates that results are being uploaded to it. (The numbers appear to reset when the Stats are updated.)

I only see three projects that are being assigned by that server: 3770, and 4436-4437 and all three of those projects show a missing atom count on psummary so something isn't configured correctly but I'm not convinced we have enough information to figure out what's wrong or how serious it is.

Re: 171.67.108.20 Could not connect to Work Server

Posted: Wed Aug 05, 2009 1:22 am
by codysluder
That server has gone from STATUS=full to STATUS=accept so the problem has probably been fixed. In that status, we'll still be able to upload completed WUs but the assignment server won't be sending us there for new work. It still says there are 10000 WUs available, but as you said, that number is suspicious.

Re: 171.67.108.20 Could not connect to Work Server

Posted: Tue Oct 06, 2009 5:58 pm
by Rum@NoV
I have some trouble with 2 clients:
[17:54:53] + Attempting to get work packet
[17:54:53] - Will indicate memory of 2047 MB
[17:54:53] - Connecting to assignment server
[17:54:53] Connecting to http://assign.stanford.edu:8080/
[17:54:54] Posted data.
[17:54:54] Initial: 43AB; - Successful: assigned to (171.67.108.20).
[17:54:54] + News From Folding@Home: Welcome to Folding@Home
[17:54:54] Loaded queue successfully.
[17:54:54] Connecting to http://171.67.108.20:8080/
[17:55:00] - Couldn't send HTTP request to server
[17:55:00] + Could not connect to Work Server
[17:55:00] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
No luck for the past 8 hours. Can somebody please check this server?

Re: 171.67.108.20 Could not connect to Work Server

Posted: Tue Oct 06, 2009 10:13 pm
by Pette Broad
No luck for the past 8 hours. Can somebody please check this server?

Your'e right, getting work is a matter of luck right now for classic units and I'm sure that's not good for the project!! There just isn't enough work to go around and its been like this for days. I've got machines on their 15th/16th attempt to get work, doesn't matter what flags I use the work is only being picked up randomly :(

Pete

Re: 171.67.108.20 Could not connect to Work Server

Posted: Wed Oct 07, 2009 11:34 am
by v00d00
This explains why im having major problems getting work at the minute.

Can someone PM Kasson or one of the other PG regulars and ask them to generate a couple thousand new workunits for us? Unless of course they've run out of science stuff for us to do (which as far as im aware is not the case ;) ).

For the linux users stuck in this loop, you can try (like i have) to scrounge windows units by running fah over wine, which has gotten me a couple of workunits.

Re: 171.67.108.20 Could not connect to Work Server

Posted: Thu Oct 08, 2009 3:12 pm
by tonic
10 clients on 3 different machines all getting this error now. We need some new WUs!

Re: 171.67.108.20 Could not connect to Work Server

Posted: Thu Oct 08, 2009 10:21 pm
by tonic
Still stuck. Can I force my clients to use a different server? Not sure why they are all using the .20 server that's obviously not working

Re: 171.67.108.20 Could not connect to Work Server

Posted: Fri Oct 09, 2009 4:21 pm
by FaaR
Almost all my single-core CPU clients are now out of work (6/8, and 2 more will be done in 1-3 hours), and none of them can get new work.

At least one client has been out of work for over a full day now.

Please fix. My PCs are getting restless! :D

Re: 171.67.108.20 Could not connect to Work Server

Posted: Sat Oct 10, 2009 10:50 am
by whynot
There's something I can't get:

Code: Select all

{8766:27} [0:0]% time telnet 171.67.108.20 8080 
Trying 171.67.108.20...
Connected to 171.67.108.20.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
telnet 171.67.108.20 8080  0.00s user 0.00s system 0% cpu 32.451 total
That beast supposed to say something (within 30sec), isn't it? According to serverstat page vsp11v is in accept; then nobody should be sent there, shouldn't her/him? I've tried all WSes from my logs -- some of them are smoking strange stuff too (should I look for server specific thread for each of them?).

PG? Admins? Mods? Anyone?

Re: 171.67.108.20 Could not connect to Work Server

Posted: Sat Oct 10, 2009 12:03 pm
by chrisretusn
All of my clients have finally received new assignments. :)

Re: 171.67.108.20 Could not connect to Work Server

Posted: Mon Oct 26, 2009 1:21 am
by tjclifford
I'm getting this message too; but generally on my Linux box (Redhat fc6 - I'd be running a more updated version, but when
I tried to run Folding 5.04 on a higher version, it would not run, so I back-revved.

This is the most recent log entries (21:18 EST, 2009-10-25):


--- Opening Log file [October 26 01:07:22]


# Linux Console Edition #######################################################
###############################################################################

Folding@Home Client Version 5.04beta

http://folding.stanford.edu

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

Launch directory: /home/tom/foldingathome
Executable: ./FAH504-Linux.exe


[01:07:22] - Ask before connecting: No
[01:07:22] - User name: tjclifford2 (Team 78002)
[01:07:22] - User ID: 1701BE9F58A44E17
[01:07:22] - Machine ID: 1
[01:07:22]
[01:07:23] Loaded queue successfully.
[01:07:23] + Benchmarking ...
[01:07:27] - Preparing to get new work unit...
[01:07:27] + Attempting to get work packet
[01:07:27] - Connecting to assignment server
[01:10:37] - Couldn't send HTTP request to server
[01:10:37] + Could not connect to Assignment Server
[01:10:37] - Successful: assigned to (171.67.108.13).
[01:10:37] + News From Folding@Home: Welcome to Folding@Home
[01:10:37] Loaded queue successfully.
[01:10:38] + Could not connect to Work Server
[01:10:38] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[01:10:52] + Attempting to get work packet
[01:10:52] - Connecting to assignment server
[01:14:01] - Couldn't send HTTP request to server
[01:14:01] + Could not connect to Assignment Server
[01:14:01] - Successful: assigned to (171.67.108.13).
[01:14:01] + News From Folding@Home: Welcome to Folding@Home
[01:14:02] Loaded queue successfully.
[01:14:02] + Could not connect to Work Server
[01:14:02] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[01:14:20] + Attempting to get work packet
[01:14:20] - Connecting to assignment server
[01:17:29] - Couldn't send HTTP request to server
[01:17:29] + Could not connect to Assignment Server
[01:17:30] - Successful: assigned to (171.67.108.13).
[01:17:30] + News From Folding@Home: Welcome to Folding@Home
[01:17:30] Loaded queue successfully.
[01:17:30] + Could not connect to Work Server
[01:17:30] - Error: Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[01:17:52] + Attempting to get work packet
[01:17:52] - Connecting to assignment server