171.64.65.64 - Proj 2653: numerous work units

Moderators: Site Moderators, FAHC Science Team

3dski
Posts: 13
Joined: Fri Aug 01, 2008 3:56 pm

171.64.65.64 - Proj 2653: numerous work units

Post by 3dski »

Not sure if this is the right place for this. I can't seem to get this project to upload:

Code: Select all

[19:18:04] + Attempting to send results [January 26 19:18:04 UTC]
[19:18:36] - Couldn't send HTTP request to server
[19:18:36] + Could not connect to Work Server (results)
[19:18:36]     (171.64.65.64:8080)
[19:18:36] + Retrying using alternative port
[19:18:57] - Couldn't send HTTP request to server
[19:18:57] + Could not connect to Work Server (results)
[19:18:57]     (171.64.65.64:80)
[19:18:57] - Error: Could not transmit unit 00 (completed January 24) to work server.


[19:18:57] + Attempting to send results [January 26 19:18:57 UTC]
[19:19:18] - Couldn't send HTTP request to server
[19:19:18] + Could not connect to Work Server (results)
[19:19:18]     (171.67.108.25:8080)
[19:19:18] + Retrying using alternative port
[19:19:39] - Couldn't send HTTP request to server
[19:19:39] + Could not connect to Work Server (results)
[19:19:39]     (171.67.108.25:80)
[19:19:39]   Could not transmit unit 00 to Collection server; keeping in queue.
[19:19:39] Project: 2653 (Run 1, Clone 20, Gen 108)


[19:19:39] + Attempting to send results [January 26 19:19:39 UTC]
[19:20:10] - Couldn't send HTTP request to server
[19:20:10] + Could not connect to Work Server (results)
[19:20:10]     (171.64.65.64:8080)
[19:20:10] + Retrying using alternative port
[19:20:31] - Couldn't send HTTP request to server
[19:20:31] + Could not connect to Work Server (results)
[19:20:31]     (171.64.65.64:80)
[19:20:31] - Error: Could not transmit unit 02 (completed January 26) to work server.


[19:20:31] + Attempting to send results [January 26 19:20:31 UTC]
[19:20:53] - Couldn't send HTTP request to server
[19:20:53] + Could not connect to Work Server (results)
[19:20:53]     (171.67.108.25:8080)
[19:20:53] + Retrying using alternative port
[19:21:14] - Couldn't send HTTP request to server
[19:21:14] + Could not connect to Work Server (results)
[19:21:14]     (171.67.108.25:80)
[19:21:14]   Could not transmit unit 02 to Collection server; keeping in queue.
[19:21:14] Project: 2653 (Run 1, Clone 27, Gen 108)


[19:21:14] + Attempting to send results [January 26 19:21:14 UTC]
[19:21:44] - Couldn't send HTTP request to server
[19:21:44] + Could not connect to Work Server (results)
[19:21:44]     (171.64.65.64:8080)
[19:21:44] + Retrying using alternative port
[19:22:05] - Couldn't send HTTP request to server
[19:22:05] + Could not connect to Work Server (results)
[19:22:05]     (171.64.65.64:80)
[19:22:05] - Error: Could not transmit unit 03 (completed January 26) to work server.


[19:22:05] + Attempting to send results [January 26 19:22:05 UTC]
[19:22:27] - Couldn't send HTTP request to server
[19:22:27] + Could not connect to Work Server (results)
[19:22:27]     (171.67.108.25:8080)
[19:22:27] + Retrying using alternative port
[19:22:48] - Couldn't send HTTP request to server
[19:22:48] + Could not connect to Work Server (results)
[19:22:48]     (171.67.108.25:80)
[19:22:48]   Could not transmit unit 03 to Collection server; keeping in queue.
[19:22:48] Project: 2653 (Run 1, Clone 36, Gen 108)


[19:22:48] + Attempting to send results [January 26 19:22:48 UTC]
[19:23:19] - Couldn't send HTTP request to server
[19:23:19] + Could not connect to Work Server (results)
[19:23:19]     (171.64.65.64:8080)
[19:23:19] + Retrying using alternative port
[19:23:40] - Couldn't send HTTP request to server
[19:23:40] + Could not connect to Work Server (results)
[19:23:40]     (171.64.65.64:80)
[19:23:40] - Error: Could not transmit unit 04 (completed January 26) to work server.


[19:23:40] + Attempting to send results [January 26 19:23:40 UTC]
[19:24:02] - Couldn't send HTTP request to server
[19:24:02] + Could not connect to Work Server (results)
[19:24:02]     (171.67.108.25:8080)
[19:24:02] + Retrying using alternative port
[19:24:23] - Couldn't send HTTP request to server
[19:24:23] + Could not connect to Work Server (results)
[19:24:23]     (171.67.108.25:80)
[19:24:23]   Could not transmit unit 04 to Collection server; keeping in queue.
[19:24:23] Project: 2653 (Run 1, Clone 45, Gen 108)


