跑SMP和BIGADV12均木有奖励分

muclemanxb

如上图，前前后后加起来跑了20个SMP2了，设置如置顶金版教程，肿么还神马奖励分都没有？SMP的成功率绝对在80％以上了，另外注意daily production里面的05.30.12顺利完成第一个（爆掉的在其后）6901也没看见有奖励分，我X。
求解答，各种解答

wpf999

客户端是什么版本？

passkey是否完全填写正确？

金鹏

回复 1# muclemanxb


    排除成功率问题以外，兄弟确认你的FAH ID是和你的PASSKEY对应的填写无误？特别是和你用FAH ID申请PASSKEY时一致？包括大小写

保险些再以 muclemanxb 申请ASSKEY页面去重发一回

vmzy

应该是成功率问题了。才20个wu，随便失败4个成功率就危险了。
如果你之前暂时退出fah的时候，没把任务算完，或者遇到服务器抽风，任务下载失败，成功率不就低于80%了。
我的成功率不达标就是新任务总是下载失败导致的

muclemanxb

回复 3# 金鹏


    下边这个截图是VB里面WEB配置页面的截图，里面有ID、passkey等等。如下图：

     下边这个是我邮件里面ID和passkey的截图。

     据目测，应该是完全一样的吧，得分都已经加到我ID上了。

金鹏

回复 5# muclemanxb

兄弟剩下的就是V版说的你的成功率没到80%，继续跑几个SMP2包，等有奖励分了再转BA包

muclemanxb

回复 4# vmzy


    这个是上一个包7511结束以后FAH.LOG的内容，上传失败是不是这个意思呢？

1. [20:35:47] Completed 495000 out of 500000 steps (99%)
   
2. [20:40:26] Completed 500000 out of 500000 steps (100%)
   
3. [20:40:26] DynamicWrapper: Finished Work Unit: sleep=10000
   
4. [20:40:36] - Autosending finished units... [June 5 20:40:36 UTC]
   
5. [20:40:36] Trying to send all finished work units
   
6. [20:40:36] + No unsent completed units remaining.
   
7. [20:40:36] - Autosend completed
   
8. [20:40:37]
   
9. [20:40:37] Finished Work Unit:
   
10. [20:40:37] - Reading up to 6296832 from "work/wudata_02.trr": Read 6296832
    
11. [20:40:37] trr file hash check passed.
    
12. [20:40:37] - Reading up to 6752864 from "work/wudata_02.xtc": Read 6752864
    
13. [20:40:37] xtc file hash check passed.
    
14. [20:40:37] edr file hash check passed.
    
15. [20:40:37] logfile size: 323102
    
16. [20:40:37] Leaving Run
    
17. [20:40:37] - Writing 13405202 bytes of core data to disk...
    
18. [20:40:40] Done: 13404690 -> 12782010 (compressed to 95.3 percent)
    
19. [20:40:40] ... Done.
    
20. [20:40:41] - Shutting down core
    
21. [20:40:41]
    
22. [20:40:41] Folding@home Core Shutdown: FINISHED_UNIT
    
23. [20:40:41] CoreStatus = 64 (100)
    
24. [20:40:41] Unit 2 finished with 95 percent of time to deadline remaining.
    
25. [20:40:41] Updated performance fraction: 0.947967
    
26. [20:40:41] Sending work to server
    
27. [20:40:41] Project: 7511 (Run 0, Clone 147, Gen 214)
    
28. 
    
29. 
    
30. [20:40:41] + Attempting to send results [June 5 20:40:41 UTC]
    
31. [20:40:41] - Reading file work/wuresults_02.dat from core
    
32. [20:40:41] (Read 12782522 bytes from disk)
    
33. [20:40:41] Connecting to http://128.143.199.97:8080/
    
34. [20:40:41] - Couldn't send HTTP request to server
    
35. [20:40:41] + Could not connect to Work Server (results)
    
36. [20:40:41] (128.143.199.97:8080)
    
37. [20:40:41] + Retrying using alternative port
    
38. [20:40:41] Connecting to http://128.143.199.97:80/
    
39. [20:40:41] - Couldn't send HTTP request to server
    
40. [20:40:41] + Could not connect to Work Server (results)
    
41. [20:40:41] (128.143.199.97:80)
    
42. [20:40:41] - Error: Could not transmit unit 02 (completed June 5) to work server.
    
43. [20:40:41] - 1 failed uploads of this unit.
    
44. [20:40:41] Keeping unit 02 in queue.
    
45. [20:40:41] Trying to send all finished work units
    
