Folding Forum

Posted: **Sun Apr 19, 2009 11:54 pm**

Setting the -advmethods switch should be included in the Do this first thread

-advmethods

Edit by Mod: Done. Thanks for the suggestion.
-b

Posted: **Mon Apr 20, 2009 7:12 am**

i have also problems ba getting new Wu's
but i found nothin suitable for me in the Forum

Code: Select all

[00:48:50] Completed 1500000 out of 1500000 steps  (100%)
[00:48:50] Writing final coordinates.
[00:48:50] Past main M.D. loop
[00:49:50] 
[00:49:50] Finished Work Unit:
[00:49:50] - Reading up to 188712 from "work/wudata_09.arc": Read 188712
[00:49:50] - Reading up to 17688 from "work/wudata_09.xtc": Read 17688
[00:49:50] goefile size: 0
[00:49:50] logfile size: 87191
[00:49:50] Leaving Run
[00:49:52] - Writing 300595 bytes of core data to disk...
[00:49:52] Done: 300083 -> 210719 (compressed to 70.2 percent)
[00:49:52]   ... Done.
[00:49:52] - Shutting down core
[00:49:52] 
[00:49:52] Folding@home Core Shutdown: FINISHED_UNIT
[00:49:56] CoreStatus = 64 (100)
[00:49:56] Sending work to server
[00:49:56] Project: 4459 (Run 525, Clone 2, Gen 11)


[00:49:56] + Attempting to send results [April 20 00:49:56 UTC]
[00:49:58] + Results successfully sent
[00:49:58] Thank you for your contribution to Folding@Home.
[00:49:58] + Number of Units Completed: 147

[00:50:02] - Preparing to get new work unit...
[00:50:02] + Attempting to get work packet
[00:50:02] - Connecting to assignment server
[00:50:05] - Successful: assigned to (171.64.122.139).
[00:50:05] + News From Folding@Home: Welcome to Folding@Home
[00:50:05] Loaded queue successfully.
[00:50:05] - Couldn't send HTTP request to server
[00:50:05] + Could not connect to Work Server
[00:50:05] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[00:50:16] + Attempting to get work packet
[00:50:16] - Connecting to assignment server
[00:50:16] - Successful: assigned to (171.64.122.139).
[00:50:16] + News From Folding@Home: Welcome to Folding@Home
[00:50:17] Loaded queue successfully.
[00:50:17] - Couldn't send HTTP request to server
[00:50:17] + Could not connect to Work Server
[00:50:17] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[00:50:31] + Attempting to get work packet
[00:50:31] - Connecting to assignment server
[00:50:32] - Successful: assigned to (171.64.122.139).
[00:50:32] + News From Folding@Home: Welcome to Folding@Home
[00:50:32] Loaded queue successfully.
[00:50:33] - Couldn't send HTTP request to server
[00:50:33] + Could not connect to Work Server
[00:50:33] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[00:51:01] + Attempting to get work packet
[00:51:01] - Connecting to assignment server
[00:51:02] - Successful: assigned to (171.64.122.139).
[00:51:02] + News From Folding@Home: Welcome to Folding@Home
[00:51:02] Loaded queue successfully.
[00:51:03] - Couldn't send HTTP request to server
[00:51:03] + Could not connect to Work Server
[00:51:03] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[00:51:50] + Attempting to get work packet
[00:51:50] - Connecting to assignment server
[00:51:51] - Successful: assigned to (171.64.122.139).
[00:51:51] + News From Folding@Home: Welcome to Folding@Home
[00:51:51] Loaded queue successfully.
[00:51:51] - Couldn't send HTTP request to server
[00:51:51] + Could not connect to Work Server
[00:51:51] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[00:53:18] + Attempting to get work packet
[00:53:18] - Connecting to assignment server
[00:53:19] - Successful: assigned to (171.64.122.139).
[00:53:19] + News From Folding@Home: Welcome to Folding@Home
[00:53:19] Loaded queue successfully.
[00:53:19] - Couldn't send HTTP request to server
[00:53:19] + Could not connect to Work Server
[00:53:19] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[00:56:12] + Attempting to get work packet
[00:56:12] - Connecting to assignment server
[00:56:13] - Successful: assigned to (171.64.122.139).
[00:56:13] + News From Folding@Home: Welcome to Folding@Home
[00:56:13] Loaded queue successfully.
[00:56:13] - Couldn't send HTTP request to server
[00:56:13] + Could not connect to Work Server
[00:56:13] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[01:01:45] + Attempting to get work packet
[01:01:45] - Connecting to assignment server
[01:01:45] - Successful: assigned to (171.67.108.12).
[01:01:45] + News From Folding@Home: Welcome to Folding@Home
[01:01:46] Loaded queue successfully.
[01:01:47] + Could not connect to Work Server
[01:01:47] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[01:12:36] + Attempting to get work packet
[01:12:36] - Connecting to assignment server
[01:12:37] - Successful: assigned to (171.67.108.13).
[01:12:37] + News From Folding@Home: Welcome to Folding@Home
[01:12:37] Loaded queue successfully.
[01:12:38] + Could not connect to Work Server
[01:12:38] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[01:33:58] + Attempting to get work packet
[01:33:58] - Connecting to assignment server
[01:33:59] - Successful: assigned to (130.49.240.81).
[01:33:59] + News From Folding@Home: Welcome to Folding@Home
[01:33:59] Loaded queue successfully.
[01:34:00] + Could not connect to Work Server
[01:34:00] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[02:16:45] + Attempting to get work packet
[02:16:45] - Connecting to assignment server
[02:16:46] - Successful: assigned to (171.64.65.65).
[02:16:46] + News From Folding@Home: Welcome to Folding@Home
[02:16:46] Loaded queue successfully.
[02:16:46] - Couldn't send HTTP request to server
[02:16:46]   (Got status 503)
[02:16:46] + Could not connect to Work Server
[02:16:46] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[03:04:55] + Attempting to get work packet
[03:04:55] - Connecting to assignment server
[03:04:56] - Successful: assigned to (171.64.65.65).
[03:04:56] + News From Folding@Home: Welcome to Folding@Home
[03:04:56] Loaded queue successfully.
[03:04:56] - Couldn't send HTTP request to server
[03:04:56]   (Got status 503)
[03:04:56] + Could not connect to Work Server
[03:04:56] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[03:52:59] + Attempting to get work packet
[03:52:59] - Connecting to assignment server
[03:53:01] - Successful: assigned to (171.67.108.13).
[03:53:01] + News From Folding@Home: Welcome to Folding@Home
[03:53:01] Loaded queue successfully.
[03:53:03] + Could not connect to Work Server
[03:53:03] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[04:41:09] + Attempting to get work packet
[04:41:09] - Connecting to assignment server
[04:41:10] - Successful: assigned to (171.64.122.139).
[04:41:10] + News From Folding@Home: Welcome to Folding@Home
[04:41:11] Loaded queue successfully.
[04:41:12] - Couldn't send HTTP request to server
[04:41:12] + Could not connect to Work Server
[04:41:12] - Attempt #14  to get work failed, and no other work to do.
Waiting before retry.
[05:29:21] + Attempting to get work packet
[05:29:21] - Connecting to assignment server
[05:29:22] - Successful: assigned to (171.64.122.139).
[05:29:22] + News From Folding@Home: Welcome to Folding@Home
[05:29:23] Loaded queue successfully.
[05:29:23] - Couldn't send HTTP request to server
[05:29:23] + Could not connect to Work Server
[05:29:23] - Attempt #15  to get work failed, and no other work to do.
Waiting before retry.
[06:17:25] + Attempting to get work packet
[06:17:25] - Connecting to assignment server
[06:17:26] - Successful: assigned to (171.67.108.13).
[06:17:26] + News From Folding@Home: Welcome to Folding@Home
[06:17:26] Loaded queue successfully.
[06:17:27] + Could not connect to Work Server
[06:17:27] - Attempt #16  to get work failed, and no other work to do.
Waiting before retry.
[06:45:52] Service stop request received.