[19:24:23] + Attempting to send results [January 26 19:24:23 UTC]
[19:24:54] - Couldn't send HTTP request to server
[19:24:54] + Could not connect to Work Server (results)
[19:24:54]     (171.64.65.64:8080)
[19:24:54] + Retrying using alternative port
[19:25:15] - Couldn't send HTTP request to server
[19:25:15] + Could not connect to Work Server (results)
[19:25:15]     (171.64.65.64:80)
[19:25:15] - Error: Could not transmit unit 05 (completed January 26) to work server.


[19:25:15] + Attempting to send results [January 26 19:25:15 UTC]
[19:25:37] - Couldn't send HTTP request to server
[19:25:37] + Could not connect to Work Server (results)
[19:25:37]     (171.67.108.25:8080)
[19:25:37] + Retrying using alternative port
[19:25:58] - Couldn't send HTTP request to server
[19:25:58] + Could not connect to Work Server (results)
[19:25:58]     (171.67.108.25:80)
[19:25:58]   Could not transmit unit 05 to Collection server; keeping in queue.
[19:25:58] Project: 2653 (Run 1, Clone 122, Gen 108)


[19:25:58] + Attempting to send results [January 26 19:25:58 UTC]
[19:26:28] - Couldn't send HTTP request to server
[19:26:28] + Could not connect to Work Server (results)
[19:26:28]     (171.64.65.64:8080)
[19:26:28] + Retrying using alternative port
[19:26:49] - Couldn't send HTTP request to server
[19:26:49] + Could not connect to Work Server (results)
[19:26:49]     (171.64.65.64:80)
[19:26:49] - Error: Could not transmit unit 06 (completed January 26) to work server.


[19:26:49] + Attempting to send results [January 26 19:26:49 UTC]
[19:27:11] - Couldn't send HTTP request to server
[19:27:11] + Could not connect to Work Server (results)
[19:27:11]     (171.67.108.25:8080)
[19:27:11] + Retrying using alternative port
[19:27:32] - Couldn't send HTTP request to server
[19:27:32] + Could not connect to Work Server (results)
[19:27:32]     (171.67.108.25:80)
[19:27:32]   Could not transmit unit 06 to Collection server; keeping in queue.
[19:27:32] Project: 2653 (Run 1, Clone 41, Gen 108)


[19:27:32] + Attempting to send results [January 26 19:27:32 UTC]
[19:28:03] - Couldn't send HTTP request to server
[19:28:03] + Could not connect to Work Server (results)
[19:28:03]     (171.64.65.64:8080)
[19:28:03] + Retrying using alternative port
[19:28:24] - Couldn't send HTTP request to server
[19:28:24] + Could not connect to Work Server (results)
[19:28:24]     (171.64.65.64:80)
[19:28:24] - Error: Could not transmit unit 07 (completed January 26) to work server.


[19:28:24] + Attempting to send results [January 26 19:28:24 UTC]
[19:28:46] - Couldn't send HTTP request to server
[19:28:46] + Could not connect to Work Server (results)
[19:28:46]     (171.67.108.25:8080)
[19:28:46] + Retrying using alternative port
[19:29:07] - Couldn't send HTTP request to server
[19:29:07] + Could not connect to Work Server (results)
[19:29:07]     (171.67.108.25:80)
[19:29:07]   Could not transmit unit 07 to Collection server; keeping in queue.
[19:29:07] Project: 2653 (Run 2, Clone 31, Gen 108)


[19:29:07] + Attempting to send results [January 26 19:29:07 UTC]
[19:29:37] - Couldn't send HTTP request to server
[19:29:37] + Could not connect to Work Server (results)
[19:29:37]     (171.64.65.64:8080)
[19:29:37] + Retrying using alternative port
[19:29:58] - Couldn't send HTTP request to server
[19:29:58] + Could not connect to Work Server (results)
[19:29:58]     (171.64.65.64:80)
[19:29:58] - Error: Could not transmit unit 08 (completed January 26) to work server.


[19:29:58] + Attempting to send results [January 26 19:29:58 UTC]
[19:30:20] - Couldn't send HTTP request to server
[19:30:20] + Could not connect to Work Server (results)
[19:30:20]     (171.67.108.25:8080)
[19:30:20] + Retrying using alternative port
[19:30:41] - Couldn't send HTTP request to server
[19:30:41] + Could not connect to Work Server (results)
[19:30:41]     (171.67.108.25:80)
[19:30:41]   Could not transmit unit 08 to Collection server; keeping in queue.
[19:30:41] Project: 2653 (Run 35, Clone 40, Gen 106)


