unable to get wu from 171.67.108.33

Moderators: Site Moderators, FAHC Science Team

MJandDave
Posts: 24
Joined: Wed Sep 01, 2010 1:36 am

Re: unable to get wu from 171.67.108.33

Post by MJandDave »

More problems today.

Code: Select all

[18:11:44] Writing local files
[18:11:44] Completed 250000 out of 250000 steps  (100%)
[18:11:44] Writing final coordinates.
[18:11:45] Past main M.D. loop
[18:12:45] 
[18:12:45] Finished Work Unit:
[18:12:45] - Reading up to 293304 from "work/wudata_02.arc": Read 293304
[18:12:45] - Reading up to 260952 from "work/wudata_02.xtc": Read 260952
[18:12:45] goefile size: 0
[18:12:45] logfile size: 22139
[18:12:45] Leaving Run
[18:12:48] - Writing 582303 bytes of core data to disk...
[18:12:48] Done: 581791 -> 560312 (compressed to 96.3 percent)
[18:12:48]   ... Done.
[18:12:48] - Shutting down core
[18:12:48] 
[18:12:48] Folding@home Core Shutdown: FINISHED_UNIT
[18:12:51] CoreStatus = 64 (100)
[18:12:51] Sending work to server
[18:12:51] Project: 11268 (Run 9, Clone 766, Gen 9)


[18:12:51] + Attempting to send results [December 24 18:12:51 UTC]
[18:13:06] + Results successfully sent
[18:13:06] Thank you for your contribution to Folding@Home.
[18:13:06] + Number of Units Completed: 12

[18:13:11] - Preparing to get new work unit...
[18:13:11] + Attempting to get work packet
[18:13:11] - Connecting to assignment server
[18:13:16] - Successful: assigned to (171.67.108.33).
[18:13:16] + News From Folding@Home: Welcome to Folding@Home
[18:13:16] Loaded queue successfully.
[18:13:19] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:13:28] + Attempting to get work packet
[18:13:28] - Connecting to assignment server
[18:13:31] - Successful: assigned to (171.67.108.33).
[18:13:31] + News From Folding@Home: Welcome to Folding@Home
[18:13:31] Loaded queue successfully.
[18:13:33] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:13:45] + Attempting to get work packet
[18:13:45] - Connecting to assignment server
[18:13:49] - Successful: assigned to (171.67.108.33).
[18:13:49] + News From Folding@Home: Welcome to Folding@Home
[18:13:50] Loaded queue successfully.
[18:13:57] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:14:27] + Attempting to get work packet
[18:14:27] - Connecting to assignment server
[18:14:28] - Successful: assigned to (171.67.108.33).
[18:14:28] + News From Folding@Home: Welcome to Folding@Home
[18:14:28] Loaded queue successfully.
[18:14:29] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:15:12] + Attempting to get work packet
[18:15:12] - Connecting to assignment server
[18:15:16] - Successful: assigned to (171.67.108.33).
[18:15:16] + News From Folding@Home: Welcome to Folding@Home
[18:15:16] Loaded queue successfully.
[18:15:19] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[18:16:50] + Attempting to get work packet
[18:16:50] - Connecting to assignment server
[18:16:56] - Successful: assigned to (171.67.108.33).
[18:16:56] + News From Folding@Home: Welcome to Folding@Home
[18:16:56] Loaded queue successfully.
[18:16:59] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[18:19:53] + Attempting to get work packet
[18:19:53] - Connecting to assignment server
[18:19:55] - Successful: assigned to (171.67.108.33).
[18:19:55] + News From Folding@Home: Welcome to Folding@Home
[18:19:55] Loaded queue successfully.
[18:19:56] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[18:25:26] + Attempting to get work packet
[18:25:26] - Connecting to assignment server
[18:25:30] - Successful: assigned to (171.67.108.33).
[18:25:30] + News From Folding@Home: Welcome to Folding@Home
[18:25:30] Loaded queue successfully.
[18:25:32] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.

Folding@Home Client Shutdown.


--- Opening Log file [December 24 18:30:41 UTC] 


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

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

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

Launch directory: C:\FAH
Executable: C:\FAH\fah6.exe