Folding@Home Client Shutdown.


--- Opening Log file [April 20 06:45:56 UTC] 


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.20

                          http://folding.stanford.edu

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

Launch directory: C:\Program Files (x86)\Folding@Home\Folding@home console 6_20
Service: C:\Program Files (x86)\Folding@Home\Folding@home console 6_20\[email protected]
Arguments: -svcstart -d C:\Program Files (x86)\Folding@Home\Folding@home console 6_20 

Launched as a service.
Entered C:\Program Files (x86)\Folding@Home\Folding@home console 6_20 to do work.

[06:45:56] - Ask before connecting: No
[06:45:56] - User name: klefreak_gletscherfloh (Team 70335)
[06:45:56] - User ID: 73D4A8A765CF28CD
[06:45:56] - Machine ID: 1
[06:45:56] 
[06:45:56] Loaded queue successfully.
[06:45:56] - Preparing to get new work unit...
[06:45:56] + Attempting to get work packet
[06:45:56] - Connecting to assignment server
[06:45:57] - Successful: assigned to (171.64.122.139).
[06:45:57] + News From Folding@Home: Welcome to Folding@Home
[06:45:57] Loaded queue successfully.
[06:45:57] - Couldn't send HTTP request to server
[06:45:57] + Could not connect to Work Server
[06:45:57] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[06:46:13] + Attempting to get work packet
[06:46:13] - Connecting to assignment server
[06:46:14] - Successful: assigned to (171.64.122.139).
[06:46:14] + News From Folding@Home: Welcome to Folding@Home
[06:46:15] Loaded queue successfully.
[06:46:15] - Couldn't send HTTP request to server
[06:46:15] + Could not connect to Work Server
[06:46:15] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[06:46:33] + Attempting to get work packet
[06:46:33] - Connecting to assignment server
[06:46:34] - Successful: assigned to (171.64.122.139).
[06:46:34] + News From Folding@Home: Welcome to Folding@Home
[06:46:34] Loaded queue successfully.
[06:46:34] - Couldn't send HTTP request to server
[06:46:34] + Could not connect to Work Server
[06:46:34] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[06:46:46] Service stop request received.