[19:30:41] + Attempting to send results [January 26 19:30:41 UTC]
[19:31:11] - Couldn't send HTTP request to server
[19:31:11] + Could not connect to Work Server (results)
[19:31:11]     (171.64.65.64:8080)
[19:31:11] + Retrying using alternative port
[19:31:32] - Couldn't send HTTP request to server
[19:31:32] + Could not connect to Work Server (results)
[19:31:32]     (171.64.65.64:80)
[19:31:32] - Error: Could not transmit unit 09 (completed January 24) to work server.


[19:31:32] + Attempting to send results [January 26 19:31:32 UTC]
[19:31:54] - Couldn't send HTTP request to server
[19:31:54] + Could not connect to Work Server (results)
[19:31:54]     (171.67.108.25:8080)
[19:31:54] + Retrying using alternative port
[19:32:15] - Couldn't send HTTP request to server
[19:32:15] + Could not connect to Work Server (results)
[19:32:15]     (171.67.108.25:80)
[19:32:15]   Could not transmit unit 09 to Collection server; keeping in queue.
Any thoughts?
Image
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Project 2653: numerous work units

Post by bruce »

Server 171.64.65.64 does seem to be on-line and not overloaded so there's no obvious explanation.

Which client version are you running? How does your computer connect to the internet?

When a problem applies to a single WU, It's best to post in the "Issues with a specific WU" forum. When a problem applies to multiple WUs associate with the same server, it's better to post in the "Issues with a particular server" forum. I'll move this to the "server" forum and change the title to reflect that server.
3dski
Posts: 13
Joined: Fri Aug 01, 2008 3:56 pm

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by 3dski »

Thanks for the advice on routing this to the correct forum topic. I'm running Folding@Home Client Version 6.23 Beta R1. I've tried connecting through my cable modem and also tried via my 3G phone and gotten the same result.
Image
3dski
Posts: 13
Joined: Fri Aug 01, 2008 3:56 pm

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by 3dski »

Here's the output from queueinfo

Code: Select all

Current Queue: 
Slot 02  Done     
Project: 2653 (Run 1, Clone 20, Gen 108), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 09:33:48
Finished date: January 26 09:38:10
Failed uploads: 36

Slot 03  Done     
Project: 2653 (Run 1, Clone 27, Gen 108), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 09:38:39
Finished date: January 26 09:43:06
Failed uploads: 34

Slot 04  Done     
Project: 2653 (Run 1, Clone 36, Gen 108), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 09:44:12
Finished date: January 26 09:49:38
Failed uploads: 31

Slot 05  Done     
Project: 2653 (Run 1, Clone 45, Gen 108), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 09:51:01
Finished date: January 26 09:56:42
Failed uploads: 29

Slot 06  Done     
Project: 2653 (Run 1, Clone 122, Gen 108), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 09:58:51
Finished date: January 26 10:04:56
Failed uploads: 27

Slot 07  Done     
Project: 2653 (Run 1, Clone 41, Gen 108), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 10:07:00
Finished date: January 26 10:13:08
Failed uploads: 25

Slot 08  Done     
Project: 2653 (Run 2, Clone 31, Gen 108), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 10:15:34
Finished date: January 26 10:22:24
Failed uploads: 23

Slot 09  Done     
Project: 2653 (Run 35, Clone 40, Gen 106), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 24 07:49:50
Finished date: January 24 08:05:10
Failed uploads: 59

Slot 00  Done     
Project: 2665 (Run 3, Clone 503, Gen 88), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 24 09:30:10
Finished date: January 24 14:41:45
Failed uploads: 47

Slot 01 *Ready    
Project: 2665 (Run 3, Clone 223, Gen 89), Core: a1
Work server: 171.64.65.64:8080
Collection server: 171.67.108.25
Download date: January 26 13:17:52
Deadline date: February 1 13:17:52

PF: 0.549612 based on last 2 slot(s)
Image
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by bruce »

3dski wrote:Thanks for the advice on routing this to the correct forum topic. I'm running Folding@Home Client Version 6.23 Beta R1. I've tried connecting through my cable modem and also tried via my 3G phone and gotten the same result.
Do you have a router, and if so, which model? Does anything change if you skip the router and connect the PC directly to the modem?

