Page 1 of 1
171.67.108.60 Not Assigning
Posted: Thu Mar 29, 2012 8:54 pm
by HendricksSA
I rarely have problems getting work from an SMP server - but I have some now. 171.67.108.60 seems fine according to the server stats page but it does not seem to want to give me an SMP work unit. Just passing FYI. Relevant log extract follows:
20:35:02:WU02:FS02:News: Welcome to Folding@Home
20:35:02:WU02:FS02:Assigned to work server 171.67.108.60
20:35:02:WU02:FS02:Requesting new work unit for slot 02: READY smp:6 from 171.67.108.60
20:35:02:WU02:FS02:Connecting to 171.67.108.60:8080
20:35:02:ERROR:WU02:FS02:Exception: Server did not assign work unit
..............
20:40:17:WU02:FS02:News: Welcome to Folding@Home
20:40:17:WU02:FS02:Assigned to work server 171.67.108.60
20:40:19:WU02:FS02:Requesting new work unit for slot 02: READY smp:6 from 171.67.108.60
20:40:19:WU02:FS02:Connecting to 171.67.108.60:8080
20:40:20:ERROR:WU02:FS02:Exception: Server did not assign work unit
Re: 171.67.108.60 Not Assigning
Posted: Thu Mar 29, 2012 9:03 pm
by HendricksSA
I will not be able to update you as I just got reassigned to 171.67.108.59 and received a SMP work unit from it. Log extract follows:
20:56:42:WU02:FS02:Connecting to assign3.stanford.edu:8080
20:56:43:WU02:FS02:News: Welcome to Folding@Home
20:56:43:WU02:FS02:Assigned to work server 171.67.108.60
20:56:43:WU02:FS02:Requesting new work unit for slot 02: READY smp:6 from 171.67.108.60
20:56:43:WU02:FS02:Connecting to 171.67.108.60:8080
20:56:43:ERROR:WU02:FS02:Exception: Server did not assign work unit
20:59:20:WU02:FS02:Connecting to assign3.stanford.edu:8080
20:59:20:WU02:FS02:News: Welcome to Folding@Home
20:59:21:WU02:FS02:Assigned to work server 171.67.108.59
20:59:21:WU02:FS02:Requesting new work unit for slot 02: READY smp:6 from 171.67.108.59
20:59:21:WU02:FS02:Connecting to 171.67.108.59:8080
20:59:21:WU02:FS02:Downloading 860.63KiB
20:59:23:WU02:FS02:Download complete
Re: 171.67.108.60 Not Assigning
Posted: Thu Mar 29, 2012 9:20 pm
by bruce
HendricksSA wrote:I will not be able to update you as I just got reassigned to 171.67.108.59 and received a SMP work unit from it.
That's to be expected. Servers do run low on WUs. The AS tries to keep track of which servers are available. Even though it polls them at regular intervals, Things can happen during those intervals and apparently it took a few minutes for the AS to figured that out. I suggest that next time you wait a bit longer for the interval (whatever it is) to pass. You waited 5m15s.
Re: 171.67.108.60 Not Assigning
Posted: Thu Mar 29, 2012 10:01 pm
by RLHay
Bruce, HendriksSA log is the same as mine, reported in viewtopic.php?f=18&t=21131, except with the 60 and 59 server roles reversed. The 59 server was reporting WU's as being available at the time and I went without assignment of 2-4 machines over a period of days.
I'm not saying that you are wrong, just that the available info didn't lead me to believe that there was a lack of WU's or a problem with server availability.
Re: 171.67.108.60 Not Assigning
Posted: Thu Mar 29, 2012 10:38 pm
by Joe_H
Those two servers were reaching the end of some projects right about then, and starting a new project in beta. There would have been a limited supply of WU's. It is possible the assignment server connected your machines to them as work was listed as available, but by the time your connection was made to the work server they were all out. Usually just a temporary problem in my experience, a bit unusual to last over a period of time.
Re: 171.67.108.60 Not Assigning
Posted: Thu Mar 29, 2012 11:57 pm
by bruce
I'm not sure it's possible to explain all of the possible reasons why a server won't make an assignment -- even if we assume it's working normally -- and there's no way to prove if it was working normally at the time. I've seen cases where something was not working correctly, so your report is valuable, particularly if someone with access to the server can see something we can't see and fix it.
Another possibility: Your client always requests a new WU with a particular set of characteristics. A server can have more than one class of WUs. The total number of WUs doesn't tell you if there are any that you're eligible to receive. the words "low on WUs" is only meaningful for the particular group of projects that are eligible to satisfy your request for a new assignment
If there are WUs that are for V7 only and you have V6 or there' a mixture of CPU and GPU projects and you're requesting the type that the sever is out of, it's a Linux/Windows/OS-X restriction or any number of other possible distinctions, the numbers you see on serverstat might not describe the situation from the perspective of YOUR client's settings even when serverstat seems to indicate that from the server's perspective, everything is working. If the PG finds a case like that, they'll try to make sure it doesn't happen again or they'll figure out a way to display that information on serverstat.
Still another possibility: The server owner might have to suspend a specific project to update it or might set temporary restrictions while adding new projects.
I have no explanation for RLHay's going without an assignment of 2-4 machines over a period of days. Obviously that's not supposed to happen.
Re: 171.67.108.60 Not Assigning
Posted: Fri Mar 30, 2012 4:29 am
by HendricksSA
Whatever the hesitation with server 108.60 is, it continues through at least 0400Z. I've had 4 machines unable to get work from it until they are reassigned to 108.59 (the server RLHay was having problems with earlier). It isn't a major problem as the reassignment usually occurs after about 30 minutes. I just hate having them sit idle for a half hour each time I complete an SMP work unit.
Here is the log from another machine that has the same error. Just reporting FYI. As before, server stat page shows normal for 108.60 keeping in mind what bruce said above.
03:54:44:WU00:FS01:Connecting to assign3.stanford.edu:8080
03:54:44:WU00:FS01:News: Welcome to Folding@Home
03:54:44:WU00:FS01:Assigned to work server 171.67.108.60
03:54:44:WU00:FS01:Requesting new work unit for slot 01: READY smp:4 from 171.67.108.60
03:54:44:WU00:FS01:Connecting to 171.67.108.60:8080
03:54:44:ERROR:WU00:FS01:Exception: Server did not assign work unit
Re: 171.67.108.60 Not Assigning
Posted: Fri Mar 30, 2012 7:09 am
by Fahrenheit451
I can confirm that 171.67.108.60 doesn't work properly (Error: Bad packet type from server), about since midnight. The finished WU's at the beginning of my log I received from 171.67.108.59.
Code: Select all
--- Opening Log file [March 27 07:07:55 UTC]
# Windows CPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\USERNAME\AppData\Roaming\Folding@home-x86
Arguments: -advmethods -verbosity 9
[07:07:55] - Ask before connecting: No
[07:07:55] - User name: superduper4711 (Team 0)
[07:07:55] - User ID: ECCE00A5AF7AA44
[07:07:55] - Machine ID: 1
[07:07:55]
[07:07:55] Loaded queue successfully.
[07:07:55] Initialization complete
[07:07:55]
[07:07:55] + Processing work unit
<SNIP>
[07:36:09] Project: 8024 (Run 39, Clone 11, Gen 1)
[07:36:09]
[07:36:09] Assembly optimizations on if available.
[07:36:09] Entering M.D.
[07:36:15] Mapping NT from 1 to 1
[07:36:15] Completed 0 out of 250000 steps (0%)
<SNIP>
[23:00:26] Completed 250000 out of 250000 steps (100%)
[23:00:27] DynamicWrapper: Finished Work Unit: sleep=10000
[23:00:37]
[23:00:37] Finished Work Unit:
[23:00:37] - Reading up to 1299552 from "work/wudata_05.trr": Read 1299552
[23:00:37] trr file hash check passed.
[23:00:37] - Reading up to 777428 from "work/wudata_05.xtc": Read 777428
[23:00:37] xtc file hash check passed.
[23:00:37] edr file hash check passed.
[23:00:37] logfile size: 28460
[23:00:37] Leaving Run
[23:00:39] - Writing 2110844 bytes of core data to disk...
[23:00:40] Done: 2110332 -> 2017628 (compressed to 95.6 percent)
[23:00:40] ... Done.
[23:00:40] - Shutting down core
[23:00:40]
[23:00:40] Folding@home Core Shutdown: FINISHED_UNIT
[23:00:43] CoreStatus = 64 (100)
[23:00:43] Unit 5 finished with 91 percent of time to deadline remaining.
[23:00:43] Updated performance fraction: 0.900677
[23:00:43] Sending work to server
[23:00:43] Project: 8024 (Run 39, Clone 11, Gen 1)
[23:00:43] - Read packet limit of 540015616... Set to 524286976.
[23:00:43] + Attempting to send results [March 29 23:00:43 UTC]
[23:00:43] - Reading file work/wuresults_05.dat from core
[23:00:43] (Read 2018140 bytes from disk)
[23:00:43] Connecting to http://171.67.108.59:8080/
[23:01:14] Posted data.
[23:01:14] Initial: 0000; - Uploaded at ~63 kB/s
[23:01:14] - Averaged speed for that direction ~63 kB/s
[23:01:14] + Results successfully sent
[23:01:14] Thank you for your contribution to Folding@Home.
[23:01:14] + Number of Units Completed: 590
[23:01:18] Trying to send all finished work units
[23:01:18] + No unsent completed units remaining.
[23:01:18] - Preparing to get new work unit...
[23:01:18] + Attempting to get work packet
[23:01:18] - Will indicate memory of 2045 MB
[23:01:18] - Connecting to assignment server
[23:01:18] Connecting to http://assign.stanford.edu:8080/
[23:01:19] Posted data.
[23:01:19] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:01:19] + News From Folding@Home: Welcome to Folding@Home
[23:01:19] Loaded queue successfully.
[23:01:19] Connecting to http://171.67.108.60:8080/
[23:01:20] Posted data.
[23:01:20] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:01:20] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[23:01:26] + Attempting to get work packet
[23:01:26] - Will indicate memory of 2045 MB
[23:01:26] - Connecting to assignment server
[23:01:26] Connecting to http://assign.stanford.edu:8080/
[23:01:27] Posted data.
[23:01:27] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:01:27] + News From Folding@Home: Welcome to Folding@Home
[23:01:27] Loaded queue successfully.
[23:01:27] Connecting to http://171.67.108.60:8080/
[23:01:28] Posted data.
[23:01:28] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:01:28] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[23:01:42] + Attempting to get work packet
[23:01:42] - Will indicate memory of 2045 MB
[23:01:42] - Connecting to assignment server
[23:01:42] Connecting to http://assign.stanford.edu:8080/
[23:01:42] Posted data.
[23:01:42] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:01:42] + News From Folding@Home: Welcome to Folding@Home
[23:01:43] Loaded queue successfully.
[23:01:43] Connecting to http://171.67.108.60:8080/
[23:01:43] Posted data.
[23:01:43] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:01:43] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[23:02:07] + Attempting to get work packet
[23:02:07] - Will indicate memory of 2045 MB
[23:02:07] - Connecting to assignment server
[23:02:07] Connecting to http://assign.stanford.edu:8080/
[23:02:08] Posted data.
[23:02:08] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:02:08] + News From Folding@Home: Welcome to Folding@Home
[23:02:08] Loaded queue successfully.
[23:02:08] Connecting to http://171.67.108.60:8080/
[23:02:08] Posted data.
[23:02:08] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:02:08] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[23:03:01] + Attempting to get work packet
[23:03:01] - Will indicate memory of 2045 MB
[23:03:01] - Connecting to assignment server
[23:03:01] Connecting to http://assign.stanford.edu:8080/
[23:03:01] Posted data.
[23:03:01] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:03:01] + News From Folding@Home: Welcome to Folding@Home
[23:03:02] Loaded queue successfully.
[23:03:02] Connecting to http://171.67.108.60:8080/
[23:03:02] Posted data.
[23:03:02] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:03:02] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[23:04:32] + Attempting to get work packet
[23:04:32] - Will indicate memory of 2045 MB
[23:04:32] - Connecting to assignment server
[23:04:32] Connecting to http://assign.stanford.edu:8080/
[23:04:33] Posted data.
[23:04:33] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:04:33] + News From Folding@Home: Welcome to Folding@Home
[23:04:33] Loaded queue successfully.
[23:04:33] Connecting to http://171.67.108.60:8080/
[23:04:34] Posted data.
[23:04:34] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:04:34] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[23:07:26] + Attempting to get work packet
[23:07:26] - Will indicate memory of 2045 MB
[23:07:26] - Connecting to assignment server
[23:07:26] Connecting to http://assign.stanford.edu:8080/
[23:07:27] Posted data.
[23:07:27] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:07:27] + News From Folding@Home: Welcome to Folding@Home
[23:07:27] Loaded queue successfully.
[23:07:27] Connecting to http://171.67.108.60:8080/
[23:07:28] Posted data.
[23:07:28] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:07:28] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[23:13:00] + Attempting to get work packet
[23:13:00] - Will indicate memory of 2045 MB
[23:13:00] - Connecting to assignment server
[23:13:00] Connecting to http://assign.stanford.edu:8080/
[23:13:01] Posted data.
[23:13:01] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:13:01] + News From Folding@Home: Welcome to Folding@Home
[23:13:01] Loaded queue successfully.
[23:13:01] Connecting to http://171.67.108.60:8080/
[23:13:01] Posted data.
[23:13:01] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:13:01] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[23:23:48] + Attempting to get work packet
[23:23:48] - Will indicate memory of 2045 MB
[23:23:48] - Connecting to assignment server
[23:23:48] Connecting to http://assign.stanford.edu:8080/
[23:23:49] Posted data.
[23:23:49] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:23:49] + News From Folding@Home: Welcome to Folding@Home
[23:23:49] Loaded queue successfully.
[23:23:49] Connecting to http://171.67.108.60:8080/
[23:23:50] Posted data.
[23:23:50] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:23:50] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[23:45:12] + Attempting to get work packet
[23:45:12] - Will indicate memory of 2045 MB
[23:45:12] - Connecting to assignment server
[23:45:12] Connecting to http://assign.stanford.edu:8080/
[23:45:13] Posted data.
[23:45:13] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[23:45:13] + News From Folding@Home: Welcome to Folding@Home
[23:45:14] Loaded queue successfully.
[23:45:14] Connecting to http://171.67.108.60:8080/
[23:45:14] Posted data.
[23:45:14] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[23:45:14] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
[00:27:59] + Attempting to get work packet
[00:27:59] - Will indicate memory of 2045 MB
[00:27:59] - Connecting to assignment server
[00:27:59] Connecting to http://assign.stanford.edu:8080/
[00:28:00] Posted data.
[00:28:00] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[00:28:00] + News From Folding@Home: Welcome to Folding@Home
[00:28:00] Loaded queue successfully.
[00:28:00] Connecting to http://171.67.108.60:8080/
[00:28:01] Posted data.
[00:28:01] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[00:28:01] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.
[01:08:22] - Autosending finished units... [March 30 01:08:22 UTC]
[01:08:22] Trying to send all finished work units
[01:08:22] + No unsent completed units remaining.
[01:08:22] - Autosend completed
[01:16:04] + Attempting to get work packet
[01:16:04] - Will indicate memory of 2045 MB
[01:16:04] - Connecting to assignment server
[01:16:04] Connecting to http://assign.stanford.edu:8080/
[01:16:05] Posted data.
[01:16:05] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[01:16:05] + News From Folding@Home: Welcome to Folding@Home
[01:16:05] Loaded queue successfully.
[01:16:05] Connecting to http://171.67.108.60:8080/
[01:16:06] Posted data.
[01:16:06] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[01:16:06] - Attempt #12 to get work failed, and no other work to do.
Waiting before retry.
[02:04:14] + Attempting to get work packet
[02:04:14] - Will indicate memory of 2045 MB
[02:04:14] - Connecting to assignment server
[02:04:14] Connecting to http://assign.stanford.edu:8080/
[02:04:15] Posted data.
[02:04:15] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[02:04:15] + News From Folding@Home: Welcome to Folding@Home
[02:04:15] Loaded queue successfully.
[02:04:15] Connecting to http://171.67.108.60:8080/
[02:04:15] Posted data.
[02:04:15] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[02:04:15] - Attempt #13 to get work failed, and no other work to do.
Waiting before retry.
[02:52:16] + Attempting to get work packet
[02:52:16] - Will indicate memory of 2045 MB
[02:52:16] - Connecting to assignment server
[02:52:16] Connecting to http://assign.stanford.edu:8080/
[02:52:17] Posted data.
[02:52:17] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[02:52:17] + News From Folding@Home: Welcome to Folding@Home
[02:52:18] Loaded queue successfully.
[02:52:18] Connecting to http://171.67.108.60:8080/
[02:52:18] Posted data.
[02:52:18] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[02:52:18] - Attempt #14 to get work failed, and no other work to do.
Waiting before retry.
[03:40:24] + Attempting to get work packet
[03:40:24] - Will indicate memory of 2045 MB
[03:40:24] - Connecting to assignment server
[03:40:24] Connecting to http://assign.stanford.edu:8080/
[03:40:25] Posted data.
[03:40:25] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[03:40:25] + News From Folding@Home: Welcome to Folding@Home
[03:40:25] Loaded queue successfully.
[03:40:25] Connecting to http://171.67.108.60:8080/
[03:40:25] Posted data.
[03:40:25] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[03:40:25] - Attempt #15 to get work failed, and no other work to do.
Waiting before retry.
[04:28:30] + Attempting to get work packet
[04:28:30] - Will indicate memory of 2045 MB
[04:28:30] - Connecting to assignment server
[04:28:30] Connecting to http://assign.stanford.edu:8080/
[04:28:32] Posted data.
[04:28:32] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[04:28:32] + News From Folding@Home: Welcome to Folding@Home
[04:28:32] Loaded queue successfully.
[04:28:32] Connecting to http://171.67.108.60:8080/
[04:28:33] Posted data.
[04:28:33] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[04:28:33] - Attempt #16 to get work failed, and no other work to do.
Waiting before retry.
[05:16:46] + Attempting to get work packet
[05:16:46] - Will indicate memory of 2045 MB
[05:16:46] - Connecting to assignment server
[05:16:46] Connecting to http://assign.stanford.edu:8080/
[05:16:47] Posted data.
[05:16:47] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[05:16:47] + News From Folding@Home: Welcome to Folding@Home
[05:16:48] Loaded queue successfully.
[05:16:48] Connecting to http://171.67.108.60:8080/
[05:16:48] Posted data.
[05:16:48] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[05:16:48] - Attempt #17 to get work failed, and no other work to do.
Waiting before retry.
[06:05:02] + Attempting to get work packet
[06:05:02] - Will indicate memory of 2045 MB
[06:05:02] - Connecting to assignment server
[06:05:02] Connecting to http://assign.stanford.edu:8080/
[06:05:04] Posted data.
[06:05:04] Initial: 43AB; - Successful: assigned to (171.67.108.60).
[06:05:04] + News From Folding@Home: Welcome to Folding@Home
[06:05:04] Loaded queue successfully.
[06:05:04] Connecting to http://171.67.108.60:8080/
[06:05:05] Posted data.
[06:05:05] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[06:05:05] - Attempt #18 to get work failed, and no other work to do.
Waiting before retry.