[18:30:41] - Ask before connecting: No
[18:30:41] - User name: MJFolding (Team 191497)
[18:30:41] - User ID: 31E193D61A304AB8
[18:30:41] - Machine ID: 1
[18:30:41] 
[18:30:41] Loaded queue successfully.
[18:30:41] - Preparing to get new work unit...
[18:30:41] + Attempting to get work packet
[18:30:41] - Connecting to assignment server
[18:30:43] - Successful: assigned to (171.67.108.33).
[18:30:43] + News From Folding@Home: Welcome to Folding@Home
[18:30:43] Loaded queue successfully.
[18:30:44] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:30:59] + Attempting to get work packet
[18:30:59] - Connecting to assignment server
[18:31:01] - Successful: assigned to (171.67.108.33).
[18:31:01] + News From Folding@Home: Welcome to Folding@Home
[18:31:01] Loaded queue successfully.
[18:31:01] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:31:17] + Attempting to get work packet
[18:31:17] - Connecting to assignment server
[18:31:19] - Successful: assigned to (171.67.108.33).
[18:31:19] + News From Folding@Home: Welcome to Folding@Home
[18:31:19] Loaded queue successfully.
[18:31:20] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:31:50] + Attempting to get work packet
[18:31:50] - Connecting to assignment server
[18:31:52] - Successful: assigned to (171.67.108.33).
[18:31:52] + News From Folding@Home: Welcome to Folding@Home
[18:31:52] Loaded queue successfully.
[18:31:53] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:32:40] + Attempting to get work packet
[18:32:40] - Connecting to assignment server
[18:32:42] - Successful: assigned to (171.67.108.33).
[18:32:42] + News From Folding@Home: Welcome to Folding@Home
[18:32:42] Loaded queue successfully.
[18:32:43] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[18:34:12] + Attempting to get work packet
[18:34:12] - Connecting to assignment server
[18:34:15] - Successful: assigned to (171.67.108.33).
[18:34:15] + News From Folding@Home: Welcome to Folding@Home
[18:34:16] Loaded queue successfully.
[18:34:20] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[18:37:10] + Attempting to get work packet
[18:37:10] - Connecting to assignment server
[18:37:12] - Successful: assigned to (171.67.108.33).
[18:37:12] + News From Folding@Home: Welcome to Folding@Home
[18:37:12] Loaded queue successfully.
[18:37:13] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
noprob
Posts: 31
Joined: Sun Mar 09, 2008 2:48 am
Hardware configuration: borgs
Location: mountains of West Virginia U.S.of A.
Contact:

Re: unable to get wu from 171.67.108.33

Post by noprob »

after many hours it seems to be doing ok now.
finally found a different server. :D

Code: Select all

--- Opening Log file [December 24 18:17:26 UTC] 


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

                       Folding@Home Client Version 6.30

                          http://folding.stanford.edu

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

Launch directory: E:\Folding@home-CPU1
Service: E:\Folding@home-CPU1\Folding@home-Win32-x86.exe
Arguments: -svcstart -d E:\Folding@home-CPU1 -verbosity 9 

Launched as a service.
Entered E:\Folding@home-CPU1 to do work.