(It's very difficult to know if this is a problem at your end or at Stanford.)
toTOW
Site Moderator
Posts: 6359
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by toTOW »

I just had some network issues with this server too.
[10:08:53] Project: 2653 (Run 11, Clone 18, Gen 108)


[10:08:53] + Attempting to send results [January 28 10:08:53 UTC]
[10:08:53] - Reading file work/wuresults_07.dat from core
[10:08:53] (Read 5525453 bytes from disk)
[10:08:53] Connecting to http://171.64.65.64:8080/
[10:09:14] - Couldn't send HTTP request to server
[10:09:14] + Could not connect to Work Server (results)
[10:09:14] (171.64.65.64:8080)
[10:09:14] + Retrying using alternative port
[10:09:14] Connecting to http://171.64.65.64:80/
[10:10:21] Posted data.
[10:10:22] Initial: 0000; + Results successfully sent
Connection dropped on port 8080 after sending some data ... but the WU finally went through on port 80.

The download of a new was also a bit irregular, with some period of transfers, and some of inactivity (from 0 to 260 KB/sec).
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
Kenelm
Posts: 11
Joined: Wed May 21, 2008 3:24 pm

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by Kenelm »

Im getting the same issue on that server. Running SMP client, most recent (had to drop in the new exe file since the old one expired on 2/2)

I have 3 other computers sending data fine, only this one and it was fine up until a few days ago.

Code: Select all

--- Opening Log file [February 6 20:15:48 UTC] 


# Windows SMP Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23 Beta R1

                          http://folding.stanford.edu

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

Launch directory: C:\FoldingSMP
Executable: C:\FoldingSMP\[email protected]
Arguments: -smp 

[20:15:48] - Ask before connecting: No
[20:15:48] - User name: Kenelm (Team 80856)
[20:15:48] - User ID: 2AD3C230427AE701
[20:15:48] - Machine ID: 1
[20:15:48] 
[20:15:49] Loaded queue successfully.
[20:15:49] Project: 2665 (Run 1, Clone 4, Gen 91)
[20:15:49] 


[20:15:49] + Attempting to send results [February 6 20:15:49 UTC]
[20:15:49] + Processing work unit
[20:15:49] Work type a1 not eligible for variable processors
[20:15:49] Core required: FahCore_a1.exe
[20:15:49] Core found.
[20:15:49] Using generic mpiexec calls
[20:15:49] Working on queue slot 00 [February 6 20:15:49 UTC]
[20:15:49] + Working ...
[20:15:49] - Couldn't send HTTP request to server
[20:15:49] + Could not connect to Work Server (results)
[20:15:49]     (171.64.65.64:8080)
[20:15:49] + Retrying using alternative port
[20:15:49] - Couldn't send HTTP request to server
[20:15:49] + Could not connect to Work Server (results)
[20:15:49]     (171.64.65.64:80)
[20:15:49] - Error: Could not transmit unit 08 (completed February 4) to work server.


[20:15:49] + Attempting to send results [February 6 20:15:49 UTC]
[20:15:49] 
[20:15:49] *------------------------------*
[20:15:49] Folding@Home Gromacs SMP Core
[20:15:49] Version 1.74 (March 10, 2007)
[20:15:49] 
[20:15:49] Preparing to commence simulation
[20:15:49] - Ensuring status. Please wait.
[20:15:49] - Couldn't send HTTP request to server
[20:15:49] + Could not connect to Work Server (results)
[20:15:49]     (171.67.108.25:8080)
[20:15:49] + Retrying using alternative port
[20:15:49] - Couldn't send HTTP request to server
[20:15:49]   (Got status 503)
[20:15:49] + Could not connect to Work Server (results)
[20:15:49]     (171.67.108.25:80)
[20:15:49]   Could not transmit unit 08 to Collection server; keeping in queue.
[20:16:06] - Looking at optimizations...
[20:16:06] - Working with standard loops on this execution.
[20:16:06] Examination of work files indicates 8 consecutive improper terminations of core.
[20:16:26] - Expanded 4838205 -> 24810145 (decompressed 512.7 percent)
[20:16:27] 
[20:16:27] Project: 2665 (Run 2, Clone 699, Gen 93)
[20:16:27] 
[20:16:29] Entering M.D.
[20:16:35] Calling FAH init
[20:16:37] Read topology
[20:16:37] s
[20:16:37] Writing local files
[20:16:37] int)
[20:16:37] Read checkpoint
[20:16:38] f 250000 steps  (13 percent)
[20:16:38] ons
[20:16:38] Writing local files
[20:16:38] Completed 32500 out of 250000 steps  (13 percent)
[20:16:48] Extra SSE boost OK.
Image
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by bruce »

Kenelm wrote:Im getting the same issue on that server. Running SMP client, most recent (had to drop in the new exe file since the old one expired on 2/2)

I have 3 other computers sending data fine, only this one and it was fine up until a few days ago.
Did you happen to update your security software a few days ago?

The server is reasonably busy, but it's not acting like it's recovering from a huge backlog of clients that haven't been able to upload. i.e.- The netload does vary so you sooner or later you should be lucky enough to find a time when it's less busy.
Kenelm
Posts: 11
Joined: Wed May 21, 2008 3:24 pm

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by Kenelm »