Folding@Home Client Shutdown.


--- Opening Log file [April 20 06:47:45 UTC] 


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.20

                          http://folding.stanford.edu

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

Launch directory: C:\Program Files (x86)\Folding@Home\Folding@home console 6_20
Service: C:\Program Files (x86)\Folding@Home\Folding@home console 6_20\[email protected]
Arguments: -svcstart -d C:\Program Files (x86)\Folding@Home\Folding@home console 6_20 

Launched as a service.
Entered C:\Program Files (x86)\Folding@Home\Folding@home console 6_20 to do work.

[06:47:45] - Ask before connecting: No
[06:47:45] - User name: klefreak_gletscherfloh (Team 70335)
[06:47:45] - User ID: 73D4A8A765CF28CD
[06:47:45] - Machine ID: 1
[06:47:45] 
[06:47:45] Work directory not found. Creating...
[06:47:45] Could not open work queue, generating new queue...
[06:47:45] - Preparing to get new work unit...
[06:47:45] + Attempting to get work packet
[06:47:45] - Connecting to assignment server
[06:47:46] - Successful: assigned to (171.64.122.139).
[06:47:46] + News From Folding@Home: Welcome to Folding@Home
[06:47:46] Loaded queue successfully.
[06:47:47] - Couldn't send HTTP request to server
[06:47:47] + Could not connect to Work Server
[06:47:47] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[06:47:54] + Attempting to get work packet
[06:47:54] - Connecting to assignment server
[06:47:54] - Successful: assigned to (171.64.122.139).
[06:47:54] + News From Folding@Home: Welcome to Folding@Home
[06:47:55] Loaded queue successfully.
[06:47:55] - Couldn't send HTTP request to server
[06:47:55] + Could not connect to Work Server
[06:47:55] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[06:48:20] + Attempting to get work packet
[06:48:20] - Connecting to assignment server
[06:48:24] - Successful: assigned to (171.64.122.139).
[06:48:24] + News From Folding@Home: Welcome to Folding@Home
[06:48:24] Loaded queue successfully.
[06:48:25] - Couldn't send HTTP request to server
[06:48:25] + Could not connect to Work Server
[06:48:25] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[06:48:58] + Attempting to get work packet
[06:48:58] - Connecting to assignment server
[06:48:59] - Successful: assigned to (171.64.122.139).
[06:48:59] + News From Folding@Home: Welcome to Folding@Home
[06:48:59] Loaded queue successfully.
[06:49:00] - Couldn't send HTTP request to server
[06:49:00] + Could not connect to Work Server
[06:49:00] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[06:49:54] + Attempting to get work packet
[06:49:54] - Connecting to assignment server
[06:49:55] - Successful: assigned to (171.64.122.139).
[06:49:55] + News From Folding@Home: Welcome to Folding@Home
[06:49:55] Loaded queue successfully.
[06:49:56] - Couldn't send HTTP request to server
[06:49:56] + Could not connect to Work Server
[06:49:56] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[06:51:27] + Attempting to get work packet
[06:51:27] - Connecting to assignment server
[06:51:28] - Successful: assigned to (171.64.122.139).
[06:51:28] + News From Folding@Home: Welcome to Folding@Home
[06:51:28] Loaded queue successfully.
[06:51:29] - Couldn't send HTTP request to server
[06:51:29] + Could not connect to Work Server
[06:51:29] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[06:54:12] + Attempting to get work packet
[06:54:12] - Connecting to assignment server
[06:54:13] - Successful: assigned to (171.67.108.13).
[06:54:13] + News From Folding@Home: Welcome to Folding@Home
[06:54:13] Loaded queue successfully.
[06:54:15] - Couldn't send HTTP request to server
[06:54:15] + Could not connect to Work Server
[06:54:15] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[06:59:37] + Attempting to get work packet
[06:59:37] - Connecting to assignment server
[06:59:38] - Successful: assigned to (171.67.108.13).
[06:59:38] + News From Folding@Home: Welcome to Folding@Home
[06:59:38] Loaded queue successfully.
[06:59:39] + Could not connect to Work Server
[06:59:39] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[07:10:24] + Attempting to get work packet
[07:10:24] - Connecting to assignment server
[07:10:25] - Successful: assigned to (171.64.122.139).
[07:10:25] + News From Folding@Home: Welcome to Folding@Home
[07:10:25] Loaded queue successfully.
[07:10:26] - Couldn't send HTTP request to server
[07:10:26] + Could not connect to Work Server
[07:10:26] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.

Posted: **Mon Apr 20, 2009 4:36 pm**

klefreak wrote:i have also problems ba getting new Wu's
but i found nothin suitable for me in the Forum

I am not sure if the -advmethods switch will show up in your FAHLog if set while using the -configonly switch.
Here is an example where a client launched as a service vs console was configured to use the -advmethods switch but it does not show in the log.
The client is started with the switch > [email protected] -configonly
[23:38:41] -configonly flag given, so exiting. This shows the client stopping. The subsequent restart picks up a WU

Code: Select all

Launch directory: c:\F@H\core2
Executable: [email protected]
Arguments: -configonly 