[18:17:26] - Ask before connecting: No
[18:17:26] - User name: noprob (Team 12072)
[18:17:26] - User ID: back spaced
[18:17:26] - Machine ID: 1
[18:17:26] 
[18:17:26] Loaded queue successfully.
[18:17:26] - Preparing to get new work unit...
[18:17:26] Cleaning up work directory
[18:17:26] - Autosending finished units... [18:17:26]
[18:17:26] Trying to send all finished work units
[18:17:26] + No unsent completed units remaining.
[18:17:26] - Autosend completed
[18:17:26] + Attempting to get work packet
[18:17:26] Passkey found
[18:17:26] - Will indicate memory of 1023 MB
[18:17:26] - Detect CPU. Vendor: AuthenticAMD, Family: 15, Model: 3, Stepping: 2
[18:17:26] - Connecting to assignment server
[18:17:26] Connecting to http://assign.stanford.edu:8080/
[18:17:27] Posted data.
[18:17:27] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:17:27] + News From Folding@Home: Welcome to Folding@Home
[18:17:27] Loaded queue successfully.
[18:17:27] Sent data
[18:17:27] Connecting to http://171.67.108.33:8080/
[18:17:27] Posted data.
[18:17:27] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:17:27] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:17:40] + Attempting to get work packet
[18:17:40] Passkey found
[18:17:40] - Will indicate memory of 1023 MB
[18:17:40] - Connecting to assignment server
[18:17:40] Connecting to http://assign.stanford.edu:8080/
[18:17:41] Posted data.
[18:17:41] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:17:41] + News From Folding@Home: Welcome to Folding@Home
[18:17:41] Loaded queue successfully.
[18:17:41] Sent data
[18:17:41] Connecting to http://171.67.108.33:8080/
[18:17:41] Posted data.
[18:17:41] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:17:41] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:18:00] + Attempting to get work packet
[18:18:00] Passkey found
[18:18:00] - Will indicate memory of 1023 MB
[18:18:00] - Connecting to assignment server
[18:18:00] Connecting to http://assign.stanford.edu:8080/
[18:18:00] Posted data.
[18:18:00] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:18:01] + News From Folding@Home: Welcome to Folding@Home
[18:18:01] Loaded queue successfully.
[18:18:01] Sent data
[18:18:01] Connecting to http://171.67.108.33:8080/
[18:18:01] Posted data.
[18:18:01] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:18:01] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:18:22] + Attempting to get work packet
[18:18:22] Passkey found
[18:18:22] - Will indicate memory of 1023 MB
[18:18:22] - Connecting to assignment server
[18:18:22] Connecting to http://assign.stanford.edu:8080/
[18:18:23] Posted data.
[18:18:23] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:18:23] + News From Folding@Home: Welcome to Folding@Home
[18:18:23] Loaded queue successfully.
[18:18:23] Sent data
[18:18:23] Connecting to http://171.67.108.33:8080/
[18:18:24] Posted data.
[18:18:24] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:18:24] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:19:12] + Attempting to get work packet
[18:19:12] Passkey found
[18:19:12] - Will indicate memory of 1023 MB
[18:19:12] - Connecting to assignment server
[18:19:12] Connecting to http://assign.stanford.edu:8080/
[18:19:13] Posted data.
[18:19:13] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:19:13] + News From Folding@Home: Welcome to Folding@Home
[18:19:13] Loaded queue successfully.
[18:19:13] Sent data
[18:19:13] Connecting to http://171.67.108.33:8080/
[18:19:14] Posted data.
[18:19:14] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:19:14] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[18:20:34] + Attempting to get work packet
[18:20:34] Passkey found
[18:20:34] - Will indicate memory of 1023 MB
[18:20:34] - Connecting to assignment server
[18:20:34] Connecting to http://assign.stanford.edu:8080/
[18:20:35] Posted data.
[18:20:35] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:20:35] + News From Folding@Home: Welcome to Folding@Home
[18:20:35] Loaded queue successfully.
[18:20:35] Sent data
[18:20:35] Connecting to http://171.67.108.33:8080/
[18:20:35] Posted data.
[18:20:35] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:20:35] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[18:23:21] + Attempting to get work packet
[18:23:21] Passkey found
[18:23:21] - Will indicate memory of 1023 MB
[18:23:21] - Connecting to assignment server
[18:23:21] Connecting to http://assign.stanford.edu:8080/
[18:23:22] Posted data.
[18:23:22] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:23:22] + News From Folding@Home: Welcome to Folding@Home
[18:23:22] Loaded queue successfully.
[18:23:22] Sent data
[18:23:22] Connecting to http://171.67.108.33:8080/
[18:23:22] Posted data.
[18:23:22] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:23:22] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[18:28:57] + Attempting to get work packet
[18:28:57] Passkey found
[18:28:57] - Will indicate memory of 1023 MB
[18:28:57] - Connecting to assignment server
[18:28:57] Connecting to http://assign.stanford.edu:8080/
[18:28:57] Posted data.
[18:28:57] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:28:57] + News From Folding@Home: Welcome to Folding@Home
[18:28:58] Loaded queue successfully.
[18:28:58] Sent data
[18:28:58] Connecting to http://171.67.108.33:8080/
[18:28:58] Posted data.
[18:28:58] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:28:58] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[18:39:41] + Attempting to get work packet
[18:39:41] Passkey found
[18:39:41] - Will indicate memory of 1023 MB
[18:39:41] - Connecting to assignment server
[18:39:41] Connecting to http://assign.stanford.edu:8080/
[18:39:42] Posted data.
[18:39:42] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[18:39:42] + News From Folding@Home: Welcome to Folding@Home
[18:39:42] Loaded queue successfully.
[18:39:42] Sent data
[18:39:42] Connecting to http://171.67.108.33:8080/
[18:39:43] Posted data.
[18:39:43] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:39:43] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[19:01:15] + Attempting to get work packet
[19:01:15] Passkey found
[19:01:15] - Will indicate memory of 1023 MB
[19:01:15] - Connecting to assignment server
[19:01:15] Connecting to http://assign.stanford.edu:8080/
[19:01:15] Posted data.
[19:01:15] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[19:01:15] + News From Folding@Home: Welcome to Folding@Home
[19:01:15] Loaded queue successfully.
[19:01:15] Sent data
[19:01:15] Connecting to http://171.67.108.33:8080/
[19:01:16] Posted data.
[19:01:16] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[19:01:16] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[19:44:04] + Attempting to get work packet
[19:44:04] Passkey found
[19:44:04] - Will indicate memory of 1023 MB
[19:44:04] - Connecting to assignment server
[19:44:04] Connecting to http://assign.stanford.edu:8080/
[19:44:04] Posted data.
[19:44:04] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[19:44:04] + News From Folding@Home: Welcome to Folding@Home
[19:44:05] Loaded queue successfully.
[19:44:05] Sent data
[19:44:05] Connecting to http://171.67.108.33:8080/
[19:44:05] Posted data.
[19:44:05] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[19:44:05] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[20:32:11] + Attempting to get work packet
[20:32:11] Passkey found
[20:32:11] - Will indicate memory of 1023 MB
[20:32:11] - Connecting to assignment server
[20:32:11] Connecting to http://assign.stanford.edu:8080/
[20:32:12] Posted data.
[20:32:12] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[20:32:12] + News From Folding@Home: Welcome to Folding@Home
[20:32:12] Loaded queue successfully.
[20:32:12] Sent data
[20:32:12] Connecting to http://171.67.108.33:8080/
[20:32:13] Posted data.
[20:32:13] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[20:32:13] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[21:20:20] + Attempting to get work packet
[21:20:20] Passkey found
[21:20:20] - Will indicate memory of 1023 MB
[21:20:20] - Connecting to assignment server
[21:20:20] Connecting to http://assign.stanford.edu:8080/
[21:20:21] Posted data.
[21:20:21] Initial: 40AB; - Successful: assigned to (171.64.65.79).
[21:20:21] + News From Folding@Home: Welcome to Folding@Home
[21:20:21] Loaded queue successfully.
[21:20:21] Sent data
[21:20:21] Connecting to http://171.64.65.79:8080/
[21:20:22] Posted data.
[21:20:22] Initial: 0000; - Receiving payload (expected size: 255826)
[21:20:26] - Downloaded at ~62 kB/s
[21:20:26] - Averaged speed for that direction ~71 kB/s
[21:20:26] + Received work.
[21:20:26] + Closed connections
[21:20:26] 
[21:20:26] + Processing work unit
[21:20:26] Core required: FahCore_a4.exe
[21:20:26] Core found.
[21:20:26] Working on queue slot 07 [December 24 21:20:26 UTC]
[21:20:26] + Working ...
[21:20:26] - Calling '.\FahCore_a4.exe -dir work/ -suffix 07 -nice 19 -checkpoint 20 -service -verbose -lifeline 1320 -version 630'