46. [20:40:41] Project: 7511 (Run 0, Clone 147, Gen 214)
    
47. 
    
48. 
    
49. [20:40:41] + Attempting to send results [June 5 20:40:41 UTC]
    
50. [20:40:41] - Reading file work/wuresults_02.dat from core
    
51. [20:40:41] (Read 12782522 bytes from disk)
    
52. [20:40:41] Connecting to http://128.143.199.97:8080/
    
53. [20:40:41] - Couldn't send HTTP request to server
    
54. [20:40:41] + Could not connect to Work Server (results)
    
55. [20:40:41] (128.143.199.97:8080)
    
56. [20:40:41] + Retrying using alternative port
    
57. [20:40:41] Connecting to http://128.143.199.97:80/
    
58. [20:40:41] - Couldn't send HTTP request to server
    
59. [20:40:41] + Could not connect to Work Server (results)
    
60. [20:40:41] (128.143.199.97:80)
    
61. [20:40:41] - Error: Could not transmit unit 02 (completed June 5) to work server.
    
62. [20:40:41] - 2 failed uploads of this unit.
    
63. 
    
64. 
    
65. [20:40:41] + Attempting to send results [June 5 20:40:41 UTC]
    
66. [20:40:41] - Reading file work/wuresults_02.dat from core
    
67. [20:40:41] (Read 12782522 bytes from disk)
    
68. [20:40:41] Connecting to http://128.143.231.202:8080/
    
69. [20:40:41] - Couldn't send HTTP request to server
    
70. [20:40:41] + Could not connect to Work Server (results)
    
71. [20:40:41] (128.143.231.202:8080)
    
72. [20:40:41] + Retrying using alternative port
    
73. [20:40:41] Connecting to http://128.143.231.202:80/
    
74. [20:40:41] - Couldn't send HTTP request to server
    
75. [20:40:41] + Could not connect to Work Server (results)
    
76. [20:40:41] (128.143.231.202:80)
    
77. [20:40:41] Could not transmit unit 02 to Collection server; keeping in queue.
    
78. [20:40:41] + Sent 0 of 1 completed units to the server
    
79. [20:40:41] - Preparing to get new work unit...
    
80. [20:40:41] Cleaning up work directory
    
81. [20:40:41] + Attempting to get work packet
    
82. [20:40:41] Passkey found
    
83. [20:40:41] - Will indicate memory of 3022 MB
    
84. [20:40:41] - Connecting to assignment server
    
85. [20:40:41] Connecting to http://assign.stanford.edu:8080/
    
86. [20:40:43] Posted data.
    
87. [20:40:43] Initial: 8F80; - Successful: assigned to (128.143.231.202).
    
88. [20:40:43] + News From Folding@Home: Welcome to Folding@Home
    
89. [20:40:43] Loaded queue successfully.
    
90. [20:40:43] Sent data
    
91. [20:40:43] Connecting to http://128.143.231.202:8080/
    
92. [20:40:44] Posted data.
    
93. [20:40:44] Initial: 0000; - Receiving payload (expected size: 3811480)
    
94. [20:41:16] - Downloaded at ~116 kB/s
    
95. [20:41:16] - Averaged speed for that direction ~96 kB/s
    
96. [20:41:16] + Received work.
    
97. [20:41:16] Trying to send all finished work units
    
98. [20:41:16] Project: 7511 (Run 0, Clone 147, Gen 214)
    
99. 
    
100. 
     
101. [20:41:16] + Attempting to send results [June 5 20:41:16 UTC]
     
102. [20:41:16] - Reading file work/wuresults_02.dat from core
     
103. [20:41:16] (Read 12782522 bytes from disk)
     
104. [20:41:16] Connecting to http://128.143.199.97:8080/
     
105. [20:41:16] - Couldn't send HTTP request to server
     
106. [20:41:16] + Could not connect to Work Server (results)
     
107. [20:41:16] (128.143.199.97:8080)
     
108. [20:41:16] + Retrying using alternative port
     
109. [20:41:16] Connecting to http://128.143.199.97:80/
     
110. [20:41:16] - Couldn't send HTTP request to server
     
111. [20:41:16] + Could not connect to Work Server (results)
     
112. [20:41:16] (128.143.199.97:80)
     
113. [20:41:16] - Error: Could not transmit unit 02 (completed June 5) to work server.
     
114. [20:41:16] - 3 failed uploads of this unit.
     
115. 
     
116. 
     
117. [20:41:16] + Attempting to send results [June 5 20:41:16 UTC]
     