[23:37:53] - Ask before connecting: No
[23:37:53] - User name: [inMEMORYof]_rangeral (Team 34878)
[23:37:53] - User ID: 242A217030D50FB5
[23:37:53] - Machine ID: 3
[23:37:53] 
[23:37:53] Configuring Folding@Home...


[23:38:41] - Ask before connecting: No
[23:38:41] - User name: [inMEMORYof]_rangeral (Team 34878)
[23:38:41] - User ID: 242A217030D50FB5
[23:38:41] - Machine ID: 3
[23:38:41] 
[23:38:41] -configonly flag given, so exiting.


--- Opening Log file [April 19 23:38:50 UTC] 


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.20

                          http://folding.stanford.edu

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

Launch directory: c:\F@H\core2
Service: c:\F@H\core2\[email protected]
Arguments: -svcstart -d c:\F@H\core2 

Launched as a service.

Have you added the-advmethods switch to the client?

Posted: **Mon Apr 20, 2009 8:35 pm**

Looks like the -advmethods switch does not work either. I now have two clients unable to get work.

Restarting does not help this time either.

Posted: **Mon Apr 20, 2009 9:13 pm**

the strange thing is, that i'm using 2 clients on my dualcore, both launched as a service and both with this options in the config file:

Code: Select all

[settings]
username=klefreak_gletscherfloh
team=70335
passkey=
asknet=no
machineid=1
bigpackets=normal
local=147

[http]
active=no
host=localhost
port=8080
usereg=no

[core]
priority=0
cpuusage=100
disableassembly=no
checkpoint=10
ignoredeadlines=no
nocpulock=0
addr=

[power]
battery=no

[clienttype]
memory=512
type=0

one client is running normal but the other one isn's getting a WU the whole day long ;(

Logfile Working Client

Code: Select all

[18:45:59] Writing local files
[18:45:59] Completed 2500000 out of 2500000 steps  (100%)
[18:45:59] Writing checkpoint files
[18:46:59] 
[18:46:59] Finished Work Unit:
[18:46:59] Leaving Run
[18:46:59] - Writing 201004 bytes of core data to disk...
[18:46:59]   ... Done.
[18:46:59] - Shutting down core
[18:46:59] 
[18:46:59] Folding@home Core Shutdown: FINISHED_UNIT
[18:47:02] CoreStatus = 64 (100)
[18:47:02] Sending work to server
[18:47:02] Project: 4597 (Run 35, Clone 41, Gen 35)


[18:47:02] + Attempting to send results [April 20 18:47:02 UTC]
[18:47:13] + Results successfully sent
[18:47:13] Thank you for your contribution to Folding@Home.
[18:47:13] + Number of Units Completed: 140

[18:47:17] - Preparing to get new work unit...
[18:47:17] + Attempting to get work packet
[18:47:17] - Connecting to assignment server
[18:47:22] - Successful: assigned to (171.67.108.13).
[18:47:22] + News From Folding@Home: Welcome to Folding@Home
[18:47:22] Loaded queue successfully.
[18:47:26] + Could not connect to Work Server
[18:47:26] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:47:44] + Attempting to get work packet
[18:47:44] - Connecting to assignment server
[18:47:45] - Successful: assigned to (171.67.108.13).
[18:47:45] + News From Folding@Home: Welcome to Folding@Home
[18:47:46] Loaded queue successfully.
[18:47:47] + Could not connect to Work Server
[18:47:47] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:48:11] + Attempting to get work packet
[18:48:11] - Connecting to assignment server
[18:48:12] - Successful: assigned to (171.67.108.13).
[18:48:12] + News From Folding@Home: Welcome to Folding@Home
[18:48:13] Loaded queue successfully.
[18:48:15] + Could not connect to Work Server
[18:48:15] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:48:49] + Attempting to get work packet
[18:48:49] - Connecting to assignment server
[18:48:52] - Successful: assigned to (171.67.108.13).
[18:48:52] + News From Folding@Home: Welcome to Folding@Home
[18:48:52] Loaded queue successfully.
[18:48:56] + Could not connect to Work Server
[18:48:56] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:49:40] + Attempting to get work packet
[18:49:40] - Connecting to assignment server
[18:49:43] - Successful: assigned to (171.67.108.13).
[18:49:43] + News From Folding@Home: Welcome to Folding@Home
[18:49:43] Loaded queue successfully.
[18:49:44] + Could not connect to Work Server
[18:49:44] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[18:51:05] + Attempting to get work packet
[18:51:05] - Connecting to assignment server
[18:51:08] - Successful: assigned to (171.67.108.13).
[18:51:08] + News From Folding@Home: Welcome to Folding@Home
[18:51:08] Loaded queue successfully.
[18:51:21] + Could not connect to Work Server
[18:51:21] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[18:54:07] + Attempting to get work packet
[18:54:07] - Connecting to assignment server
[18:54:09] - Successful: assigned to (169.230.26.30).
[18:54:09] + News From Folding@Home: Welcome to Folding@Home
[18:54:09] Loaded queue successfully.
[18:54:14] + Closed connections
[18:54:14] 
[18:54:14] + Processing work unit
[18:54:14] Core required: FahCore_82.exe
[18:54:14] Core found.
[18:54:14] Working on queue slot 06 [April 20 18:54:14 UTC]
[18:54:14] + Working ...
[18:54:14] 
[18:54:14] *------------------------------*
[18:54:14] Folding@Home PMD Core
[18:54:14] Version 1.03 (September 7, 2005)
[18:54:14] 
[18:54:14] Preparing to commence simulation
[18:54:14] - Looking at optimizations...
[18:54:14] - Created dyn
[18:54:14] - Files status OK
[18:54:14] - Expanded 10092 -> 62868 (decompressed 622.9 percent)
[18:54:14] 
[18:54:14] Project: 4602 (Run 19, Clone 52, Gen 13)
[18:54:14] 
[18:54:15] Assembly optimizations on if available.
[18:54:15] Entering M.D.
[18:54:21] Protein: p4602_T0_NTL9-8_minout
[18:54:21] 
[18:54:21] Completed 0 out of 2500000 steps  (0%)
[18:55:36] Writing local files
[18:55:36] Completed 25000 out of 2500000 steps  (1%)

