171.67.108.22 Could not connect to Work Server

coccola · Post by **coccola** » Mon Apr 19, 2010 2:55 pm

I checked all connections, firewall settings (nothing changed) and everything is OK. Server status is Accepting. Already followed "Do this first" topic, it's OK. Help!

Code: Select all

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

Folding@Home Client Version 6.29

http://folding.stanford.edu

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

Launch directory: /usr/local/fah
Executable: ./fah6
Arguments: -bigadv -oneunit -smp 8

[14:16:33] - Ask before connecting: No
[14:16:33] - User name: coccola (Team 86565)
[14:16:33] - User ID: 2149C7372E8A8F29
[14:16:33] - Machine ID: 1
[14:16:33]
[14:16:34] Loaded queue successfully.
[14:16:34] - Preparing to get new work unit...
[14:16:34] Cleaning up work directory
[14:17:18] + Attempting to get work packet
[14:17:18] Passkey found
[14:17:19] - Connecting to assignment server
[14:17:21] - Successful: assigned to (171.67.108.22).
[14:17:21] + News From Folding@Home: Welcome to Folding@Home
[14:17:21] Loaded queue successfully.
[14:17:22] + Could not connect to Work Server
[14:17:22] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[14:17:28] + Attempting to get work packet
[14:17:28] Passkey found
[14:17:28] - Connecting to assignment server
[14:17:29] - Successful: assigned to (171.67.108.22).
[14:17:29] + News From Folding@Home: Welcome to Folding@Home
[14:17:29] Loaded queue successfully.
[14:17:34] + Could not connect to Work Server
[14:17:34] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[14:17:54] + Attempting to get work packet
[14:17:54] Passkey found
[14:17:54] - Connecting to assignment server
[14:17:55] - Successful: assigned to (171.67.108.22).
[14:17:55] + News From Folding@Home: Welcome to Folding@Home
[14:17:55] Loaded queue successfully.
[14:17:57] + Could not connect to Work Server
[14:17:57] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[14:18:31] + Attempting to get work packet
[14:18:31] Passkey found
[14:18:31] - Connecting to assignment server
[14:18:33] - Successful: assigned to (171.67.108.22).
[14:18:33] + News From Folding@Home: Welcome to Folding@Home
[14:18:33] Loaded queue successfully.
[14:18:34] + Could not connect to Work Server
[14:18:34] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[14:19:19] + Attempting to get work packet
[14:19:19] Passkey found
[14:19:19] - Connecting to assignment server
[14:19:23] - Successful: assigned to (171.67.108.22).
[14:19:23] + News From Folding@Home: Welcome to Folding@Home
[14:19:23] Loaded queue successfully.
[14:19:24] + Could not connect to Work Server
[14:19:24] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[14:20:54] + Attempting to get work packet
[14:20:54] Passkey found
[14:20:54] - Connecting to assignment server
[14:20:56] - Successful: assigned to (171.67.108.22).
[14:20:56] + News From Folding@Home: Welcome to Folding@Home
[14:20:56] Loaded queue successfully.
[14:20:57] + Could not connect to Work Server
[14:20:57] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[14:23:39] + Attempting to get work packet
[14:23:39] Passkey found
[14:23:39] - Connecting to assignment server
[14:23:41] - Successful: assigned to (171.67.108.22).
[14:23:41] + News From Folding@Home: Welcome to Folding@Home
[14:23:41] Loaded queue successfully.
[14:23:43] + Could not connect to Work Server
[14:23:43] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[14:29:16] + Attempting to get work packet
[14:29:16] Passkey found
[14:29:16] - Connecting to assignment server
[14:29:18] - Successful: assigned to (171.67.108.22).
[14:29:18] + News From Folding@Home: Welcome to Folding@Home
[14:29:18] Loaded queue successfully.
[14:29:20] + Could not connect to Work Server
[14:29:20] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[14:40:06] + Attempting to get work packet
[14:40:06] Passkey found
[14:40:06] - Connecting to assignment server
[14:40:07] - Successful: assigned to (171.67.108.22).
[14:40:07] + News From Folding@Home: Welcome to Folding@Home
[14:40:07] Loaded queue successfully.
[14:40:09] + Could not connect to Work Server
[14:40:09] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.

Folding@Home Client Shutdown.

Post by **toTOW** » Mon Apr 19, 2010 3:26 pm

Server seems up and running ...

How many processors and memory amount are you reporting ?

DrSpalding · Post by **DrSpalding** » Mon Apr 19, 2010 3:29 pm

I think we are suffering from a lack of work units. Based on the FAH-Addict web site, A2 and A3 WUs are in short supply:
http://en.fah-addict.net/news/news-0-20 ... re-wus.php

P5-133XL · Post by **P5-133XL** » Mon Apr 19, 2010 3:38 pm

DrSpalding wrote:I think we are suffering from a lack of work units. Based on the FAH-Addict web site, A2 and A3 WUs are in short supply:
http://en.fah-addict.net/news/news-0-20 ... re-wus.php

Yes, but he has specified -bigadv and as long as he is running Linux, has enough cores and RAM, he would be getting those in preference to A2/A3's.