118. [20:41:16] - Reading file work/wuresults_02.dat from core
     
119. [20:41:16] (Read 12782522 bytes from disk)
     
120. [20:41:16] Connecting to http://128.143.231.202:8080/
     
121. [20:41:16] - Couldn't send HTTP request to server
     
122. [20:41:16] + Could not connect to Work Server (results)
     
123. [20:41:16] (128.143.231.202:8080)
     
124. [20:41:16] + Retrying using alternative port
     
125. [20:41:16] Connecting to http://128.143.231.202:80/
     
126. [20:41:16] - Couldn't send HTTP request to server
     
127. [20:41:16] + Could not connect to Work Server (results)
     
128. [20:41:16] (128.143.231.202:80)
     
129. [20:41:16] Could not transmit unit 02 to Collection server; keeping in queue.
     
130. [20:41:16] + Sent 0 of 1 completed units to the server
     
131. [20:41:16] + Closed connections
     

复制代码

这个是代理Langouste  De-coupler日志，对应上一个包7511上传情况，看这个架势

1. ue Jun 5 20:40:41 2012 Accepted connection from: 127.0.0.1:53683
   
2. Tue Jun 5 20:40:41 2012 PID for socket: 765
   
3. Tue Jun 5 20:40:41 2012 PID 765: issending: 0
   
4. Tue Jun 5 20:40:41 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
   
5. Tue Jun 5 20:40:41 2012 ===> Helper pid: -1
   
6. Tue Jun 5 20:40:41 2012 ===> PID 765: numcores: 0
   
7. Tue Jun 5 20:40:41 2012 ===> now: 1338928841, last helper launched at: 1338900934
   
8. Tue Jun 5 20:40:41 2012 ===> Launching helper: '/proc/765/cwd/langouste-helper.sh' (exe name: '/usr/local/fah/fah6')...
   
9. Tue Jun 5 20:40:41 2012 ===> Forked 3390
   
10. Tue Jun 5 20:40:41 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
11. Tue Jun 5 20:40:41 2012 Accepted connection from: 127.0.0.1:53684
    
12. Tue Jun 5 20:40:41 2012 PID for socket: 765
    
13. Tue Jun 5 20:40:41 2012 PID 765: issending: 0
    
14. Tue Jun 5 20:40:41 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
15. Tue Jun 5 20:40:41 2012 ===> Helper pid: -1
    
16. Tue Jun 5 20:40:41 2012 ===> PID 765: numcores: 0
    
17. Tue Jun 5 20:40:41 2012 ===> now: 1338928841, last helper launched at: 1338928841
    
18. Tue Jun 5 20:40:41 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
    
19. Tue Jun 5 20:40:41 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
20. Tue Jun 5 20:40:41 2012 Accepted connection from: 127.0.0.1:53685
    
21. Tue Jun 5 20:40:41 2012 PID for socket: 765
    
22. Tue Jun 5 20:40:41 2012 PID 765: issending: 0
    
23. Tue Jun 5 20:40:41 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
24. Tue Jun 5 20:40:41 2012 ===> Helper pid: -1
    
25. Tue Jun 5 20:40:41 2012 ===> PID 765: numcores: 0
    
26. Tue Jun 5 20:40:41 2012 ===> now: 1338928841, last helper launched at: 1338928841
    
27. Tue Jun 5 20:40:41 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
    
28. Tue Jun 5 20:40:41 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
29. Tue Jun 5 20:40:41 2012 Accepted connection from: 127.0.0.1:53686
    
30. Tue Jun 5 20:40:41 2012 PID for socket: 765
    
31. Tue Jun 5 20:40:41 2012 PID 765: issending: 0
    
32. Tue Jun 5 20:40:41 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
33. Tue Jun 5 20:40:41 2012 ===> Helper pid: -1
    
34. Tue Jun 5 20:40:41 2012 ===> PID 765: numcores: 0
    
35. Tue Jun 5 20:40:41 2012 ===> now: 1338928841, last helper launched at: 1338928841
    
36. Tue Jun 5 20:40:41 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
    
37. Tue Jun 5 20:40:41 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
38. Tue Jun 5 20:40:41 2012 Accepted connection from: 127.0.0.1:53687
    
39. Tue Jun 5 20:40:41 2012 PID for socket: 765
    
40. Tue Jun 5 20:40:41 2012 PID 765: issending: 0
    
41. Tue Jun 5 20:40:41 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
42. Tue Jun 5 20:40:41 2012 ===> Helper pid: -1
    
