Posts by TRuEQ & TuVaLu

21) Message boards : BOINC client : BM .62 strange (Message 48611) Posted 12 Apr 2013 by TRuEQ & TuVaLu Post: And .62 didn't allow me to run 2 Poem tasks when running 1 moowrapper configured in cc_config.xml with exclude. .60 does
22) Message boards : BOINC client : BM .62 strange (Message 48610) Posted 12 Apr 2013 by TRuEQ & TuVaLu Post: My SETI ATI ap tasks that "paused" with no warning has stoped after downgrading from .62 to .60 Sometimes 2 tasks of 6 or 4 tasks of 6 "pauses".
23) Message boards : BOINC client : BM .62 strange (Message 48605) Posted 12 Apr 2013 by TRuEQ & TuVaLu Post: Random stuff like MS essentials stoped working(1 time). BM dies for no reason(1 time). Errors of tasks occour(1 time). Computor freezes)1 time). Small stuff, nothin serious really. But they started to come after 5mins, 15mins and then something else after 20 mins. Always different kind of malfunctions. normally you do a change and then 1 or 2 things start to malfunction. You fix it and the same thing malfunctions. But not here. "Fuzzy stuff". Like if your picture was perfect and then 1 small part of it geys blured like yours. You close picture program and restart it and another small part gets blured. I am now running .60 and "fuzzy stuff" has only occoured once". So computor seems more in shape now.(7.0.60) I will see if "fuzzy stuff" comes back in the next day or so.
24) Message boards : BOINC client : BM .62 strange (Message 48596) Posted 12 Apr 2013 by TRuEQ & TuVaLu Post: I ran .62 and computor BM and stuff started to give strange fuzzy stuff in respons. I do run SETI Beta as well. I have done driver change for graphic card as well. So I decided to go back to 7.0.60 and use the "old" newer cat driver 12.8 to see if random fuzzy stuff with computor starts to work again. This is just a note, not a report. Any one else seen strange random fuzzy things when going to .62 from .60 ??
25) Message boards : BOINC client : Bm counters stops for about 1min and then resumes. Any ideas? (Message 48581) Posted 10 Apr 2013 by TRuEQ & TuVaLu Post: Now when I returned to my computor. BM had exited.... I've started it again...
26) Message boards : BOINC client : Bm counters stops for about 1min and then resumes. Any ideas? (Message 48576) Posted 10 Apr 2013 by TRuEQ & TuVaLu Post: I've been seeing that, on and off, for two years at least. I put it down to the new Windows laptop I bought then, rather than any particular version of BOINC. Well, it was new to me. Only hapend when runing seti Mb ati tasks with a low period iteration number. about 5. But that was when new tasks where started tasks made BM counters freeze. What I experienced here is more random. Not "connected" to task routines. running 7.0.62 now.
27) Message boards : BOINC client : Bm counters stops for about 1min and then resumes. Any ideas? (Message 48574) Posted 10 Apr 2013 by TRuEQ & TuVaLu Post: Something strange happend now. All tasks in BM stoped counting in progres meter including 1 docking task and 1 wu-prop task. 1 SETI beta was at 92% when the "clock" stoped. And the task was completed when the "clock" started to count again. And a new task was at 9%. Windows Gui worked and SIV showed that all 3 GPU's was running. A bit strange.....Might be BM 7.0.60, I dunno. ideas anyone?? Hapend again after 20mins. All BM counters stoped for about 1min and then resumed. Win GUI works and SIV reports activity on all cpu and gpu's. Ideas anyone??
28) Message boards : BOINC client : Cpu project asks for ATI work? (Message 48199) Posted 14 Mar 2013 by TRuEQ & TuVaLu Post: It's not the project asking for work, it's BOINC that does so. The standard scheduler will ask for available work for GPU (Nvidia, ATI or intel_gpu) and CPU. In the case the project does not have a GPU application, BOINC will still ask for work, because for all it knows the project could decide to release a GPU application tomorrow and then the user won't have to do anything about getting work for it. It'll be done automatically. If well and truly left alone (aka you not doing manual Updates), the GPU work request will eventually back off until it's only done once every 24 hours. When you see ATI work requests, then this usually means that the project already has an Nvidia application. ok, thanks.
29) Message boards : BOINC client : project is not highest priority... (Message 48195) Posted 13 Mar 2013 by TRuEQ & TuVaLu Post: BM .56 asks for work in a more aggressive way. Looks promising.
30) Message boards : BOINC client : I can't believe I am the only one..... (Message 48194) Posted 13 Mar 2013 by TRuEQ & TuVaLu Post: BM .56 asks for work in a more aggressive way. Looks promising.
31) Message boards : BOINC client : Cpu project asks for ATI work? (Message 48193) Posted 13 Mar 2013 by TRuEQ & TuVaLu Post: Why does a project like Docking ask for ATI work? It doesn't have an option in it's preferences? The same with Edges. Edges has: Use Graphics Processing Unit (GPU) if available no in prefs.
32) Message boards : BOINC client : I can't believe I am the only one..... (Message 48085) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: I should mention resource set. SETI 100 MooWrapper 80 and avg work done is. Moowrapper 419000 SETI is 12200 Scheduling prio is Moowrapper 0.71 Seti 1.00 I'm not making sense of this either. since MooWrapper is alot higher RAC then SETI and SETI is alot lower RAC then SETI should ask for alot more work.... I thought this numbers might be of intrest as well. Post the Resource Share from Boinc of ALL your projects, just because you're only interested in GPU work doesn't mean the other projects resource share don't matter. The scheduling priority Shouldn't be above 0, they should be Negative numbers only, not Positive. Claggy They are negative, my bad. But they can't be positive so it has to be my bad when typing 1.00 instead of -1.00 I need to be more focused on all the details. I've been kind of tired today... I've should have gone to bed early instead.
33) Message boards : BOINC client : I can't believe I am the only one..... (Message 48084) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: I should mention resource set. SETI 100 MooWrapper 80 and avg work done is. Moowrapper 419000 SETI is 12200 Scheduling prio is Moowrapper 0.71 Seti 1.00 I'm not making sense of this either. since MooWrapper is alot higher RAC then SETI and SETI is alot lower RAC then SETI should ask for alot more work.... I thought this numbers might be of intrest as well. Post the Resource Share from Boinc of ALL your projects, just because you're only interested in GPU work doesn't mean the other projects resource share don't matter. The scheduling priority Shouldn't be above 0, they should be Negative numbers only, not Positive. Claggy I run WU-prop as well, but that is an NCI project and it looks to me that boinc treats it like NCI Wu-prop is also set to 100 in resource share.
34) Message boards : BOINC client : I can't believe I am the only one..... (Message 48083) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: Another thought. Your post at SETI Beta (which is what brought me here), showed your account with just one computer, running BOINC v7.0.52: Computers belonging to TRuEQ & TuVaLu Yet, your work fetch debug log, as posted here, bears no relation to a v7.0.52 log: 06/03/2013 19:35:02 \| \| [work_fetch] ------- start work fetch state ------- 06/03/2013 19:35:02 \| \| [work_fetch] target work buffer: 21600.00 + 3456.00 sec 06/03/2013 19:35:02 \| \| [work_fetch] --- project states --- 06/03/2013 19:35:02 \| Albert@Home \| [work_fetch] REC 1758.593 prio -0.077874 can req work 06/03/2013 19:35:02 \| boincsimap \| [work_fetch] REC 1754.948 prio -0.077447 can req work 06/03/2013 19:35:02 \| BURP \| [work_fetch] REC 31.547 prio -0.000000 can't req work: "no new tasks" requested via Manager 06/03/2013 19:35:02 \| Einstein@Home \| [work_fetch] REC 110688.739 prio -2.456847 can't req work: some task is suspended via Manager 06/03/2013 19:35:02 \| Test4Theory@Home \| [work_fetch] REC 14.628 prio -0.000000 can't req work: "no new tasks" requested via Manager 06/03/2013 19:35:02 \| LHC@home 1.0 \| [work_fetch] REC 207.314 prio -0.000000 can't req work: "no new tasks" requested via Manager 06/03/2013 19:35:02 \| Milkyway@Home \| [work_fetch] REC 71.306 prio -0.000000 can't req work: "no new tasks" requested via Manager 06/03/2013 19:35:02 \| NumberFields@home \| [work_fetch] REC 1757.149 prio -0.078984 can req work 06/03/2013 19:35:02 \| SETI@home \| [work_fetch] REC 148423.132 prio -3.208901 can't req work: scheduler RPC backoff (backoff: 236.87 sec) 06/03/2013 19:35:02 \| SETI@home Beta Test \| [work_fetch] REC 8906.820 prio -0.000000 can't req work: "no new tasks" requested via Manager 06/03/2013 19:35:02 \| GPUGRID \| [work_fetch] REC 159721.068 prio -3.601839 can't req work: "no new tasks" requested via Manager 06/03/2013 19:35:02 \| \| [work_fetch] --- state for CPU --- 06/03/2013 19:35:02 \| \| [work_fetch] shortfall 0.00 nidle 0.00 saturated 27357.91 busy 0.00 06/03/2013 19:35:02 \| Albert@Home \| [work_fetch] fetch share 0.333 06/03/2013 19:35:02 \| boincsimap \| [work_fetch] fetch share 0.333 06/03/2013 19:35:02 \| BURP \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| Einstein@Home \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| Test4Theory@Home \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| LHC@home 1.0 \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| Milkyway@Home \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| NumberFields@home \| [work_fetch] fetch share 0.333 06/03/2013 19:35:02 \| SETI@home \| [work_fetch] fetch share 0.000 (blocked by prefs) 06/03/2013 19:35:02 \| SETI@home Beta Test \| [work_fetch] fetch share 0.000 (blocked by prefs) 06/03/2013 19:35:02 \| GPUGRID \| [work_fetch] fetch share 0.000 (no apps) 06/03/2013 19:35:02 \| \| [work_fetch] --- state for NVIDIA --- 06/03/2013 19:35:02 \| \| [work_fetch] shortfall 11020.86 nidle 0.00 saturated 13847.86 busy 0.00 06/03/2013 19:35:02 \| Albert@Home \| [work_fetch] fetch share 0.000 (blocked by prefs) 06/03/2013 19:35:02 \| boincsimap \| [work_fetch] fetch share 0.000 (no apps) 06/03/2013 19:35:02 \| BURP \| [work_fetch] fetch share 0.000 (no apps) 06/03/2013 19:35:02 \| Einstein@Home \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| Test4Theory@Home \| [work_fetch] fetch share 0.000 (no apps) 06/03/2013 19:35:02 \| LHC@home 1.0 \| [work_fetch] fetch share 0.000 (no apps) 06/03/2013 19:35:02 \| Milkyway@Home \| [work_fetch] fetch share 0.000 (blocked by prefs) (no apps) 06/03/2013 19:35:02 \| NumberFields@home \| [work_fetch] fetch share 0.000 (no apps) 06/03/2013 19:35:02 \| SETI@home \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| SETI@home Beta Test \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| GPUGRID \| [work_fetch] fetch share 0.000 06/03/2013 19:35:02 \| \| [work_fetch] ------- end work fetch state ------- So, what version are you logging here? I am sorry. It is 7.0.28 here But I ran .52 some days ago and the problem is the same. When I saw this in .52 I abandone it and started to run .28 again. Then I see that there is the same problem in .28 and it is a leftover from the start of 7.0.3 It is like creating something that takes 48hours but after 15mins you create a "malfunction" and compensates yet it still needs more compenstation the longer the process continues. I from a user perspective suspects that there is something created early in the making of the REC based work fetch priority. I feel terribly stupid not to mention I went back to .28
35) Message boards : BOINC client : I can't believe I am the only one..... (Message 48080) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: And my cc_config.xml file. <cc_config> <options> <http_transfer_timeout>60</http_transfer_timeout> <report_results_immediately>1</report_results_immediately> <exclude_gpu> <url>http://moowrap.net/</url> <device_num>1</device_num> </exclude_gpu> <exclude_gpu> <url>http://moowrap.net/</url> <device_num>2</device_num> </exclude_gpu> <exclude_gpu> <url>http://setiathome.berkeley.edu</url> <device_num>0</device_num> </exclude_gpu> <max_file_xfers>24</max_file_xfers> <max_file_xfers_per_project>20</max_file_xfers_per_project> </options> </cc_config>
36) Message boards : BOINC client : I can't believe I am the only one..... (Message 48079) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: I should mention resource set. SETI 100 MooWrapper 80 and avg work done is. Moowrapper 419000 SETI is 12200 Scheduling prio is Moowrapper 0.71 Seti 1.00 I'm not making sense of this either. since MooWrapper is alot higher RAC then SETI and SETI is alot lower RAC then SETI should ask for alot more work.... I thought this numbers might be of intrest as well.
37) Message boards : BOINC client : I can't believe I am the only one..... (Message 48076) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: I hope you can make some sence from this. 2013-03-06 19:19:51 \| Moo! Wrapper \| Scheduler request completed 2013-03-06 19:37:42 \| \| Re-reading cc_config.xml 2013-03-06 19:37:42 \| \| Config: report completed tasks immediately 2013-03-06 19:37:42 \| Moo! Wrapper \| Config: excluded GPU. Type: all. App: all. Device: 1 2013-03-06 19:37:42 \| Moo! Wrapper \| Config: excluded GPU. Type: all. App: all. Device: 2 2013-03-06 19:37:42 \| SETI@home \| Config: excluded GPU. Type: all. App: all. Device: 0 2013-03-06 19:37:42 \| \| log flags: file_xfer, sched_ops, task, work_fetch_debug 2013-03-06 19:37:42 \| \| [work_fetch] Request work fetch: Core client configuration 2013-03-06 19:37:46 \| \| [work_fetch] work fetch start 2013-03-06 19:37:46 \| \| [work_fetch] ------- start work fetch state ------- 2013-03-06 19:37:46 \| \| [work_fetch] target work buffer: 172800.00 + 864.00 sec 2013-03-06 19:37:46 \| Moo! Wrapper \| [work_fetch] REC 76020.674 priority -0.800567 2013-03-06 19:37:46 \| SETI@home \| [work_fetch] REC 139380.804 priority -1.165058 2013-03-06 19:37:46 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:37:46 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:37:46 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:37:46 \| \| [work_fetch] ATI: shortfall 511597.01 nidle 1.00 saturated 0.00 busy 0.00 2013-03-06 19:37:46 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 0.444 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:37:46 \| SETI@home \| [work_fetch] ATI: fetch share 0.556 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:37:46 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:37:46 \| \| [work_fetch] No project chosen for work fetch Yes, that you don't know the meaning of "one iteration only". OK, I'll have a think. Thank you very much.
38) Message boards : BOINC client : I can't believe I am the only one..... (Message 48075) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: This is how it has been the last 24hours. Getting 3-6 new ap tasks running them until none is left. asking for new tasks. getting 3-6 tasks running them. and so on. Moo is like running out of tasks. getting 131 new tasks running them until out of getting 131 new running them and so on.
39) Message boards : BOINC client : I can't believe I am the only one..... (Message 48073) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: And this is how it looks in log when seti is out of work. I got me 6 more. 2013-03-06 19:57:36 \| SETI@home \| [work_fetch] REC 139712.101 priority -1.163268 2013-03-06 19:57:36 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:57:36 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:57:36 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:57:36 \| \| [work_fetch] ATI: shortfall 513912.43 nidle 1.50 saturated 0.00 busy 0.00 2013-03-06 19:57:36 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 0.444 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:57:36 \| SETI@home \| [work_fetch] ATI: fetch share 0.556 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:57:36 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:57:36 \| \| [work_fetch] No project chosen for work fetch 2013-03-06 19:58:29 \| \| [work_fetch] Request work fetch: application exited 2013-03-06 19:58:29 \| SETI@home \| Computation for task ap_25my12ac_B6_P1_00278_20130305_31423.wu_1 finished 2013-03-06 19:58:31 \| SETI@home \| Started upload of ap_25my12ac_B6_P1_00278_20130305_31423.wu_1_0 2013-03-06 19:58:32 \| \| [work_fetch] work fetch start 2013-03-06 19:58:32 \| \| [work_fetch] set_request(): ninst 3 nused_total 0.000000 nidle_now 2.000000 fetch share 0.555556 req_inst 1.111111 2013-03-06 19:58:32 \| \| [work_fetch] ------- start work fetch state ------- 2013-03-06 19:58:32 \| \| [work_fetch] target work buffer: 172800.00 + 864.00 sec 2013-03-06 19:58:32 \| Moo! Wrapper \| [work_fetch] REC 76502.055 priority -0.801640 2013-03-06 19:58:32 \| SETI@home \| [work_fetch] REC 139721.248 priority -1.163141 2013-03-06 19:58:32 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:58:32 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:58:32 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:58:32 \| \| [work_fetch] ATI: shortfall 513951.95 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:58:32 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 0.444 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:58:32 \| SETI@home \| [work_fetch] ATI: fetch share 0.556 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:58:32 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:58:32 \| SETI@home \| [work_fetch] deferring work fetch; upload active 2013-03-06 19:58:35 \| SETI@home \| Finished upload of ap_25my12ac_B6_P1_00278_20130305_31423.wu_1_0 2013-03-06 19:58:35 \| \| [work_fetch] Request work fetch: project finished uploading 2013-03-06 19:58:37 \| \| [work_fetch] work fetch start 2013-03-06 19:58:37 \| \| [work_fetch] set_request(): ninst 3 nused_total 0.000000 nidle_now 2.000000 fetch share 0.555556 req_inst 1.111111 2013-03-06 19:58:37 \| \| [work_fetch] ------- start work fetch state ------- 2013-03-06 19:58:37 \| \| [work_fetch] target work buffer: 172800.00 + 864.00 sec 2013-03-06 19:58:37 \| Moo! Wrapper \| [work_fetch] REC 76502.055 priority -0.801641 2013-03-06 19:58:37 \| SETI@home \| [work_fetch] REC 139721.248 priority -1.163141 2013-03-06 19:58:37 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:58:37 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:58:37 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:58:37 \| \| [work_fetch] ATI: shortfall 513951.42 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:58:37 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 0.444 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:58:37 \| SETI@home \| [work_fetch] ATI: fetch share 0.556 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:58:37 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:58:37 \| SETI@home \| [work_fetch] request: CPU (0.00 sec, 0.00 inst) ATI (513951.42 sec, 1.11 inst) 2013-03-06 19:58:37 \| SETI@home \| Sending scheduler request: To report completed tasks. 2013-03-06 19:58:37 \| SETI@home \| Reporting 1 completed tasks, requesting new tasks for ATI 2013-03-06 19:58:49 \| SETI@home \| Scheduler request completed: got 6 new tasks 2013-03-06 19:58:49 \| \| [work_fetch] Request work fetch: RPC complete 2013-03-06 19:58:52 \| SETI@home \| Started download of ap_06my12ae_B1_P1_00352_20130302_19488.wu 2013-03-06 19:58:52 \| SETI@home \| Started download of ap_03my12ab_B2_P1_00007_20130302_24164.wu 2013-03-06 19:58:52 \| SETI@home \| Started download of ap_26jn12aa_B1_P0_00273_20130306_03174.wu 2013-03-06 19:58:52 \| SETI@home \| Started download of ap_26jl12ac_B2_P0_00189_20130306_07402.wu 2013-03-06 19:58:52 \| SETI@home \| Started download of ap_26jl12aa_B6_P0_00080_20130306_11200.wu 2013-03-06 19:58:52 \| SETI@home \| Started download of ap_26jl12ac_B2_P0_00188_20130306_07402.wu 2013-03-06 19:58:55 \| \| [work_fetch] work fetch start 2013-03-06 19:58:55 \| \| [work_fetch] ------- start work fetch state ------- 2013-03-06 19:58:55 \| \| [work_fetch] target work buffer: 172800.00 + 864.00 sec 2013-03-06 19:58:55 \| Moo! Wrapper \| [work_fetch] REC 76502.055 priority -1.005531 2013-03-06 19:58:55 \| SETI@home \| [work_fetch] REC 139721.248 priority -1.506896 (project backoff 297.81) 2013-03-06 19:58:55 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:58:55 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:58:55 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:58:55 \| \| [work_fetch] ATI: shortfall 502079.99 nidle 1.00 saturated 0.00 busy 0.00 2013-03-06 19:58:55 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 1.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:58:55 \| SETI@home \| [work_fetch] ATI: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:58:55 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:58:55 \| \| [work_fetch] No project chosen for work fetch 2013-03-06 19:59:04 \| \| [work_fetch] Request work fetch: application exited 2013-03-06 19:59:04 \| Moo! Wrapper \| Computation for task dnetc_r72_1362408967_13_823_0 finished 2013-03-06 19:59:04 \| Moo! Wrapper \| Starting task dnetc_r72_1362315235_13_823_1 using dnetc version 103 (ati14) in slot 0 2013-03-06 19:59:05 \| \| [work_fetch] work fetch start 2013-03-06 19:59:05 \| \| [work_fetch] ------- start work fetch state ------- 2013-03-06 19:59:05 \| \| [work_fetch] target work buffer: 172800.00 + 864.00 sec 2013-03-06 19:59:05 \| Moo! Wrapper \| [work_fetch] REC 76530.966 priority -1.005478 2013-03-06 19:59:05 \| SETI@home \| [work_fetch] REC 139717.354 priority -1.590465 (project backoff 287.54) 2013-03-06 19:59:05 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:59:05 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:59:05 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:59:05 \| \| [work_fetch] ATI: shortfall 502147.46 nidle 1.00 saturated 0.00 busy 0.00 2013-03-06 19:59:05 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 1.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:59:05 \| SETI@home \| [work_fetch] ATI: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:59:05 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:59:05 \| \| [work_fetch] No project chosen for work fetch 2013-03-06 19:59:06 \| Moo! Wrapper \| Started upload of dnetc_r72_1362408967_13_823_0_0 2013-03-06 19:59:07 \| Moo! Wrapper \| Finished upload of dnetc_r72_1362408967_13_823_0_0 2013-03-06 19:59:07 \| \| [work_fetch] Request work fetch: project finished uploading 2013-03-06 19:59:10 \| \| [work_fetch] work fetch start 2013-03-06 19:59:10 \| \| [work_fetch] ------- start work fetch state ------- 2013-03-06 19:59:10 \| \| [work_fetch] target work buffer: 172800.00 + 864.00 sec 2013-03-06 19:59:10 \| Moo! Wrapper \| [work_fetch] REC 76530.966 priority -1.005187 2013-03-06 19:59:10 \| SETI@home \| [work_fetch] REC 139717.354 priority -1.632466 (project backoff 282.39) 2013-03-06 19:59:10 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:59:10 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:59:10 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:59:10 \| \| [work_fetch] ATI: shortfall 502515.54 nidle 1.00 saturated 0.00 busy 0.00 2013-03-06 19:59:10 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 1.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:59:10 \| SETI@home \| [work_fetch] ATI: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:59:10 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:59:10 \| \| [work_fetch] No project chosen for work fetch 2013-03-06 19:59:10 \| Moo! Wrapper \| [work_fetch] request: CPU (0.00 sec, 0.00 inst) ATI (0.00 sec, 0.00 inst) 2013-03-06 19:59:10 \| Moo! Wrapper \| Sending scheduler request: To report completed tasks. 2013-03-06 19:59:10 \| Moo! Wrapper \| Reporting 1 completed tasks, not requesting new tasks 2013-03-06 19:59:12 \| Moo! Wrapper \| Scheduler request completed 2013-03-06 19:59:12 \| \| [work_fetch] Request work fetch: RPC complete 2013-03-06 19:59:17 \| \| [work_fetch] work fetch start 2013-03-06 19:59:17 \| \| [work_fetch] ------- start work fetch state ------- 2013-03-06 19:59:17 \| \| [work_fetch] target work buffer: 172800.00 + 864.00 sec 2013-03-06 19:59:17 \| Moo! Wrapper \| [work_fetch] REC 76530.966 priority -0.005196 (project backoff 55.85) 2013-03-06 19:59:17 \| SETI@home \| [work_fetch] REC 139717.354 priority -0.003237 (project backoff 275.22) 2013-03-06 19:59:17 \| \| [work_fetch] CPU: shortfall 347328.00 nidle 2.00 saturated 0.00 busy 0.00 2013-03-06 19:59:17 \| Moo! Wrapper \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:59:17 \| SETI@home \| [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs) (no apps) 2013-03-06 19:59:17 \| \| [work_fetch] ATI: shortfall 502503.55 nidle 1.00 saturated 0.00 busy 0.00 2013-03-06 19:59:17 \| Moo! Wrapper \| [work_fetch] ATI: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:59:17 \| SETI@home \| [work_fetch] ATI: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 2013-03-06 19:59:17 \| \| [work_fetch] ------- end work fetch state ------- 2013-03-06 19:59:17 \| \| [work_fetch] No project chosen for work fetch
40) Message boards : BOINC client : I can't believe I am the only one..... (Message 48072) Posted 6 Mar 2013 by TRuEQ & TuVaLu Post: I hope you can make some sence from this.

Previous 20 · Next 20

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.