Post by **toTOW** » Mon Apr 19, 2010 3:40 pm

This shortage shouldn't affect the BigAdv server as far as I know (and it's not mentioned as having problems in the news

) : it has more than 2000 WUs ready, and not so much clients connecting to it ...

DrSpalding · Post by **DrSpalding** » Mon Apr 19, 2010 3:43 pm

A2 WUs may also include bigadv units since they use the same core. I have one client that uploaded a bidadv WU ~7:15 PDT (90 minutes ago) and it has not yet been able to get a new WU either, and if there was a non-bigadv WU available, I would have gotten one of those instead of a bigadv WU. It is still waiting... and it does say:

"Could not connect to Work Server" and the server IP is 171.67.108.22.

Could be a connection issue or just a lack of WUs at this point.

Edit: 08:47 PDT. Good news. It just downloaded a bigadv WU (2681) and is starting up now.

coccola · Post by **coccola** » Mon Apr 19, 2010 4:01 pm

Thanks for replying. Reporting 4457 MB and 8 cores (Intel Core i7 920). No WU yet. Log with verbosity enabled:

Code: Select all

Launch directory: /usr/local/fah
Executable: ./fah6
Arguments: -bigadv -oneunit -verbosity 7 -smp 8

[15:09:24] - Ask before connecting: No
[15:09:24] - User name: coccola (Team 86565)
[15:09:24] - User ID: 2149C7372E8A8F29
[15:09:24] - Machine ID: 1
[15:09:24]
[15:09:24] Loaded queue successfully.
[15:09:24] - Preparing to get new work unit...
[15:09:24] - Autosending finished units... [April 19 15:09:24 UTC]
[15:09:24] Trying to send all finished work units
[15:09:24] + No unsent completed units remaining.
[15:09:24] - Autosend completed
[15:09:24] Cleaning up work directory
[15:09:24] + Attempting to get work packet
[15:09:24] Passkey found
[15:09:24] - Will indicate memory of 4457 MB
[15:09:24] - Connecting to assignment server
[15:09:24] Connecting to http://assign.stanford.edu:8080/
[15:09:26] - Successful: assigned to (171.67.108.22).
[15:09:26] + News From Folding@Home: Welcome to Folding@Home
[15:09:26] Loaded queue successfully.
[15:09:26] Connecting to http://171.67.108.22:8080/
[15:09:30] + Could not connect to Work Server
[15:09:30] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.

7im · Post by **7im** » Mon Apr 19, 2010 4:36 pm

Curious, why the -oneunit flag, and why verbosity 7 instead of 9?

coccola · Post by **coccola** » Mon Apr 19, 2010 5:03 pm

