171.67.108.22

[Michael_McCord,_M.D.]

Same issue as the thread beneath this one exactly...171.67.108.31.

[DrSpalding]

I have a Win SMP 6.29 console client running -bigadv and the server 171.67.108.22 is marked as up and running but is not assigning a WU from 6:44 PDT today when it uploaded a 2684 WU. My machine has been trying for 3+ hours now to get a WU. I am considering running -advmethods instead to get some work to do.

[kasson]

The server is out of windows-capable jobs right now.

[DrSpalding]

Thanks for the update, kasson. Are there any non -bigadv A3 units available via -smp -advmethods?

[PantherX]

I will be completing my bigadv in ~14hrs. I have read that if there aren't any bigadv WUs, the Server will assign -advmethods WUs. Has that been implemented yet?

[DrSpalding]

I will be completing my bigadv in ~14hrs. I have read that if there aren't any bigadv WUs, the Server will assign -advmethods WUs. Has that been implemented yet?

I thought that it should have moved off of the bigadv server too, but it has been my experience that once the assignment server assigns your machine to a particular WU server, it is pretty sticky. It may just take longer than I have patience for though.

I switched to -advmethods and picked up a WU immediately. I'll let it run and check back periodically to see if -bigadv has been repopulated with WUs to distribute.

[kasson]

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.

Edit by Mod:
Changed ".22" above to "Server .22" to avoid the misunderstanding discussed in the next two posts.

[filu]

So, although the core (v.22) has not been tested and is written by the same algorithm as for Linux. That is easier and faster but is it better? Good luck.

[PantherX]

So, although the core (v.22) has not been tested and is written by the same algorithm as for Linux. That is easier and faster but is it better? Good luck.

I think that Dr. Kasson was referring to Server 171.67.108.22 when he stated .22
More info about FahCore_a3 v2.22: (http://en.fah-addict.net/news/news-0-25 ... -linux.php) and (http://en.fah-addict.net/news/news-0-25 ... indows.php)

[hrsetrdr]

The server is out of windows-capable jobs right now.

Ha, looks like my timing is impeccable- I just tore down two Debian installs and switched to Windows to capture some bigadv WUs....

[bruce]

The server is out of windows-capable jobs right now.

Ha, looks like my timing is impeccable- I just tore down two Debian installs and switched to Windows to capture some bigadv WUs....

Well, Kasson already knows about it, and he wants it fixed as much as you do.

[DrSpalding]

Quick update as of 16:00 PDT.

Still no Windows -bigadv WUs to be had. Restarted again back to -advmethods and will check again tomorrow.

[hrsetrdr]

The server is out of windows-capable jobs right now.

Ha, looks like my timing is impeccable- I just tore down two Debian installs and switched to Windows to capture some bigadv WUs....

Well, Kasson already knows about it, and he wants it fixed as much as you do.

Bruce,

I'm not a complainer, but I just feel better after a good cry. I've already gone to "Plan B"(actually "Plan C") as there's bigger WUs to fry.

[PantherX]

My first attempt was unsuccessful but on the second attempt, I was assigned a bigadv. Looks that everything is fixed

[DrSpalding]

I switched over to -bigadv again and it is finishing up a 6702 WU now. I'll know in ~8 hours if I can get going on -bigadv again.