No updates to that computer to my knowledge.
Image
Kenelm
Posts: 11
Joined: Wed May 21, 2008 3:24 pm

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by Kenelm »

I finally killed it and restarted it 10 times to send it and squeezed thru. Well one did, one had expired.
Image
BuddhaChu
Posts: 77
Joined: Wed Apr 16, 2008 2:38 am

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by BuddhaChu »

Can't get a new WU from this server. Connecting to port 80 & 8080 gives "OK" and the server status page says it's in "Full" operation.

Code: Select all

[00:54:07] Connecting to http://assign.stanford.edu:8080/
[00:54:08] Posted data.
[00:54:08] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:54:08] + News From Folding@Home: Welcome to Folding@Home
[00:54:08] Loaded queue successfully.
[00:54:08] Connecting to http://171.64.65.64:8080/
[00:54:08] Posted data.
[00:54:08] Initial: 0000; + Could not connect to Work Server
[00:54:08] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[00:54:18] + Attempting to get work packet
[00:54:18] - Will indicate memory of 2046 MB
[00:54:18] - Connecting to assignment server
[00:54:18] Connecting to http://assign.stanford.edu:8080/
[00:54:18] Posted data.
[00:54:18] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:54:18] + News From Folding@Home: Welcome to Folding@Home
[00:54:18] Loaded queue successfully.
[00:54:18] Connecting to http://171.64.65.64:8080/
[00:54:18] Posted data.
[00:54:18] Initial: 0000; + Could not connect to Work Server
[00:54:18] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[00:54:30] + Attempting to get work packet
[00:54:30] - Will indicate memory of 2046 MB
[00:54:30] - Connecting to assignment server
[00:54:30] Connecting to http://assign.stanford.edu:8080/
[00:54:30] Posted data.
[00:54:30] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:54:30] + News From Folding@Home: Welcome to Folding@Home
[00:54:30] Loaded queue successfully.
[00:54:30] Connecting to http://171.64.65.64:8080/
[00:54:31] Posted data.
[00:54:31] Initial: 0000; + Could not connect to Work Server
[00:54:31] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[00:54:55] + Attempting to get work packet
[00:54:55] - Will indicate memory of 2046 MB
[00:54:55] - Connecting to assignment server
[00:54:55] Connecting to http://assign.stanford.edu:8080/
[00:54:55] Posted data.
[00:54:55] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:54:55] + News From Folding@Home: Welcome to Folding@Home
[00:54:55] Loaded queue successfully.
[00:54:55] Connecting to http://171.64.65.64:8080/
[00:54:56] Posted data.
[00:54:56] Initial: 0000; + Could not connect to Work Server
[00:54:56] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[00:55:44] + Attempting to get work packet
[00:55:44] - Will indicate memory of 2046 MB
[00:55:44] - Connecting to assignment server
[00:55:44] Connecting to http://assign.stanford.edu:8080/
[00:55:45] Posted data.
[00:55:45] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:55:45] + News From Folding@Home: Welcome to Folding@Home
[00:55:45] Loaded queue successfully.
[00:55:45] Connecting to http://171.64.65.64:8080/
[00:55:45] Posted data.
[00:55:45] Initial: 0000; + Could not connect to Work Server
[00:55:45] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[00:57:06] + Attempting to get work packet
[00:57:06] - Will indicate memory of 2046 MB
[00:57:06] - Connecting to assignment server
[00:57:06] Connecting to http://assign.stanford.edu:8080/
[00:57:06] Posted data.
[00:57:06] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:57:06] + News From Folding@Home: Welcome to Folding@Home
[00:57:06] Loaded queue successfully.
[00:57:06] Connecting to http://171.64.65.64:8080/
[00:57:07] Posted data.
[00:57:07] Initial: 0000; + Could not connect to Work Server
[00:57:07] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[00:59:59] + Attempting to get work packet
[00:59:59] - Will indicate memory of 2046 MB
[00:59:59] - Connecting to assignment server
[00:59:59] Connecting to http://assign.stanford.edu:8080/
[01:00:00] Posted data.
[01:00:00] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[01:00:00] + News From Folding@Home: Welcome to Folding@Home
[01:00:00] Loaded queue successfully.
[01:00:00] Connecting to http://171.64.65.64:8080/
[01:00:00] Posted data.
[01:00:00] Initial: 0000; + Could not connect to Work Server
[01:00:00] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[01:05:26] + Attempting to get work packet
[01:05:26] - Will indicate memory of 2046 MB
[01:05:26] - Connecting to assignment server
[01:05:26] Connecting to http://assign.stanford.edu:8080/
[01:05:26] Posted data.
[01:05:26] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[01:05:26] + News From Folding@Home: Welcome to Folding@Home
[01:05:26] Loaded queue successfully.
[01:05:26] Connecting to http://171.64.65.64:8080/
[01:05:27] Posted data.
[01:05:27] Initial: 0000; + Could not connect to Work Server
[01:05:27] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[01:16:18] + Attempting to get work packet
[01:16:18] - Will indicate memory of 2046 MB
[01:16:18] - Connecting to assignment server
[01:16:18] Connecting to http://assign.stanford.edu:8080/
[01:16:18] Posted data.
[01:16:18] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[01:16:18] + News From Folding@Home: Welcome to Folding@Home
[01:16:18] Loaded queue successfully.
[01:16:18] Connecting to http://171.64.65.64:8080/
[01:16:19] Posted data.
[01:16:19] Initial: 0000; + Could not connect to Work Server
[01:16:19] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[01:37:51] + Attempting to get work packet
[01:37:51] - Will indicate memory of 2046 MB
[01:37:51] - Connecting to assignment server
[01:37:51] Connecting to http://assign.stanford.edu:8080/
[01:37:51] Posted data.
[01:37:51] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[01:37:51] + News From Folding@Home: Welcome to Folding@Home
[01:37:51] Loaded queue successfully.
[01:37:51] Connecting to http://171.64.65.64:8080/
[01:37:52] Posted data.
[01:37:52] Initial: 0000; + Could not connect to Work Server
[01:37:52] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
BuddhaChu
Posts: 77
Joined: Wed Apr 16, 2008 2:38 am

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by BuddhaChu »