[21:20:26] 
[21:20:26] *------------------------------*
[21:20:26] Folding@Home Gromacs GB Core
[21:20:26] Version 2.25 (Sept. 16, 2010)
[21:20:26] 
[21:20:26] Preparing to commence simulation
[21:20:26] - Looking at optimizations...
[21:20:26] - Created dyn
[21:20:26] - Files status OK
[21:20:27] - Expanded 255314 -> 397584 (decompressed 155.7 percent)
[21:20:27] Called DecompressByteArray: compressed_data_size=255314 data_size=397584, decompressed_data_size=397584 diff=0
[21:20:27] - Digital signature verified
[21:20:27] 
[21:20:27] Project: 10424 (Run 3239, Clone 0, Gen 7)
[21:20:27] 
[21:20:27] Assembly optimizations on if available.
[21:20:27] Entering M.D.
[21:20:33] Completed 0 out of 2000000 steps  (0%)
[21:46:31] Completed 20000 out of 2000000 steps  (1%)
[22:13:13] Completed 40000 out of 2000000 steps  (2%)
Image
codysluder
Posts: 1024
Joined: Sun Dec 02, 2007 12:43 pm

Re: unable to get wu from 171.67.108.33

Post by codysluder »

The Assignment process depends a lot on which servers are functional and which ones have WUs for your client.