it also didn't get a new WU quikly (but after six retrys !)

Non working Client:

Code: Select all

--- Opening Log file [April 20 12:40:26 UTC] 


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.20

                          http://folding.stanford.edu

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

Launch directory: C:\Program Files (x86)\Folding@Home\Folding@home console 6_20
Service: C:\Program Files (x86)\Folding@Home\Folding@home console 6_20\[email protected]
Arguments: -svcstart -d C:\Program Files (x86)\Folding@Home\Folding@home console 6_20 

Launched as a service.
Entered C:\Program Files (x86)\Folding@Home\Folding@home console 6_20 to do work.

[12:40:26] - Ask before connecting: No
[12:40:26] - User name: klefreak_gletscherfloh (Team 70335)
[12:40:26] - User ID: 73D4A8A765CF28CD
[12:40:26] - Machine ID: 1
[12:40:26] 
[12:40:26] Loaded queue successfully.
[12:40:26] - Preparing to get new work unit...
[12:40:26] + Attempting to get work packet
[12:40:26] - Connecting to assignment server
[12:40:30] - Successful: assigned to (171.67.108.13).
[12:40:30] + News From Folding@Home: Welcome to Folding@Home
[12:40:30] Loaded queue successfully.
[12:40:31] + Could not connect to Work Server
[12:40:31] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[12:40:37] + Attempting to get work packet
[12:40:37] - Connecting to assignment server
[12:40:39] - Successful: assigned to (171.67.108.13).
[12:40:39] + News From Folding@Home: Welcome to Folding@Home
[12:40:39] Loaded queue successfully.
[12:40:42] + Could not connect to Work Server
[12:40:42] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[12:41:06] + Attempting to get work packet
[12:41:06] - Connecting to assignment server
[12:41:08] - Successful: assigned to (171.67.108.13).
[12:41:08] + News From Folding@Home: Welcome to Folding@Home
[12:41:08] Loaded queue successfully.
[12:41:09] + Could not connect to Work Server
[12:41:09] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[12:41:31] + Attempting to get work packet
[12:41:31] - Connecting to assignment server
[12:41:32] - Successful: assigned to (171.67.108.13).
[12:41:32] + News From Folding@Home: Welcome to Folding@Home
[12:41:32] Loaded queue successfully.
[12:41:33] + Could not connect to Work Server
[12:41:33] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[12:42:16] + Attempting to get work packet
[12:42:16] - Connecting to assignment server
[12:42:17] - Successful: assigned to (171.64.65.65).
[12:42:17] + News From Folding@Home: Welcome to Folding@Home
[12:42:17] Loaded queue successfully.
[12:42:17] - Couldn't send HTTP request to server
[12:42:17]   (Got status 503)
[12:42:17] + Could not connect to Work Server
[12:42:17] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[12:43:39] + Attempting to get work packet
[12:43:39] - Connecting to assignment server
[12:43:39] - Successful: assigned to (171.64.65.65).
[12:43:39] + News From Folding@Home: Welcome to Folding@Home
[12:43:39] Loaded queue successfully.
[12:43:40] - Couldn't send HTTP request to server
[12:43:40]   (Got status 503)
[12:43:40] + Could not connect to Work Server
[12:43:40] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[12:46:25] + Attempting to get work packet
[12:46:25] - Connecting to assignment server
[12:46:26] - Successful: assigned to (171.64.65.65).
[12:46:26] + News From Folding@Home: Welcome to Folding@Home
[12:46:26] Loaded queue successfully.
[12:46:26] - Couldn't send HTTP request to server
[12:46:26]   (Got status 503)
[12:46:26] + Could not connect to Work Server
[12:46:26] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[12:51:59] + Attempting to get work packet
[12:51:59] - Connecting to assignment server
[12:52:00] - Successful: assigned to (171.64.122.139).
[12:52:00] + News From Folding@Home: Welcome to Folding@Home
[12:52:00] Loaded queue successfully.
[12:52:00] - Couldn't send HTTP request to server
[12:52:00] + Could not connect to Work Server
[12:52:00] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[13:02:46] + Attempting to get work packet
[13:02:46] - Connecting to assignment server
[13:02:47] - Successful: assigned to (171.64.122.139).
[13:02:47] + News From Folding@Home: Welcome to Folding@Home
[13:02:47] Loaded queue successfully.
[13:02:47] - Couldn't send HTTP request to server
[13:02:47] + Could not connect to Work Server
[13:02:47] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[13:24:19] + Attempting to get work packet
[13:24:19] - Connecting to assignment server
[13:24:20] - Successful: assigned to (171.64.65.65).
[13:24:20] + News From Folding@Home: Welcome to Folding@Home
[13:24:20] Loaded queue successfully.
[13:24:21] - Couldn't send HTTP request to server
[13:24:21]   (Got status 503)
[13:24:21] + Could not connect to Work Server
[13:24:21] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[14:07:01] + Attempting to get work packet
[14:07:01] - Connecting to assignment server
[14:07:04] - Successful: assigned to (171.67.108.13).
[14:07:04] + News From Folding@Home: Welcome to Folding@Home
[14:07:05] Loaded queue successfully.
[14:07:05] + Could not connect to Work Server
[14:07:05] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[14:55:08] + Attempting to get work packet
[14:55:08] - Connecting to assignment server
[14:55:09] - Successful: assigned to (171.64.122.139).
[14:55:09] + News From Folding@Home: Welcome to Folding@Home
[14:55:09] Loaded queue successfully.
[14:55:10] - Couldn't send HTTP request to server
[14:55:10] + Could not connect to Work Server
[14:55:10] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[15:43:10] + Attempting to get work packet
[15:43:10] - Connecting to assignment server
[15:43:11] - Successful: assigned to (171.64.122.139).
[15:43:11] + News From Folding@Home: Welcome to Folding@Home
[15:43:11] Loaded queue successfully.
[15:43:15] - Couldn't send HTTP request to server
[15:43:15] + Could not connect to Work Server
[15:43:15] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[16:31:19] + Attempting to get work packet
[16:31:19] - Connecting to assignment server
[16:31:23] - Successful: assigned to (171.64.122.139).
[16:31:23] + News From Folding@Home: Welcome to Folding@Home
[16:31:23] Loaded queue successfully.
[16:31:24] - Couldn't send HTTP request to server
[16:31:24] + Could not connect to Work Server
[16:31:24] - Attempt #14  to get work failed, and no other work to do.
Waiting before retry.
[17:19:39] + Attempting to get work packet
[17:19:39] - Connecting to assignment server
[17:19:42] - Successful: assigned to (171.67.108.13).
[17:19:42] + News From Folding@Home: Welcome to Folding@Home
[17:19:42] Loaded queue successfully.
[17:19:45] + Could not connect to Work Server
[17:19:45] - Attempt #15  to get work failed, and no other work to do.
Waiting before retry.
[18:07:48] + Attempting to get work packet
[18:07:48] - Connecting to assignment server
[18:08:11] - Successful: assigned to (171.64.65.65).
[18:08:11] + News From Folding@Home: Welcome to Folding@Home
[18:08:11] Loaded queue successfully.
[18:08:15] - Couldn't send HTTP request to server
[18:08:15]   (Got status 503)
[18:08:15] + Could not connect to Work Server
[18:08:15] - Attempt #16  to get work failed, and no other work to do.
Waiting before retry.
[18:56:18] + Attempting to get work packet
[18:56:18] - Connecting to assignment server
[18:56:19] - Successful: assigned to (130.49.240.81).
[18:56:19] + News From Folding@Home: Welcome to Folding@Home
[18:56:19] Loaded queue successfully.
[18:56:23] + Could not connect to Work Server
[18:56:23] - Attempt #17  to get work failed, and no other work to do.
Waiting before retry.
[19:44:29] + Attempting to get work packet
[19:44:29] - Connecting to assignment server
[19:44:31] - Successful: assigned to (171.64.65.65).
[19:44:31] + News From Folding@Home: Welcome to Folding@Home
[19:44:31] Loaded queue successfully.
[19:44:32] - Couldn't send HTTP request to server
[19:44:32]   (Got status 503)
[19:44:32] + Could not connect to Work Server
[19:44:32] - Attempt #18  to get work failed, and no other work to do.
Waiting before retry.
[20:32:44] + Attempting to get work packet
[20:32:44] - Connecting to assignment server
[20:32:48] - Successful: assigned to (171.64.65.65).
[20:32:48] + News From Folding@Home: Welcome to Folding@Home
[20:32:48] Loaded queue successfully.
[20:32:48] - Couldn't send HTTP request to server
[20:32:48]   (Got status 503)
[20:32:48] + Could not connect to Work Server
[20:32:48] - Attempt #19  to get work failed, and no other work to do.
Waiting before retry.