I'm running a pre-built vmware image (evga forums). In its custom settings webpage there's a verbosity checkbox that automatically enables level 7 (it's either no verbosity or verbosity 7).
Oneunit is because sometimes I want or need to reboot my real machine and doing that while processing WUs that reward more points the faster you finish them is not a good idea.

Drugless · Post by **Drugless** » Mon Apr 19, 2010 5:17 pm

Same problem here.

Code: Select all

--- Opening Log file [April 19 17:09:54 UTC] 


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

                       Folding@Home Client Version 6.29

                          http://folding.stanford.edu

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

Launch directory: /home/administrator/folding
Executable: ./fah6
Arguments: -smp 8 -bigadv -verbosity 9 -oneunit 

[17:09:54] - Ask before connecting: No
[17:09:54] - User name: FatCamel (Team 32)
[17:09:54] - User ID: 32018A622887F48D
[17:09:54] - Machine ID: 1
[17:09:54] 
[17:09:54] Loaded queue successfully.
[17:09:54] - Preparing to get new work unit...
[17:09:54] Cleaning up work directory
[17:09:54] - Autosending finished units... [April 19 17:09:54 UTC]
[17:09:54] Trying to send all finished work units
[17:09:54] + No unsent completed units remaining.
[17:09:54] - Autosend completed
[17:09:54] + Attempting to get work packet
[17:09:54] Passkey found
[17:09:54] - Will indicate memory of 5840 MB
[17:09:54] - Connecting to assignment server
[17:09:54] Connecting to http://assign.stanford.edu:8080/
[17:09:56] Posted data.
[17:09:56] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[17:09:56] + News From Folding@Home: Welcome to Folding@Home
[17:09:56] Loaded queue successfully.
[17:09:56] Connecting to http://171.67.108.22:8080/
[17:09:58] Posted data.
[17:09:58] Initial: 0000; + Could not connect to Work Server
[17:09:58] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[17:10:10] + Attempting to get work packet
[17:10:10] Passkey found
[17:10:10] - Will indicate memory of 5840 MB
[17:10:10] - Connecting to assignment server
[17:10:10] Connecting to http://assign.stanford.edu:8080/
[17:10:12] Posted data.
[17:10:12] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[17:10:12] + News From Folding@Home: Welcome to Folding@Home
[17:10:12] Loaded queue successfully.
[17:10:12] Connecting to http://171.67.108.22:8080/
[17:10:14] Posted data.
[17:10:14] Initial: 0000; + Could not connect to Work Server
[17:10:14] - Attempt #2  to get work failed, and no other work to do.

hrsetrdr · Post by **hrsetrdr** » Mon Apr 19, 2010 6:14 pm

[17:13:09] + No unsent completed units remaining.
[17:13:09] - Autosend completed
[17:38:51] Completed 250000 out of 250000 steps (100%)

Writing final coordinates.

Average load imbalance: 0.1 %
Part of the total run time spent waiting due to load imbalance: 0.0 %
Steps where the load balancing was limited by -rdd, -rcon and/or -dds: X 0 %

Parallel run - timing based on wallclock.

NODE (s) Real (s) (%)
Time: 131111.847 131111.847 100.0
1d12h25:11
(Mnbf/s) (GFlops) (ns/day) (hour/ns)
Performance: 442.537 24.135 0.422 56.923

gcq#0: Thanx for Using GROMACS - Have a Nice Day

[17:39:00] DynamicWrapper: Finished Work Unit: sleep=10000
[17:39:10]
[17:39:10] Finished Work Unit:
[17:39:10] - Reading up to 52544928 from "work/wudata_02.trr": Read 52544928
[17:39:10] trr file hash check passed.
[17:39:10] - Reading up to 41984660 from "work/wudata_02.xtc": Read 41984660
[17:39:10] xtc file hash check passed.
[17:39:10] edr file hash check passed.
[17:39:10] logfile size: 206788
[17:39:10] Leaving Run
[17:39:11] - Writing 94901292 bytes of core data to disk...
[17:39:15] ... Done.
[17:39:28] - Shutting down core
[17:39:28]
[17:39:28] Folding@home Core Shutdown: FINISHED_UNIT
Attempting to use an MPI routine after finalizing MPICH
[17:42:34] CoreStatus = 64 (100)
[17:42:34] Unit 2 finished with 60 percent of time to deadline remaining.
[17:42:34] Updated performance fraction: 0.597925
[17:42:34] Sending work to server
[17:42:34] Project: 2683 (Run 12, Clone 17, Gen 35)

[17:42:34] + Attempting to send results [April 19 17:42:34 UTC]
[17:42:34] - Reading file work/wuresults_02.dat from core
[17:42:34] (Read 94901292 bytes from disk)
[17:42:34] Connecting to http://171.67.108.22:8080/
[17:59:48] Posted data.
[17:59:48] Initial: 0000; - Uploaded at ~66 kB/s
[18:05:39] - Averaged speed for that direction ~70 kB/s
[18:05:39] + Results successfully sent
[18:05:39] Thank you for your contribution to Folding@Home.
[18:05:39] + Number of Units Completed: 51

[18:05:42] - Warning: Could not delete all work unit files (2): Core file absent
[18:05:42] Trying to send all finished work units
[18:05:42] + No unsent completed units remaining.
[18:05:42] - Preparing to get new work unit...
[18:05:42] Cleaning up work directory
[18:05:43] + Attempting to get work packet
[18:05:43] Passkey found
[18:05:43] - Will indicate memory of 5986 MB
[18:05:43] - Connecting to assignment server
[18:05:43] Connecting to http://assign.stanford.edu:8080/
[18:05:44] Posted data.
[18:05:44] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[18:05:44] + News From Folding@Home: Welcome to Folding@Home
[18:05:44] Loaded queue successfully.
[18:05:44] Connecting to http://171.67.108.22:8080/
[18:05:44] Posted data.
[18:05:44] Initial: 0000; + Could not connect to Work Server
[18:05:44] - Attempt #1 to get work failed, and no other work to do.

six attempts and counting...

coccola · Post by **coccola** » Mon Apr 19, 2010 6:19 pm

I can't understand it. Why isn't another WU is assigned? All this time doing nothing. Things could be changed so that the server is changed after a certain number of attempts...

Still no WU. As the time between attempts increases over time, I have to reboot my machine sometimes.

Post by **bruce** » Mon Apr 19, 2010 6:22 pm

DrSpalding wrote:"Could not connect to Work Server" and the server IP is 171.67.108.22.

Could be a connection issue or just a lack of WUs at this point.

When you have this sort of a problem, the first two steps you should take is to check the ServerStatus page (see the link in our header) and see how many WUs it says it has and try to open http:171.67.108.22:8080 and/or http:171.67.108.22 with your browser. (Use the actual server's IP address, of course.) Most of the time you'll be able to figure out if it's a connection issue or lack of WUs. Then if you're still not sure, ask here.

In this case, there's something strange going on so I'll dig deeper.

Drugless · Post by **Drugless** » Mon Apr 19, 2010 6:33 pm

Did that initially Bruce.
Thanks for investigating.
I just checked server again and same status but now (10:55:10) there are 1762 WU available whereas at 10:15:10 there were only 1705. Weird.

Another machine of mine just finished a bigadv WU and it has same problem.

coccola · Post by **coccola** » Mon Apr 19, 2010 6:35 pm

I've just got a 2683. Thanks for helping!

Folding Forum

171.67.108.22 Could not connect to Work Server

171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server

Re: 171.67.108.22 Could not connect to Work Server