Page 3 of 4
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:16 pm
by noorman
kasson wrote:There are plenty of A3 -advanced methods work units. The situation with Server .22 is a little more complicated right now because we have a primary supply of 2684's and then some work units that are more client-restricted (e.g. a few leftover A2 work units). This makes it harder for the AS to correctly account for the # of available work units. The spec is that it's supposed to count the number of unrestricted work units, but evidently something's going wrong there.
.
I don't understand though, the logic of the AS in leaving member's systems without work for over 20 hours (as reported to me); why doesn't it look for Work Units in a lower grade pool (like the -advmethods in stead of the bigadv) ?
There 's more wrong than the bad counting of available Work units of a certain kind, IMO.
.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:21 pm
by PantherX
noorman wrote:...why doesn't it look for Work Units in a lower grade pool (like the -advmethods in stead of the bigadv) ?...
It does actually:
[quote=""Kasson"]...bigadv has been enabled for windows. Depending on the work unit availability, machines requesting bigadv may roll over to normal -advmethods.[/quote]
My windows -bigadv did ~10 normal WUs when bigadv was unavailable. Now it is back crunching bigadv WUs.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:23 pm
by noorman
PantherX wrote:noorman wrote:...why doesn't it look for Work Units in a lower grade pool (like the -advmethods in stead of the bigadv) ?...
It does actually:
[quote=""Kasson"]...bigadv has been enabled for windows. Depending on the work unit availability, machines requesting bigadv may roll over to normal -advmethods.
My windows -bigadv did ~10 normal WUs when bigadv was unavailable. Now it is back crunching bigadv WUs.[/quote].
I 'm sorry to say that a fellow Folder reported to me that his system was configured for -bigadv and that it had been idle for = 20 hrs !
He noticed the lack of Work and switched it 'manually' to -advmethods to get Work !?
.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:41 pm
by PantherX
@noorman: If you could get the time-frame of this event, it would be helpful as I have read that some users had to use -advmethods to get WU. However, I am guessing that that problem was fixed because from 15 July to 18 July, I was doing normal a3 WUs with these flags:
Arguments: -smp 7 -bigadv -verbosity 9
On 19 July, at 0613 UTC, I was able to get a bigadv WU Project 2685 which was released on 18 July for Windows and OS/X
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:44 pm
by noorman
PantherX wrote:@noorman: If you could get the time-frame of this event, it would be helpful as I have read that some users had to use -advmethods to get WU. However, I am guessing that that problem was fixed because from 15 July to 18 July, I was doing normal a3 WUs with these flags:
Arguments: -smp 7 -bigadv -verbosity 9
On 19 July, at 0613 UTC, I was able to get a bigadv WU Project 2685 which was released on 18 July for Windows and OS/X
.
The report I got is from today ! It was only posted a few hours ago.
So, if anything was changed on 15 July, it hasn't fixed things (completely) ...
.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:55 pm
by bruce
noorman wrote:I don't understand though, the logic of the AS in leaving member's systems without work for over 20 hours (as reported to me); why doesn't it look for Work Units in a lower grade pool (like the -advmethods in stead of the bigadv) ?
There 's more wrong than the bad counting of available Work units of a certain kind, IMO.
kasson wrote:The spec is that it's supposed to count the number of unrestricted work units, but evidently something's going wrong there.
.
Would it help if kasson has used the word "bug" in his last sentence?
I'm not sure I understand the exact nature of the bug but I can make some observations.
First, apparently the same server has both bigadv projects and other projects. Second, bigadv is one restriction. Third, the server has projects for Windows/Linux/MacOS and since he's shut off bigadv for Linux, there is more than one possible answer to how many WUs are available for "your" platform. Fourth, there may be other combinations of restrictions, but somehow the code has to digest all those numbers into a single number that counts WUs that your client is willing to accept. Fifth, the new server code is still under development, so new combinations of restrictions might uncover a bug that hasn't been seen before (and that's apparently what happened).
I have no information about when that bug might be fixed.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 5:56 pm
by 7im
Um, Windows or Linux client?
EDIT: Bruce beat me to it...
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 7:33 pm
by noorman
7im wrote:Um, Windows or Linux client?
EDIT: Bruce beat me to it...
.
Since there were only bigadv WU's available for Windows (at this time), Windows ...
OK, I got it, that both problems seem to have been recognized (as bugs)
I just wanted to make sure of that !
.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 8:40 pm
by 7im
noorman wrote:7im wrote:Um, Windows or Linux client?
EDIT: Bruce beat me to it...
.
Since there were only bigadv WU's available for Windows (at this time), Windows ...
Ya, sure, we both knew that already. But did you ask that question back on your forum before bringing that question here? Or did you just assume it was Windows, like you wrongly assumed I was asking a dumb question when you rolled your eyes at me?
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 8:48 pm
by zetachi
I was the user that Norrman was referencing that brought the issue up in our forum as well as here.
Re: 171.67.108.22
Posted: Mon Jul 19, 2010 8:59 pm
by noorman
7im wrote:noorman wrote:7im wrote:Um, Windows or Linux client?
EDIT: Bruce beat me to it...
.
Since there were only bigadv WU's available for Windows (at this time), Windows ...
Ya, sure, we both knew that already. But did you ask that question back on your forum before bringing that question here? Or did you just assume it was Windows, like you wrongly assumed I was asking a dumb question when you rolled your eyes at me?
.
Since my fellow Folder reported this now, he was doing Windows SMP WU's ...
Very few people at my previous Team did run any Linux stuff.
So I 'm very sure it was Windows !
.
Re: 171.67.108.22
Posted: Tue Jul 20, 2010 1:45 pm
by kasson
FYI we fixed the WU available reporting issue on this server some time back (via a workaround). Assigns appear to be working for all users but about 5; I'm guessing that's the one noorman is referring to. Corresponding offline.
Re: 171.67.108.22
Posted: Tue Jul 20, 2010 2:03 pm
by zetachi
hmmm and again?
Code: Select all
Folding@Home Client Version 6.29
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\Doug\SMP 3
Executable: C:\Users\Doug\SMP 3\SMP 3.exe
Arguments: -local -forceasm -smp -bigadv
[03:58:02] - Ask before connecting: No
[03:58:02] - User name: Zetachi (Team 734)
[03:58:02] - User ID:
[03:58:02] - Machine ID: 3
[03:58:02]
[03:58:02] Loaded queue successfully.
[03:58:02] - Preparing to get new work unit...
[03:58:02] Cleaning up work directory
[03:58:02] + Attempting to get work packet
[03:58:02] Passkey found
[03:58:02] - Connecting to assignment server
[03:58:03] - Successful: assigned to (171.67.108.22).
[03:58:03] + News From Folding@Home: Welcome to Folding@Home
[03:58:03] Loaded queue successfully.
[03:58:15] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[03:58:33] + Attempting to get work packet
[03:58:33] Passkey found
[03:58:33] - Connecting to assignment server
[03:58:34] - Successful: assigned to (171.67.108.22).
[03:58:34] + News From Folding@Home: Welcome to Folding@Home
[03:58:34] Loaded queue successfully.
[03:58:45] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[03:59:09] + Attempting to get work packet
[03:59:09] Passkey found
[03:59:09] - Connecting to assignment server
[03:59:10] - Successful: assigned to (171.67.108.22).
[03:59:10] + News From Folding@Home: Welcome to Folding@Home
[03:59:10] Loaded queue successfully.
[03:59:22] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[03:59:54] + Attempting to get work packet
[03:59:54] Passkey found
[03:59:54] - Connecting to assignment server
[03:59:55] - Successful: assigned to (171.67.108.22).
[03:59:55] + News From Folding@Home: Welcome to Folding@Home
[03:59:55] Loaded queue successfully.
[04:00:06] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[04:00:50] + Attempting to get work packet
[04:00:50] Passkey found
[04:00:50] - Connecting to assignment server
[04:00:51] - Successful: assigned to (171.67.108.22).
[04:00:51] + News From Folding@Home: Welcome to Folding@Home
[04:00:51] Loaded queue successfully.
[04:01:03] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[04:02:25] + Attempting to get work packet
[04:02:25] Passkey found
[04:02:25] - Connecting to assignment server
[04:02:27] - Successful: assigned to (171.67.108.22).
[04:02:27] + News From Folding@Home: Welcome to Folding@Home
[04:02:27] Loaded queue successfully.
[04:02:38] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[04:05:31] + Attempting to get work packet
[04:05:31] Passkey found
[04:05:31] - Connecting to assignment server
[04:05:32] - Successful: assigned to (171.67.108.22).
[04:05:32] + News From Folding@Home: Welcome to Folding@Home
[04:05:32] Loaded queue successfully.
[04:05:43] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[04:11:13] + Attempting to get work packet
[04:11:13] Passkey found
[04:11:13] - Connecting to assignment server
[04:11:14] - Successful: assigned to (171.67.108.22).
[04:11:14] + News From Folding@Home: Welcome to Folding@Home
[04:11:14] Loaded queue successfully.
[04:11:26] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[04:22:12] + Attempting to get work packet
[04:22:12] Passkey found
[04:22:12] - Connecting to assignment server
[04:22:14] - Successful: assigned to (171.67.108.22).
[04:22:14] + News From Folding@Home: Welcome to Folding@Home
[04:22:14] Loaded queue successfully.
[04:22:25] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[04:43:45] + Attempting to get work packet
[04:43:45] Passkey found
[04:43:45] - Connecting to assignment server
[04:43:46] - Successful: assigned to (171.67.108.22).
[04:43:46] + News From Folding@Home: Welcome to Folding@Home
[04:43:46] Loaded queue successfully.
[04:43:58] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
[05:29:53] + Attempting to get work packet
[05:29:53] Passkey found
[05:29:53] - Connecting to assignment server
[05:29:54] - Successful: assigned to (171.67.108.22).
[05:29:54] + News From Folding@Home: Welcome to Folding@Home
[05:29:54] Loaded queue successfully.
[05:30:04] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.
[06:21:12] + Attempting to get work packet
[06:21:12] Passkey found
[06:21:12] - Connecting to assignment server
[06:21:13] - Successful: assigned to (171.67.108.22).
[06:21:13] + News From Folding@Home: Welcome to Folding@Home
[06:21:13] Loaded queue successfully.
[06:21:24] - Attempt #12 to get work failed, and no other work to do.
Waiting before retry.
[07:11:36] + Attempting to get work packet
[07:11:36] Passkey found
[07:11:36] - Connecting to assignment server
[07:11:37] - Successful: assigned to (171.67.108.22).
[07:11:37] + News From Folding@Home: Welcome to Folding@Home
[07:11:37] Loaded queue successfully.
[07:11:45] - Attempt #13 to get work failed, and no other work to do.
Waiting before retry.
[07:59:57] + Attempting to get work packet
[07:59:57] Passkey found
[07:59:57] - Connecting to assignment server
[07:59:58] - Successful: assigned to (171.67.108.22).
[07:59:58] + News From Folding@Home: Welcome to Folding@Home
[07:59:59] Loaded queue successfully.
[08:00:11] - Attempt #14 to get work failed, and no other work to do.
Waiting before retry.
[08:48:19] + Attempting to get work packet
[08:48:19] Passkey found
[08:48:19] - Connecting to assignment server
[08:48:21] - Successful: assigned to (171.67.108.22).
[08:48:21] + News From Folding@Home: Welcome to Folding@Home
[08:48:21] Loaded queue successfully.
[08:48:32] - Attempt #15 to get work failed, and no other work to do.
Waiting before retry.
[09:36:36] + Attempting to get work packet
[09:36:36] Passkey found
[09:36:36] - Connecting to assignment server
[09:36:37] - Successful: assigned to (171.67.108.22).
[09:36:37] + News From Folding@Home: Welcome to Folding@Home
[09:36:37] Loaded queue successfully.
[09:36:49] - Attempt #16 to get work failed, and no other work to do.
Waiting before retry.
[10:24:53] + Attempting to get work packet
[10:24:53] Passkey found
[10:24:53] - Connecting to assignment server
[10:24:54] - Successful: assigned to (171.67.108.22).
[10:24:54] + News From Folding@Home: Welcome to Folding@Home
[10:24:54] Loaded queue successfully.
[10:25:05] - Attempt #17 to get work failed, and no other work to do.
Waiting before retry.
[11:13:09] + Attempting to get work packet
[11:13:09] Passkey found
[11:13:09] - Connecting to assignment server
[11:13:10] - Successful: assigned to (171.67.108.22).
[11:13:10] + News From Folding@Home: Welcome to Folding@Home
[11:13:10] Loaded queue successfully.
[11:13:23] - Attempt #18 to get work failed, and no other work to do.
Waiting before retry.
[12:01:33] + Attempting to get work packet
[12:01:33] Passkey found
[12:01:33] - Connecting to assignment server
[12:01:35] - Successful: assigned to (171.67.108.22).
[12:01:35] + News From Folding@Home: Welcome to Folding@Home
[12:01:35] Loaded queue successfully.
[12:01:47] - Attempt #19 to get work failed, and no other work to do.
Waiting before retry.
[12:49:59] + Attempting to get work packet
[12:49:59] Passkey found
[12:49:59] - Connecting to assignment server
[12:50:00] - Successful: assigned to (171.67.108.22).
[12:50:00] + News From Folding@Home: Welcome to Folding@Home
[12:50:00] Loaded queue successfully.
[12:50:09] - Attempt #20 to get work failed, and no other work to do.
Waiting before retry.
[13:38:24] + Attempting to get work packet
[13:38:24] Passkey found
[13:38:24] - Connecting to assignment server
[13:38:25] - Successful: assigned to (171.67.108.22).
[13:38:25] + News From Folding@Home: Welcome to Folding@Home
[13:38:25] Loaded queue successfully.
[13:38:37] - Attempt #21 to get work failed, and no other work to do.
Waiting before retry.
Re: 171.67.108.22
Posted: Tue Jul 20, 2010 2:08 pm
by PantherX
@zetachi: you may want to remove the -local and -forceasm flags as they won't be used by the Client. -local flag's feature is by default used in v6 Clients and SMP2 Core is hard-coded to use advanced CPU calculations.
Have you tried with a different Machine ID?
Re: 171.67.108.22
Posted: Tue Jul 20, 2010 2:09 pm
by kasson
What we see on our side is that the server decides to give you a work unit, starts the send process, and then immediately reports a failure. There are about five users for whom this is happening repeatedly; the rest of the assigns appear to be successful.
Is this a rig that was getting bigadv work units successfully before? Some obvious things to check are client configuration (work unit size set to big?), firewalls, etc.