???

there's no -advmethods switch??
the server ip is sometimes switching but it seems like there's no work for this type of client today??

Posted: **Mon Apr 20, 2009 10:57 pm**

Actually there were 10000 WU on the 171.64.122.139 server earlier. Try stopping the client and setting the -advmethods switch again.

Posted: **Tue Apr 21, 2009 3:22 pm**

I cannot connect to get a WU from this server either

[14:55:33] + Attempting to get work packet
[14:55:33] - Connecting to assignment server
[14:55:54] - Couldn't send HTTP request to server
[14:55:54] + Could not connect to Assignment Server
[14:55:55] - Successful: assigned to (171.67.108.13).
[14:55:55] + News From Folding@Home: Welcome to Folding@Home
[14:55:55] Loaded queue successfully.
[14:55:56] - Couldn't send HTTP request to server
[14:55:56] + Could not connect to Work Server
[14:55:56] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[15:01:26] + Attempting to get work packet
[15:01:26] - Connecting to assignment server
[15:01:47] - Couldn't send HTTP request to server
[15:01:47] + Could not connect to Assignment Server
[15:01:47] - Successful: assigned to (171.67.108.13).
[15:01:47] + News From Folding@Home: Welcome to Folding@Home
[15:01:47] Loaded queue successfully.
[15:01:48] - Couldn't send HTTP request to server
[15:01:48] + Could not connect to Work Server
[15:01:48] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.

