• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

big adv shortage?

F

Filter

[H]F Junkie
Joined
Dec 30, 2001
Messages
9,531
seems i cant pull a big adv lately. yes settings are correct i been pulling the 7508 wu
 
Visiting family so I can't check the farm, but I know there are server issues.
 
Checked my systems logs since 30th August; I got a 7134 earlier today but then got a 6903, server 2 has literally just finished and got a 6903.

Code: 
Server 1;
14:08:46:Unit 00:Project: 6900 (Run 46, Clone 4, Gen 23)
01:14:46:Unit 01:Project: 6900 (Run 24, Clone 11, Gen 34)
11:36:01:Unit 00:Project: 6900 (Run 4, Clone 0, Gen 30)
21:56:55:Unit 01:Project: 6904 (Run 0, Clone 24, Gen 16)
06:28:26:Unit 00:Project: 6904 (Run 1, Clone 43, Gen 3)
14:52:43:Unit 01:Project: 6903 (Run 4, Clone 16, Gen 29)
12:16:42:Unit 00:Project: 7134 (Run 0, Clone 50, Gen 240)
13:44:01:Unit 01:Project: 6903 (Run 5, Clone 5, Gen 27)

Server 2;
15:49:59:Unit 00:Project: 6900 (Run 53, Clone 13, Gen 34)
04:39:56:Unit 01:Project: 6900 (Run 7, Clone 19, Gen 17)
17:09:13:Unit 00:Project: 6900 (Run 28, Clone 19, Gen 7)
04:43:59:Unit 01:Project: 6904 (Run 0, Clone 5, Gen 13)
17:21:11:Unit 00:Project: 2689 (Run 8, Clone 8, Gen 133)
05:37:57:Unit 01:Project: 6900 (Run 54, Clone 8, Gen 3)
16:48:00:Unit 00:Project: 6903 (Run 10, Clone 2, Gen 6)
16:22:16:Unit 01:Project: 6903 (Run 0, Clone 13, Gen 29)
 
Last edited:
Just checked for predicted points and found it failed on the HTTP_OK at the end of it sending back the previous WU, then when it retried it said it had got_already and dumped the WU.. I might have just lost all the points.. :mad:

Below is the start of new WU while uploading old results;

Code: 
16:22:16:Unit 01:Project: 6903 (Run 0, Clone 13, Gen 29)
16:22:16:Unit 01:
16:22:16:Unit 01:Assembly optimizations on if available.
16:22:16:Unit 01:Entering M.D.
16:22:21:Unit 00: 11.51%
16:22:24:Unit 01:Mapping NT from 128 to 128
16:22:27:Unit 00: 16.48%
16:22:33:Unit 00: 21.26%
16:22:36:Unit 01:Completed 0 out of 250000 steps  (0%)
16:22:39:Unit 00: 26.17%
16:22:45:Unit 00: 31.11%
16:22:51:Unit 00: 36.07%
16:22:57:Unit 00: 41.00%
16:23:03:Unit 00: 45.95%
16:23:09:Unit 00: 50.89%
16:23:15:Unit 00: 55.81%
16:23:21:Unit 00: 60.76%
16:23:27:Unit 00: 65.68%
16:23:33:Unit 00: 70.59%
16:23:39:Unit 00: 75.54%
16:23:45:Unit 00: 80.47%
16:23:51:Unit 00: 85.35%
16:23:57:Unit 00: 90.28%
16:24:03:Unit 00: 95.27%
16:24:38:WARNING: Exception: Failed to send results to work server: Failed to read response packet: HTTP_OK
16:24:38:Trying to send results to collection server
16:24:38:Unit 00: Uploading 212.17MiB
16:24:38:Connecting to 127.0.0.1:8081
16:24:44:Unit 00: 8.98%
16:24:50:Unit 00: 17.70%
16:24:56:Unit 00: 26.48%
16:25:02:Unit 00: 35.38%
16:25:08:Unit 00: 44.15%
16:25:14:Unit 00: 52.99%
16:25:20:Unit 00: 62.12%
16:25:26:Unit 00: 70.84%
16:25:32:Unit 00: 79.50%
16:25:38:Unit 00: 88.40%
16:25:44:Unit 00: 97.06%
16:25:47:ERROR: Exception: Failed to read response packet: HTTP_OK
16:25:48:Sending unit results: id:00 state:SEND project:6903 run:10 clone:2 gen:6 core:0xa5 unit:0x0000000752be746d4de929ead106f18d
16:25:48:Unit 00: Uploading 212.17MiB
16:25:48:Connecting to 127.0.0.1:8081
16:25:54:Unit 00: 6.90%
16:26:00:Unit 00: 11.58%
16:26:06:Unit 00: 16.27%
16:26:12:Unit 00: 20.98%
16:26:18:Unit 00: 25.82%
16:26:24:Unit 00: 30.66%
16:26:30:Unit 00: 35.51%
16:26:36:Unit 00: 40.35%
16:26:42:Unit 00: 45.18%
16:26:48:Unit 00: 50.02%
16:26:54:Unit 00: 54.86%
16:27:00:Unit 00: 59.70%
16:27:06:Unit 00: 64.55%
16:27:12:Unit 00: 69.38%
16:27:18:Unit 00: 74.25%
16:27:24:Unit 00: 79.09%
16:27:30:Unit 00: 83.96%
16:27:36:Unit 00: 88.80%
16:27:42:Unit 00: 93.64%
16:27:48:Unit 00: 98.51%
16:27:53:Unit 00: Upload complete
16:27:53:Server responded GOT_ALREADY (434)
16:27:53:WARNING: Server did not like results, dumping
 