Follow up:

I restarted the client service and it eventually was able to download a new WU to crunch so I'm now good-2-go with 171.64.65.64
lobuxracer
Posts: 18
Joined: Mon Aug 18, 2008 5:49 am

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by lobuxracer »

Been having issues with this server all weekend.

Code: Select all

[03:39:05] Folding@home Core Shutdown: FINISHED_UNIT
[03:39:05] 
[03:39:05] Folding@home Core Shutdown: FINISHED_UNIT
[03:41:13] CoreStatus = 64 (100)
[03:41:13] Unit 6 finished with 77 percent of time to deadline remaining.
[03:41:13] Updated performance fraction: 0.746027
[03:41:13] Sending work to server
[03:41:13] Project: 2653 (Run 28, Clone 52, Gen 143)


[03:41:13] + Attempting to send results [March 31 03:41:13 UTC]
[03:41:13] - Reading file work/wuresults_06.dat from core
[03:41:13]   (Read 5521044 bytes from disk)
[03:41:13] Connecting to http://171.64.65.64:8080/
[03:41:28] Posted data.
[03:41:28] Initial: 0000; - Uploaded at ~359 kB/s
[03:41:28] - Averaged speed for that direction ~304 kB/s
[03:41:28] + Results successfully sent
[03:41:28] Thank you for your contribution to Folding@Home.
[03:41:28] + Number of Units Completed: 117