It very likely works like this: The status of the servers is only updated periodically (maybe every 10 or 20 minutes, I don't know). If the status changes (say the server runs out of WUs) during that period, the assignment server still uses the old status so it keeps sending everyone there. Whether you are assigned the same server 5 or 15 times depends on how frequently you retry and how long it takes for the server status to be refreshed.
brityank
Posts: 161
Joined: Wed Dec 05, 2007 9:16 pm
Location: SE Pennsylvania

Re: unable to get wu from 171.67.108.33

Post by brityank »

codysluder wrote:The Assignment process depends a lot on which servers are functional and which ones have WUs for your client.

It very likely works like this: The status of the servers is only updated periodically (maybe every 10 or 20 minutes, I don't know). If the status changes (say the server runs out of WUs) during that period, the assignment server still uses the old status so it keeps sending everyone there. Whether you are assigned the same server 5 or 15 times depends on how frequently you retry and how long it takes for the server status to be refreshed.
See this thread for info: viewtopic.php?f=18&t=17133

I've had at least a half dozen different servers assigned for WUs over the past few months, so I doubt that it's a lack of WUs each time. The Retry is set by the Client, and steps up to 48-49 minutes between retries.

Thanks for the help.
... ... Free Republic Folders - A Tribute to Ronald Reagan ... ...
Image
baz657
Posts: 55
Joined: Thu Nov 12, 2009 1:40 pm
Hardware configuration: Win 7 Ultimate x64, 2 X Nvidia Fermi cards, one 2 Core CPU and one quad and one very old laptop
Location: Chesterfield, UK
Contact:

Re: unable to get wu from 171.67.108.33

Post by baz657 »

Code: Select all

[16:47:01] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[16:47:01] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[16:57:52] + Attempting to get work packet
[16:57:52] - Will indicate memory of 4094 MB
[16:57:52] - Connecting to assignment server
[16:57:52] Connecting to http://assign.stanford.edu:8080/
[16:57:53] Posted data.
[16:57:53] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[16:57:53] + News From Folding@Home: Welcome to Folding@Home
[16:57:53] Loaded queue successfully.
[16:57:53] Connecting to http://171.67.108.33:8080/
[16:57:54] Posted data.
[16:57:54] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[16:57:54] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[17:19:17] + Attempting to get work packet
[17:19:17] - Will indicate memory of 4094 MB
[17:19:17] - Connecting to assignment server
[17:19:17] Connecting to http://assign.stanford.edu:8080/
[17:19:18] Posted data.
[17:19:18] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[17:19:18] + News From Folding@Home: Welcome to Folding@Home
[17:19:19] Loaded queue successfully.
[17:19:19] Connecting to http://171.67.108.33:8080/
[17:19:20] Posted data.
[17:19:20] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[17:19:20] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
This has been happening to a couple of clients for the past hour or so

*Edit* One running again after client restarts
gwildperson
Posts: 450
Joined: Tue Dec 04, 2007 8:36 pm

Re: unable to get wu from 171.67.108.33

Post by gwildperson »

brityank wrote:I've had at least a half dozen different servers assigned for WUs over the past few months, so I doubt that it's a lack of WUs each time. The Retry is set by the Client, and steps up to 48-49 minutes between retries.
The Retry interval varies considerably. My client often fails to download on the first try but succeeds on the second. (My ISP probably sets up the connection too slowly but caches some information that is useful the second time.) Initially it tries to download very quickly. If it continues to fail, though, the time between retries gets longer and longer.
cybertimber2009
Posts: 7
Joined: Wed Dec 29, 2010 3:25 am

Re: unable to get wu from 171.67.108.33

Post by cybertimber2009 »

baz657 wrote:

Code: Select all

[16:47:01] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[16:47:01] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[16:57:52] + Attempting to get work packet
[16:57:52] - Will indicate memory of 4094 MB
[16:57:52] - Connecting to assignment server
[16:57:52] Connecting to http://assign.stanford.edu:8080/
[16:57:53] Posted data.
[16:57:53] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[16:57:53] + News From Folding@Home: Welcome to Folding@Home
[16:57:53] Loaded queue successfully.
[16:57:53] Connecting to http://171.67.108.33:8080/
[16:57:54] Posted data.
[16:57:54] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[16:57:54] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[17:19:17] + Attempting to get work packet
[17:19:17] - Will indicate memory of 4094 MB
[17:19:17] - Connecting to assignment server
[17:19:17] Connecting to http://assign.stanford.edu:8080/
[17:19:18] Posted data.
[17:19:18] Initial: 43AB; - Successful: assigned to (171.67.108.33).
[17:19:18] + News From Folding@Home: Welcome to Folding@Home
[17:19:19] Loaded queue successfully.
[17:19:19] Connecting to http://171.67.108.33:8080/
[17:19:20] Posted data.
[17:19:20] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[17:19:20] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
This has been happening to a couple of clients for the past hour or so

*Edit* One running again after client restarts
Same server (well, one of two).

Code: Select all

[13:04:51] + Attempting to send results [December 30 13:04:51 UTC]
[13:04:53] - Couldn't send HTTP request to server
[13:04:53] + Could not connect to Work Server (results)
[13:04:53]     (171.67.108.33:8080)
[13:04:53] + Retrying using alternative port
[13:05:04] + Results successfully sent
[13:05:04] Thank you for your contribution to Folding@Home.
[13:05:04] + Number of Units Completed: 11

[13:05:08] - Preparing to get new work unit...
[13:05:08] + Attempting to get work packet
[13:05:08] - Connecting to assignment server
[13:05:10] - Successful: assigned to (171.67.108.33).
[13:05:10] + News From Folding@Home: Welcome to Folding@Home
[13:05:10] Loaded queue successfully.
[13:05:13] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[13:05:22] + Attempting to get work packet
[13:05:22] - Connecting to assignment server
[13:05:23] - Successful: assigned to (171.67.108.33).
[13:05:23] + News From Folding@Home: Welcome to Folding@Home
[13:05:23] Loaded queue successfully.
[13:05:23] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[13:05:41] + Attempting to get work packet
[13:05:41] - Connecting to assignment server
[13:05:42] - Successful: assigned to (171.67.108.33).
[13:05:42] + News From Folding@Home: Welcome to Folding@Home
[13:05:42] Loaded queue successfully.
[13:05:43] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[13:06:13] + Attempting to get work packet
[13:06:13] - Connecting to assignment server
[13:06:14] - Successful: assigned to (171.67.108.33).
[13:06:14] + News From Folding@Home: Welcome to Folding@Home
[13:06:14] Loaded queue successfully.
[13:06:15] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[13:06:56] + Attempting to get work packet
[13:06:56] - Connecting to assignment server
[13:06:57] - Successful: assigned to (171.67.108.33).
[13:06:57] + News From Folding@Home: Welcome to Folding@Home
[13:06:58] Loaded queue successfully.
[13:07:01] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[13:08:32] + Attempting to get work packet
[13:08:32] - Connecting to assignment server
[13:08:33] - Successful: assigned to (171.67.108.33).
[13:08:33] + News From Folding@Home: Welcome to Folding@Home
[13:08:33] Loaded queue successfully.
[13:08:33] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[13:11:15] + Attempting to get work packet
[13:11:15] - Connecting to assignment server
[13:11:16] - Successful: assigned to (171.67.108.33).
[13:11:16] + News From Folding@Home: Welcome to Folding@Home
[13:11:17] Loaded queue successfully.
[13:11:20] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[13:16:46] + Attempting to get work packet
[13:16:46] - Connecting to assignment server
[13:16:47] - Successful: assigned to (171.67.108.33).
[13:16:47] + News From Folding@Home: Welcome to Folding@Home
[13:16:47] Loaded queue successfully.
[13:16:48] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[13:27:33] + Attempting to get work packet
[13:27:33] - Connecting to assignment server
[13:27:34] - Successful: assigned to (171.67.108.33).
[13:27:34] + News From Folding@Home: Welcome to Folding@Home
[13:27:34] Loaded queue successfully.
[13:27:37] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[13:48:59] + Attempting to get work packet
[13:48:59] - Connecting to assignment server
[13:49:00] - Successful: assigned to (171.67.108.33).
[13:49:00] + News From Folding@Home: Welcome to Folding@Home
[13:49:00] Loaded queue successfully.
[13:49:01] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[14:31:42] + Attempting to get work packet
[14:31:42] - Connecting to assignment server
[14:31:43] - Successful: assigned to (171.67.108.39).
[14:31:43] + News From Folding@Home: Welcome to Folding@Home
[14:31:43] Loaded queue successfully.
[14:31:43] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[15:19:50] + Attempting to get work packet
[15:19:50] - Connecting to assignment server
[15:19:51] - Successful: assigned to (171.67.108.33).
[15:19:51] + News From Folding@Home: Welcome to Folding@Home
[15:19:51] Loaded queue successfully.
[15:19:52] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[16:08:06] + Attempting to get work packet
[16:08:06] - Connecting to assignment server
[16:08:07] - Successful: assigned to (171.67.108.33).
[16:08:07] + News From Folding@Home: Welcome to Folding@Home
[16:08:07] Loaded queue successfully.
[16:08:59] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[16:57:06] + Attempting to get work packet
[16:57:06] - Connecting to assignment server
[16:57:07] - Successful: assigned to (171.64.65.84).
[16:57:07] + News From Folding@Home: Welcome to Folding@Home
[16:57:07] Loaded queue successfully.
[16:57:13] + Closed connections
[16:57:13] 
[16:57:13] + Processing work unit
[16:57:13] Core required: FahCore_a4.exe
[16:57:13] Core found.
[16:57:13] Working on queue slot 02 [December 30 16:57:13 UTC]
[16:57:13] + Working ...
Running now, no complaints really. My computer just chilled for awhile.
brityank
Posts: 161
Joined: Wed Dec 05, 2007 9:16 pm
Location: SE Pennsylvania

Re: unable to get wu from 171.67.108.33

Post by brityank »

gwildperson wrote:
brityank wrote:I've had at least a half dozen different servers assigned for WUs over the past few months, so I doubt that it's a lack of WUs each time. The Retry is set by the Client, and steps up to 48-49 minutes between retries.
The Retry interval varies considerably. My client often fails to download on the first try but succeeds on the second. (My ISP probably sets up the connection too slowly but caches some information that is useful the second time.) Initially it tries to download very quickly. If it continues to fail, though, the time between retries gets longer and longer.
I'm not sure of the timings, but the sequence is something like wait:xx.xx between re-requests to the Assignment server and getting sent to the WU server. That wait on my client was 18 seconds; 19 seconds; 25 seconds; 1 minute 2 seconds; 1 minute 33 seconds; - and increasing so by the tenth iteration is stable around the 48 minute mark retry getting resent to the same WU server.

Of all the errors I've had over the years, this
Initial: 0000; - Error: Bad packet type from server, expected work assignment
Attempt #XX to get work failed, and no other work to do.
Waiting before retry.
is the only server to post this specific Bad packet type error - all others are non-connects due to no WUs, or netload issues.

I would let it ride except there are several others in the threads that have posted the same error on this same server, and as we all know the folks that post here are a very minor portion of the community at large of F@H clients. A minor glitch that is a big frustration, and close-out/restart doesn't always jump to another server. As I recall from my Ver. 4 client, there was some type of counter on the Assignment Server that kept track of the number of times it had sent you to a WU server, and at (I believe) 4 it sent you to another instead. That no longer appears to be the case, but I wish it were put back in.

Thanks for your help. :)
... ... Free Republic Folders - A Tribute to Ronald Reagan ... ...
Image
Post Reply