SF is having issue with server 130.x.x.x ... I think they pulled it off...
However, it seems bigadv smp clients under Linux (Ubuntu or VM) are still able to pull bigadv WUs.
 
p6903 and p6904 are unaffected, but no other bigadv units are being issued and 130.237.232.141 is not accepting results.
I guess that is their way of saying go big or go home.
 
130.237.165.141 not accepting results either for my 2600k.
It just pulled down a regular SMP unit after failing to send my BigAdv 4 times so far.
 
odd, because i dropped a 6900 at ~4AM est today, ad picked up a 2684 at the same time...

KMac said:
p6903 and p6904 are unaffected, but no other bigadv units are being issued and 130.237.232.141 is not accepting results.
I guess that is their way of saying go big or go home.
Click to expand...
 
I haven't had trouble getting units, but I couldn't send back the last one I finished.
 
are you guys on linux or windows. im on windows and cant pull one.
 
windows, and not getting bigadv, my 970 has pulled a second SMP WU, few more hours till my 2600K turns in its WU.
 
all my rigs get regular SMP .. even i7 970 gets 6901 and 7135
 
Windows here too. So far, it's run 3 smp units, and still trying to send the bigadv.
 
I currently have at least 3 machines that have bigadv's to send and cannot. I've changed 2 of them to normal SMP for now.
 
The bigadv server for normal bigadv WU's is down for repairs The server that has 6903 and 6904 big bigadv is still running for Linux they had some bugs in the server code and they had to bring the server down to fix them.
 
Folding2 is on normal SMP right now, so I guess there is both a bigadv and bigbeta shortage right now.
 
Had 4 -bigadv back to back on my rigs and now it looks like both are on standard SMP
 
Only had one machine pickup a bigadv today. The other ones have been getting smp.
 
got home and one of my machines had one but was hung so deleted and pulled normal smp.
 
Sounds like it is just the nasty -bigadv that are left in the wild.

I have a 6903 and 6904 on my rig currently.

I hope they get this fixed sometime soon.
 
It seems like bigadv has dried up completely for the time being as both my rigs have been doing nothing but regular smp the entire day.
 
Kendrak said:
Sounds like it is just the nasty -bigadv that are left in the wild.

I have a 6903 and 6904 on my rig currently.

I hope they get this fixed sometime soon.
Click to expand...

The 6903 and 6904 server is not supposed to be affected. It should still be giving out bigadv WU's to 12 core Linux rigs.
 
Here's the thing, on my machines i get nearly the same PPD on SMP as I do on Bigadv:confused:
 
You must log in or register to reply here.
Back
Top