[03:41:32] - Warning: Could not delete all work unit files (6): Core returned invalid code
[03:41:32] Trying to send all finished work units
[03:41:32] + No unsent completed units remaining.
[03:41:32] - Preparing to get new work unit...
[03:41:32] + Attempting to get work packet
[03:41:32] - Will indicate memory of 2046 MB
[03:41:32] - Connecting to assignment server
[03:41:32] Connecting to http://assign.stanford.edu:8080/
[03:41:34] Posted data.
[03:41:34] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:41:34] + News From Folding@Home: Welcome to Folding@Home
[03:41:34] Loaded queue successfully.
[03:41:34] Connecting to http://171.64.65.64:8080/
[03:41:34] Posted data.
[03:41:34] Initial: 0000; + Could not connect to Work Server
[03:41:34] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[03:41:54] + Attempting to get work packet
[03:41:54] - Will indicate memory of 2046 MB
[03:41:54] - Connecting to assignment server
[03:41:54] Connecting to http://assign.stanford.edu:8080/
[03:41:54] Posted data.
[03:41:54] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:41:54] + News From Folding@Home: Welcome to Folding@Home
[03:41:54] Loaded queue successfully.
[03:41:54] Connecting to http://171.64.65.64:8080/
[03:41:55] Posted data.
[03:41:55] Initial: 0000; + Could not connect to Work Server
[03:41:55] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[03:42:15] + Attempting to get work packet
[03:42:15] - Will indicate memory of 2046 MB
[03:42:15] - Connecting to assignment server
[03:42:15] Connecting to http://assign.stanford.edu:8080/
[03:42:16] Posted data.
[03:42:16] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:42:16] + News From Folding@Home: Welcome to Folding@Home
[03:42:16] Loaded queue successfully.
[03:42:16] Connecting to http://171.64.65.64:8080/
[03:42:17] Posted data.
[03:42:17] Initial: 0000; + Could not connect to Work Server
[03:42:17] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[03:42:39] + Attempting to get work packet
[03:42:39] - Will indicate memory of 2046 MB
[03:42:39] - Connecting to assignment server
[03:42:39] Connecting to http://assign.stanford.edu:8080/
[03:42:39] Posted data.
[03:42:39] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:42:39] + News From Folding@Home: Welcome to Folding@Home
[03:42:39] Loaded queue successfully.
[03:42:39] Connecting to http://171.64.65.64:8080/
[03:42:40] Posted data.
[03:42:40] Initial: 0000; + Could not connect to Work Server
[03:42:40] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[03:43:23] + Attempting to get work packet
[03:43:23] - Will indicate memory of 2046 MB
[03:43:23] - Connecting to assignment server
[03:43:23] Connecting to http://assign.stanford.edu:8080/
[03:43:23] Posted data.
[03:43:23] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:43:23] + News From Folding@Home: Welcome to Folding@Home
[03:43:23] Loaded queue successfully.
[03:43:23] Connecting to http://171.64.65.64:8080/
[03:43:24] Posted data.
[03:43:24] Initial: 0000; + Could not connect to Work Server
[03:43:24] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[03:44:54] + Attempting to get work packet
[03:44:54] - Will indicate memory of 2046 MB
[03:44:54] - Connecting to assignment server
[03:44:54] Connecting to http://assign.stanford.edu:8080/
[03:44:54] Posted data.
[03:44:54] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:44:54] + News From Folding@Home: Welcome to Folding@Home
[03:44:55] Loaded queue successfully.
[03:44:55] Connecting to http://171.64.65.64:8080/
[03:44:55] Posted data.
[03:44:55] Initial: 0000; + Could not connect to Work Server
[03:44:55] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[03:47:39] + Attempting to get work packet
[03:47:39] - Will indicate memory of 2046 MB
[03:47:39] - Connecting to assignment server
[03:47:39] Connecting to http://assign.stanford.edu:8080/
[03:47:40] Posted data.
[03:47:40] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:47:40] + News From Folding@Home: Welcome to Folding@Home
[03:47:40] Loaded queue successfully.
[03:47:40] Connecting to http://171.64.65.64:8080/
[03:47:41] Posted data.
[03:47:41] Initial: 0000; + Could not connect to Work Server
[03:47:41] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[03:53:07] + Attempting to get work packet
[03:53:07] - Will indicate memory of 2046 MB
[03:53:07] - Connecting to assignment server
[03:53:07] Connecting to http://assign.stanford.edu:8080/
[03:53:08] Posted data.
[03:53:08] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[03:53:08] + News From Folding@Home: Welcome to Folding@Home
[03:53:08] Loaded queue successfully.
[03:53:08] Connecting to http://171.64.65.64:8080/
[03:53:08] Posted data.
[03:53:08] Initial: 0000; + Could not connect to Work Server
[03:53:08] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[04:03:54] + Attempting to get work packet
[04:03:54] - Will indicate memory of 2046 MB
[04:03:54] - Connecting to assignment server
[04:03:54] Connecting to http://assign.stanford.edu:8080/
[04:03:54] Posted data.
[04:03:54] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[04:03:54] + News From Folding@Home: Welcome to Folding@Home
[04:03:55] Loaded queue successfully.
[04:03:55] Connecting to http://171.64.65.64:8080/
[04:03:55] Posted data.
[04:03:55] Initial: 0000; + Could not connect to Work Server
[04:03:55] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[04:25:17] + Attempting to get work packet
[04:25:17] - Will indicate memory of 2046 MB
[04:25:17] - Connecting to assignment server
[04:25:17] Connecting to http://assign.stanford.edu:8080/
[04:25:18] Posted data.
[04:25:18] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[04:25:18] + News From Folding@Home: Welcome to Folding@Home
[04:25:18] Loaded queue successfully.
[04:25:18] Connecting to http://171.64.65.64:8080/
[04:25:18] Posted data.
[04:25:18] Initial: 0000; + Could not connect to Work Server
[04:25:18] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
Typically waiting at least a half hour to get a new WU. What's up with this?
Image
road-runner
Posts: 227
Joined: Sun Dec 02, 2007 4:01 am
Location: Willis, Texas

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by road-runner »

I have been having trouble getting WUs from this server also....

Code: Select all

[02:06:09] Project: 2653 (Run 23, Clone 46, Gen 146)


[02:06:09] + Attempting to send results [March 31 02:06:09 UTC]
[02:07:36] + Results successfully sent
[02:07:36] Thank you for your contribution to Folding@Home.
[02:07:36] + Number of Units Completed: 12