43. Tue Jun 5 20:40:41 2012 ===> PID 765: numcores: 0
    
44. Tue Jun 5 20:40:41 2012 ===> now: 1338928841, last helper launched at: 1338928841
    
45. Tue Jun 5 20:40:41 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
    
46. Tue Jun 5 20:40:41 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
47. Tue Jun 5 20:40:41 2012 Accepted connection from: 127.0.0.1:53688
    
48. Tue Jun 5 20:40:41 2012 PID 3390 (child) exited
    
49. Tue Jun 5 20:40:41 2012 PID for socket: 765
    
50. Tue Jun 5 20:40:41 2012 PID 765: issending: 0
    
51. Tue Jun 5 20:40:41 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
52. Tue Jun 5 20:40:41 2012 ===> Helper pid: -1
    
53. Tue Jun 5 20:40:41 2012 ===> PID 765: numcores: 0
    
54. Tue Jun 5 20:40:41 2012 ===> now: 1338928841, last helper launched at: 1338928841
    
55. Tue Jun 5 20:40:41 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
    
56. Tue Jun 5 20:40:41 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
57. Tue Jun 5 20:40:41 2012 Accepted connection from: 127.0.0.1:53689
    
58. Tue Jun 5 20:40:41 2012 PID for socket: 765
    
59. Tue Jun 5 20:40:41 2012 PID 765: issending: 0
    
60. Tue Jun 5 20:40:41 2012 ===> PID 765 is contacting main assignment server
    
61. Tue Jun 5 20:40:41 2012 (0) resolving 'assign.stanford.edu:8080'
    
62. Tue Jun 5 20:40:42 2012 (0) Connecting to: 171.67.108.200:8080
    
63. Tue Jun 5 20:40:42 2012 (0) Connected.
    
64. Tue Jun 5 20:40:43 2012 (0) Local connection closed (bsize: 0).
    
65. Tue Jun 5 20:40:43 2012 (0) Local: received 559 bytes, sent 396 bytes
    
66. Tue Jun 5 20:40:43 2012 (0) Remote: received 396 bytes, sent 559 bytes
    
67. Tue Jun 5 20:40:43 2012 Accepted connection from: 127.0.0.1:53691
    
68. Tue Jun 5 20:40:43 2012 PID for socket: 765
    
69. Tue Jun 5 20:40:43 2012 PID 765: issending: 0
    
70. Tue Jun 5 20:40:43 2012 ===> PID 765 is (most likely) contacting WU server, content length: 512
    
71. Tue Jun 5 20:40:43 2012 (0) resolving '128.143.231.202:8080'
    
72. Tue Jun 5 20:40:43 2012 (0) Connecting to: 128.143.231.202:8080
    
73. Tue Jun 5 20:40:43 2012 (0) Connected.
    
74. Tue Jun 5 20:41:16 2012 (0) Remote connection closed (rbsize: 0).
    
75. Tue Jun 5 20:41:16 2012 (0) Local: received 631 bytes, sent 3812099 bytes
    
76. Tue Jun 5 20:41:16 2012 (0) Remote: received 3812099 bytes, sent 631 bytes
    
77. Tue Jun 5 20:41:16 2012 Accepted connection from: 127.0.0.1:53693
    
78. Tue Jun 5 20:41:16 2012 PID for socket: 765
    
79. Tue Jun 5 20:41:16 2012 PID 765: issending: 0
    
80. Tue Jun 5 20:41:16 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
81. Tue Jun 5 20:41:16 2012 ===> Helper pid: -1
    
82. Tue Jun 5 20:41:16 2012 ===> PID 765: numcores: 0
    
83. Tue Jun 5 20:41:16 2012 ===> now: 1338928876, last helper launched at: 1338928841
    
84. Tue Jun 5 20:41:16 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
    
85. Tue Jun 5 20:41:16 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
86. Tue Jun 5 20:41:16 2012 Accepted connection from: 127.0.0.1:53694
    
87. Tue Jun 5 20:41:16 2012 PID for socket: 765
    
88. Tue Jun 5 20:41:16 2012 PID 765: issending: 0
    
89. Tue Jun 5 20:41:16 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
90. Tue Jun 5 20:41:16 2012 ===> Helper pid: -1
    
91. Tue Jun 5 20:41:16 2012 ===> PID 765: numcores: 0
    
92. Tue Jun 5 20:41:16 2012 ===> now: 1338928876, last helper launched at: 1338928841
    
93. Tue Jun 5 20:41:16 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
    
94. Tue Jun 5 20:41:16 2012 (0) Local: received 16384 bytes, sent 0 bytes
    