It's been like this for 24 hours now and when I try connecting direct to http://171.67.108.13 I get unable to connect error from my browser too.

Posted: **Tue Apr 21, 2009 3:30 pm**

No body posted in this thread, but Pande Group is aware of the issue with this server too.

Posted: **Wed Apr 22, 2009 8:37 pm**

Thanks for the heads up. I was going to post in this thread regarding the 10 day old completed WU that won't upload to this server:

Code: Select all

[19:53:14] Trying to send all finished work units
[19:53:14] Project: 4458 (Run 512, Clone 0, Gen 13)


[19:53:14] + Attempting to send results [April 22 19:53:14 UTC]
[19:53:14] - Detect CPU. Vendor: GenuineIntel, Family: 15, Model: 2, Stepping: 9
[19:53:14] - Reading file work/wuresults_06.dat from core
[19:53:14]   (Read 208092 bytes from disk)
[19:53:14] Connecting to http://171.67.108.13:8080/
[19:53:14] - Connecting to assignment server
[19:53:14] Connecting to http://assign.stanford.edu:8080/
[19:53:14] Posted data.
[19:53:14] Initial: E6A9; - Successful: assigned to (169.230.26.30).
[19:53:14] + News From Folding@Home: Welcome to Folding@Home
[19:53:15] Loaded queue successfully.
[19:53:15] Connecting to http://169.230.26.30:8080/
[19:53:15] Posted data.
[19:53:15] Posted data.
[19:53:15] Initial: 0000; - Receiving payload (expected size: 21198)
[19:53:15] + Could not get Work unit data from Work Server
[19:53:15] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[19:53:16] Initial: 0000; + Could not connect to Work Server (results)
[19:53:16]     (171.67.108.13:8080)
[19:53:16] + Retrying using alternative port
[19:53:16] Connecting to http://171.67.108.13:80/
[19:53:17] - Couldn't send HTTP request to server
[19:53:17] + Could not connect to Work Server (results)
[19:53:17]     (171.67.108.13:80)
[19:53:17] - Error: Could not transmit unit 06 (completed April 12) to work server.
[19:53:17] - 74 failed uploads of this unit.

Meanwhile, as previously described in detail in a different thread, mere seconds apart other completed WUs from this same server were sent back successfully.

Posted: **Fri Apr 24, 2009 4:00 am**

Currently at 81 attempts (11 days). I posted about this in the server forum, but haven't received a response. Oddly, the same IP address that continues to fail to accept the completed WU was used today to download a WU while Firefox continues to return:

"Problem loading page: Unable to connect. Firefox can't establish a connection to the server at 171.67.108.13"

Doesn't make any sense.

Posted: **Fri Apr 24, 2009 7:39 pm**

Tynat wrote:Currently at 81 attempts (11 days). I posted about this in the server forum, but haven't received a response. Oddly, the same IP address that continues to fail to accept the completed WU was used today to download a WU while Firefox continues to return:

"Problem loading page: Unable to connect. Firefox can't establish a connection to the server at 171.67.108.13"

Doesn't make any sense.

At the top of this page you'll find a link "Server status" which takes you to http://fah-web.stanford.edu/serverstat.html if you look on that page, you'll see that server 171.67.108.13 says Reject in the Connections column so there is clearly something wrong with the server.

According to the history of that server, it was in full operation until Thu Apr 23 13:50:20 (23 hours ago) at which time it went DOWN. At 08:15:20 it was brought back up but since then it has not been accepting connections. [All times are Stanford server times = UTC-7.] Obviously somebody is working on it and they'll probably give us a progress report when there is something to report.

I can't say anything about the 10 days prior to the past 24 hours. I can only see a small portion of that period, but everything I can see appears normal -- and I do not see any other complaints for that 10 day period.

This server is for the GPU client and you're posting in a forum for the CPU (uniprocessor) client. I'll move this thread to the right forum.