[02:07:40] - Preparing to get new work unit...
[02:07:40] + Attempting to get work packet
[02:07:40] - Connecting to assignment server
[02:07:40] - Successful: assigned to (171.64.65.64).
[02:07:40] + News From Folding@Home: Welcome to Folding@Home
[02:07:40] Loaded queue successfully.
[02:07:41] + Could not connect to Work Server
[02:07:41] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[02:07:47] + Attempting to get work packet
[02:07:47] - Connecting to assignment server
[02:07:48] - Successful: assigned to (171.64.65.64).
[02:07:48] + News From Folding@Home: Welcome to Folding@Home
[02:07:48] Loaded queue successfully.
[02:07:48] + Could not connect to Work Server
[02:07:48] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[02:08:10] + Attempting to get work packet
[02:08:10] - Connecting to assignment server
[02:08:10] - Successful: assigned to (171.64.65.64).
[02:08:10] + News From Folding@Home: Welcome to Folding@Home
[02:08:10] Loaded queue successfully.
[02:08:11] + Could not connect to Work Server
[02:08:11] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[02:08:37] + Attempting to get work packet
[02:08:37] - Connecting to assignment server
[02:08:37] - Successful: assigned to (171.64.65.64).
[02:08:37] + News From Folding@Home: Welcome to Folding@Home
[02:08:37] Loaded queue successfully.
[02:08:38] + Could not connect to Work Server
[02:08:38] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[02:09:22] + Attempting to get work packet
[02:09:22] - Connecting to assignment server
[02:09:23] - Successful: assigned to (171.64.65.64).
[02:09:23] + News From Folding@Home: Welcome to Folding@Home
[02:09:23] Loaded queue successfully.
[02:09:23] + Could not connect to Work Server
[02:09:23] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[02:10:44] + Attempting to get work packet
[02:10:44] - Connecting to assignment server
[02:10:44] - Successful: assigned to (171.64.65.64).
[02:10:44] + News From Folding@Home: Welcome to Folding@Home
[02:10:44] Loaded queue successfully.
[02:10:45] + Could not connect to Work Server
[02:10:45] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[02:13:28] + Attempting to get work packet
[02:13:28] - Connecting to assignment server
[02:13:29] - Successful: assigned to (171.64.65.64).
[02:13:29] + News From Folding@Home: Welcome to Folding@Home
[02:13:29] Loaded queue successfully.
[02:13:29] + Could not connect to Work Server
[02:13:29] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[02:18:57] + Attempting to get work packet
[02:18:57] - Connecting to assignment server
[02:18:57] - Successful: assigned to (171.64.65.64).
[02:18:57] + News From Folding@Home: Welcome to Folding@Home
[02:18:58] Loaded queue successfully.
[02:18:58] + Could not connect to Work Server
[02:18:58] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[02:29:45] + Attempting to get work packet
[02:29:45] - Connecting to assignment server
[02:29:53] - Successful: assigned to (171.64.65.64).
[02:29:53] + News From Folding@Home: Welcome to Folding@Home
[02:29:53] Loaded queue successfully.
[02:29:58] + Could not connect to Work Server
[02:29:58] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[02:51:20] + Attempting to get work packet
[02:51:20] - Connecting to assignment server
[02:51:20] - Successful: assigned to (171.64.65.64).
[02:51:20] + News From Folding@Home: Welcome to Folding@Home
[02:51:21] Loaded queue successfully.
[02:51:21] + Could not connect to Work Server
[02:51:21] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[03:34:09] + Attempting to get work packet
[03:34:09] - Connecting to assignment server
[03:34:10] - Successful: assigned to (171.64.65.64).
[03:34:10] + News From Folding@Home: Welcome to Folding@Home
[03:34:10] Loaded queue successfully.
[03:34:11] + Could not connect to Work Server
[03:34:11] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[04:22:11] + Attempting to get work packet
[04:22:11] - Connecting to assignment server
[04:22:12] - Successful: assigned to (171.64.65.64).
[04:22:12] + News From Folding@Home: Welcome to Folding@Home
[04:22:12] Loaded queue successfully.
[04:22:12] + Could not connect to Work Server
[04:22:12] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[05:10:25] + Attempting to get work packet
[05:10:25] - Connecting to assignment server
[05:10:39] - Successful: assigned to (171.64.65.64).
[05:10:39] + News From Folding@Home: Welcome to Folding@Home
[05:10:39] Loaded queue successfully.
[05:10:43] + Could not connect to Work Server
[05:10:43] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
Image
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.64.65.64 - Proj 2653: numerous work units

Post by bruce »

That server is low on WUs.

If a server runs out of WUs, the Assignment Server will redirect you to another server which has work for your client (such as 171.64.65.56) but every time somebody returns a WU, an new one is generated so 171.64.65.64 is constantly switching between having work to assign and not having work to assign. I think the Assignment Server is having trouble keeping up with the changes.
Post Reply