95. Tue Jun 5 20:41:16 2012 Accepted connection from: 127.0.0.1:53695
    
96. Tue Jun 5 20:41:16 2012 PID for socket: 765
    
97. Tue Jun 5 20:41:16 2012 PID 765: issending: 0
    
98. Tue Jun 5 20:41:16 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
    
99. Tue Jun 5 20:41:16 2012 ===> Helper pid: -1
    
100. Tue Jun 5 20:41:16 2012 ===> PID 765: numcores: 0
     
101. Tue Jun 5 20:41:16 2012 ===> now: 1338928876, last helper launched at: 1338928841
     
102. Tue Jun 5 20:41:16 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
     
103. Tue Jun 5 20:41:16 2012 (0) Local: received 16384 bytes, sent 0 bytes
     
104. Tue Jun 5 20:41:16 2012 Accepted connection from: 127.0.0.1:53696
     
105. Tue Jun 5 20:41:16 2012 PID for socket: 765
     
106. Tue Jun 5 20:41:16 2012 PID 765: issending: 0
     
107. Tue Jun 5 20:41:16 2012 ===> PID 765 is (most likely) contacting WU server, content length: 12783034
     
108. Tue Jun 5 20:41:16 2012 ===> Helper pid: -1
     
109. Tue Jun 5 20:41:16 2012 ===> PID 765: numcores: 0
     
110. Tue Jun 5 20:41:16 2012 ===> now: 1338928876, last helper launched at: 1338928841
     
111. Tue Jun 5 20:41:16 2012 ===> WARNING: can only launch one helper in 2 minutes (per client)
     
112. Tue Jun 5 20:41:16 2012 (0) Local: received 16384 bytes, sent 0 bytes
     
113. Tue Jun 5 20:41:42 2012 Accepted connection from: 127.0.0.1:53697
     
114. Tue Jun 5 20:41:42 2012 PID for socket: 3438
     
115. Tue Jun 5 20:41:42 2012 PID 3438: issending: 1
     
116. Tue Jun 5 20:41:42 2012 (0) resolving '128.143.199.97:8080'
     
117. Tue Jun 5 20:41:42 2012 (0) Connecting to: 128.143.199.97:8080
     
118. Tue Jun 5 20:41:42 2012 (0) Connected.
     
119. Tue Jun 5 20:43:33 2012 (0) Remote connection closed (rbsize: 0).
     
120. Tue Jun 5 20:43:33 2012 (0) Local: received 12783156 bytes, sent 615 bytes
     
121. Tue Jun 5 20:43:33 2012 (0) Remote: received 615 bytes, sent 12783156 bytes
     
122. Tue Jun 5 20:43:33 2012 (0) Ratelimit: sent 12783156 byte(s) in 110.928 seconds, 115238 Bps (112.53 kBps)
     

复制代码

muclemanxb

回复 6# 金鹏


    如何判断成功率？到目前位置，印象里面只爆了一个6098（这个大概34％爆掉）和一个6901（99％爆掉，气得我瞬间繁体字）两个包而已～有个疑问是：是不是SMP2没有到成功率又转去跑BA的话，后面要重新计算成功率？

muclemanxb

假如如7楼所列log记录显示的网络问题导致木有奖励分，那这个问题实在不是我能解决了～考虑是不是要转回去跑rosetta、WCG了

wpf999

从日志看，有3个没上传成功，连接服务器失败

zxj-iq180

在跑几天smp2试试，反正也很快，再没有奖励分转战wvg也不晚

Lynt

回复 9# muclemanxb

你的情况跟我很像，可能是网络环境的原因，我不论是虚拟机还是原生Linux，只要开启了同步上传/下载，就是配置页中的 Enable Langouste De-coupler，就会报错无法正常上传结果，你试一下禁用这项看看

金鹏

回复 7# muclemanxb
回复 12# Lynt

开启了代理就不用管FAH.LOG里的提示，只要看代理有就行，上传成功就会在代理日志里看到如下内容

1. Tue Jun 5 20:43:33 2012 (0) Ratelimit: sent 12783156 byte(s) in 110.928 seconds, 115238 Bps (112.53 kBps)

复制代码

muclemanxb

Langouste  De-coupler的日志，我是从上上个包成功上传后开始复制，直到上一个包7511上传结束～就像金版13楼说的

muclemanxb

回复 10# wpf999


    纳尼～是哪一个？FAH还是Langouste  De-coupler的日志？FAH我几乎是经常要失败个4、5次才能上传结束