Posted: **Sat Apr 25, 2009 9:14 am**

bruce wrote:
Tynat wrote:Currently at 81 attempts (11 days). I posted about this in the server forum, but haven't received a response. Oddly, the same IP address that continues to fail to accept the completed WU was used today to download a WU while Firefox continues to return:

"Problem loading page: Unable to connect. Firefox can't establish a connection to the server at 171.67.108.13"

Doesn't make any sense.
At the top of this page you'll find a link "Server status" which takes you to http://fah-web.stanford.edu/serverstat.html if you look on that page, you'll see that server 171.67.108.13 says Reject in the Connections column so there is clearly something wrong with the server.

At the time you wrote that, the server was down. However, I feel that this is irrelevant to the issue at hand, since the server going down is a more recent occurrence. As I mentioned HERE, this same server has been sending and receiving other WUs just fine. More to the point, now that the server is up and running again, the stuck completed WU now stands at 86 attempts (13 days).

bruce wrote:According to the history of that server, it was in full operation until Thu Apr 23 13:50:20 (23 hours ago) at which time it went DOWN. At 08:15:20 it was brought back up but since then it has not been accepting connections. [All times are Stanford server times = UTC-7.] Obviously somebody is working on it and they'll probably give us a progress report when there is something to report.

It's up, no progress report.

bruce wrote:I can't say anything about the 10 days prior to the past 24 hours. I can only see a small portion of that period, but everything I can see appears normal -- and I do not see any other complaints for that 10 day period.

The logs currently go back to April 17th. Between April 17th and April 23rd there was a total of 2 rejects. Even though the log doesn't account for the 5 days before April 17th, the 6 days it does account for should have provided ample time for the stuck completed WU to be accepted back to the fold.

I have seen other posters complain about their stuck completed WUs. Grant it, it's not the same server, but others are posting about it and some have chosen to leave FAH. Besides, not everyone who folds posts problems in the forum. It is but a small sample of the total clients. And, even if it is not a systemic problem, it's still a WU whose life support system is failing and it is beyond my ability to correct the situation.

bruce wrote:This server is for the GPU client and you're posting in a forum for the CPU (uniprocessor) client. I'll move this thread to the right forum.

What the h...? The stuck completed WU is for the GPU console client? Someone else had this same problem.

I posted in the 'Windows v6.23 Uniprocessor Client' forum because on April 12th, when this all began, I hadn't even installed the GPU console client. Maybe this explains why the console client, that downloaded and completed the WU, can't send the completed WU back?

How does one go about sending back a completed WU that the console client shouldn't have downloaded in the first place?

Posted: **Sat Apr 25, 2009 10:41 pm**

Tynat wrote:
bruce wrote:This server is for the GPU client and you're posting in a forum for the CPU (uniprocessor) client. I'll move this thread to the right forum.
What the h...? The stuck completed WU is for the GPU console client? Someone else had this same problem.

Yes, someone else had the same problem DURING THE TIME THAT THE SERVER WAS DOWN. As you've already said that is irrelevant because you have demonstrated that you cannot upload when the server is in full operation.

I posted in the 'Windows v6.23 Uniprocessor Client' forum because on April 12th, when this all began, I hadn't even installed the GPU console client. Maybe this explains why the console client, that downloaded and completed the WU, can't send the completed WU back?

OK, so what you're saying is that the CPU client cannot upload to a server that distributes uniprocessor projects AND the GPU client cannot upload to a server that distributes GPU projects. The post that I moved only talked about the latter.

How does one go about sending back a completed WU that the console client shouldn't have downloaded in the first place?

Well, did the client complete the WU or not? If the client did complete the WU, then I don't understand why you think it sent you the wrong type of WU. If it didn't complete the WU, there is nothing to upload except maybe an EUE that says you didn't have the proper hardware to work on the WU. In that case, the WU can simply be deleted.

OK first let's talk about server 171.67.108.13. After my previous post, the server was restarted. Since then it has been accepting uploads at a rate of 400-600 per hour except for the first couple hours after it came back up when it was accepting 1100-1200 per hour. (Yes, there was a backlog.) I think it's fair to discount the possiblity that your problem is based on something that's wrong at the server -- but rather something at your end of the wire.

That is supported by your report that you have WUs which are not uploading to more than one server.

First, disable your security software. Then restart the client(s) which have WUs to be uploaded. If they upload successfully, your anti-spyware software was blocking the FAH client from uploading. Re-enable your security software and then figure out how to configure your software to give FAH permission to connect to the internet. If they do not upload, post that segment of FAHlog.

Folding Forum

171.67.108.13 - cannot connect

Re: 171.67.108.13

Re: 171.67.108.13 - cannot connect

Re: 171.67.108.13 - cannot connect

Re: 171.67.108.13 - cannot connect

Re: 171.67.108.13 - cannot connect

Re: 171.67.108.13 - cannot connect

Re: 171.67.108.13 - cannot connect

Re: 171.67.108.13 - cannot connect

Re: 171.67.108.13 - cannot connect

Re: It sure would be nice to be able to contribute

171.67.108.13

Re: 171.67.108.13

Re: 171.67.108.13