Message boards :
Number crunching :
Moo doesn't start tasks with BM 7.0.8
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 May 11 Posts: 8 Credit: 98,906,368 RAC: 0 |
I resumed Moo yesterday and I got 2 tasks that said "ready to start" in BM But no matter what I did I couldn't get them to start.... What do I do wrong?? All other projects works with my ATI card |
Send message Joined: 5 May 11 Posts: 233 Credit: 351,414,150 RAC: 0 |
Try a Project dettatch/reattatch (not reset), that will send down a freash load of Project files for the current configuration. It should work ok then. Post again if it doesnt. Bare in mind that you are running BAM 7.XX which an Alpha release, so there is a real possibility that wacky things will happen. With Alpha releases life is rarely what it may look like on the surface :) Regards Zy |
Send message Joined: 1 Jan 12 Posts: 13 Credit: 21,324,276 RAC: 0 |
read the app_info thread. |
Send message Joined: 8 Jul 11 Posts: 36 Credit: 3,198,157,199 RAC: 1,774,775 |
i ran 7.0.3 the other day,and could get no work for any project.switched back to 6.12.34 and every thing went back to working fine |
Send message Joined: 2 May 11 Posts: 8 Credit: 98,906,368 RAC: 0 |
Well, I made an app_info.xml that looks like this. <app_info> <app> <name>dnetc</name> <user_friendly_name>Distributed.net Client</user_friendly_name> </app> <file_info> <name>dnetc_1.3_windows_intelx86__ati14.exe</name> <executable/> </file_info> <file_info> <name>dnetc518-win32-x86-stream.exe</name> <executable/> </file_info> <file_info> <name>dnetc-1.00.ini</name> </file_info> <file_info> <name>job-ati14-1.00.xml</name> </file_info> <app_version> <app_name>dnetc</app_name> <version_num>13</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.250</avg_ncpus> <max_ncpus>1.0</max_ncpus> <plan_class>ati14</plan_class> <flops>1157115231469.729200</flops> <api_version>7.0.11</api_version> <file_ref> <file_name>dnetc_1.3_windows_intelx86__ati14.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>dnetc518-win32-x86-stream.exe</file_name> <copy_file/> </file_ref> <file_ref> <file_name>dnetc-1.00.ini</file_name> <open_name>dnetc.ini</open_name> <copy_file/> </file_ref> <file_ref> <file_name>job-ati14-1.00.xml</file_name> <open_name>job.xml</open_name> <copy_file/> </file_ref> <coproc> <type>ATI</type> <count>1.0</count> </coproc> </app_version> </app_info> I tried to get the version numbers right from 1.02 to 1.3 I am not sure that it is correct written. Starting up BM and woooops ....,all the files where gone except from the app.info.xml file. Of course I should have made a backup. Oki, I remove the app_info.xml file and try to reset the project to get back the missing files. No luck. I detach and reattach and hope the files will be downloaded again. No luck. Getting stuck in server backoffs for 2mins in every move I make.... I will try attach again......Hopefully I will get the files.... WORKED!!! Now I will try get the files backedup and see if I can get this to work.... |
Send message Joined: 2 May 11 Posts: 8 Credit: 98,906,368 RAC: 0 |
I got it to work by putting the files in the moowrap folder manually. I also edited my app_info.xml file to this. <app_info> <app> <name>dnetc</name> <user_friendly_name>Distributed.net Client</user_friendly_name> </app> <file_info> <name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</name> <executable/> </file_info> <file_info> <name>dnetc518-win32-x86-stream.exe</name> <executable/> </file_info> <file_info> <name>dnetc-gpu-1.3.ini</name> </file_info> <file_info> <name>job-ati14-1.00.xml</name> </file_info> <app_version> <app_name>dnetc</app_name> <version_num>13</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.250</avg_ncpus> <max_ncpus>1.0</max_ncpus> <plan_class>ati14</plan_class> <flops>1157115231469.729200</flops> <api_version>7.0.11</api_version> <file_ref> <file_name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>dnetc518-win32-x86-stream.exe</file_name> <copy_file/> </file_ref> <file_ref> <file_name>dnetc-gpu-1.3.ini</file_name> <open_name>dnetc.ini</open_name> <copy_file/> </file_ref> <file_ref> <file_name>job-ati14-1.00.xml</file_name> <open_name>job.xml</open_name> <copy_file/> </file_ref> <coproc> <type>ATI</type> <count>1.0</count> </coproc> </app_version> </app_info> I also use this cc_config.xml file to exclude gpu from some projects. <cc_config> <options> <use_all_gpus>1</use_all_gpus> <exclude_gpu> <url>http://albert.phys.uwm.edu</url> <device_num>1</device_num> </exclude_gpu> <exclude_gpu> <url>http://setiathome.berkeley.edu</url> <device_num>1</device_num> </exclude_gpu> <exclude_gpu> <url>http://milkyway.cs.rpi.edu/milkyway/</url> <device_num>1</device_num> </exclude_gpu> <exclude_gpu> <url>http://boinc.fzk.de/poem/</url> <device_num>0</device_num> </exclude_gpu> <exclude_gpu> <url>http://boinc.thesonntags.com/collatz/</url> <device_num>1</device_num> </exclude_gpu> <exclude_gpu> <url>http://moowrap.net/</url> <device_num>1</device_num> </exclude_gpu> <report_results_immediately>1</report_results_immediately> </options> </cc_config> It should make the moowrap use only gpu(0) but it uses both anyhow.... I can't find any where in moowrap preferences to exclude 1 card??!??+ The app_info.xml and the app works perfect on my mix of ATI cards 5850+4850 though |
Send message Joined: 6 Dec 11 Posts: 60 Credit: 306,719,331 RAC: 0 |
To get moowrap to exclude a card I had to use cc_config to exclude a card, allow multiple clients, create another boinc instance and run from command line with the following: c:\boinc\boinc -allow_multple_clients -gui_rpc_port 9999 And then user EmFER's Bionc Manager or switch between computers with the standard manager. |
Send message Joined: 2 May 11 Posts: 8 Credit: 98,906,368 RAC: 0 |
To get moowrap to exclude a card I had to use cc_config to exclude a card, allow multiple clients, create another boinc instance and run from command line with the following: First task completed: http://moowrap.net/results.php?hostid=8559&offset=0&show_names=1&state=3&appid= Ok. I am not in to running 2 BM's at once at present.... But thank you for the tip. I need to get that 4850card excluded since I have a slight heating problem when running Moo at both cards. cc_config.xml and the exclude command didn't help me here. exclude works with SETI, POEM, Albert, Milkyway, Collatz, Primegrid |
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
Well, I made an app_info.xml that looks like this. Looks pretty good, except version could be 103 to get the 1.3 encoded correctly. Although, it's not a big of a deal since that's pretty much used only for statisticial purposes with anonymous platforms. API version for this application is actually 6.13.12 but I'm not entirely sure if a BOINC Client v7 likes such version. It's the major part (6 or 7) that's actually only meaningfull here as that's what BOINC Client seems to verify. It's also only used for in the client end, so whatever makes this work for your system... :) Hmm, I wonder if this v6 vs. v7 major version is what prevents BOINC Client v7 to start these tasks. But that would mean tasks from other projects shouldn't start either. -w |
Send message Joined: 2 May 11 Posts: 8 Credit: 98,906,368 RAC: 0 |
Well, I made an app_info.xml that looks like this. Changes 13 changed to 103 i keep the api version 7.0.11 since it works anyway :) Isn't there any way to let moo use only 1gpu in 1BoincManager? I have 2GPU's and they get warm. |
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
Isn't there any way to let moo use only 1gpu in 1BoincManager? I have 2GPU's and they get warm. Unfortunately, not at the moment as D.net Client that we use is designed to find and use every GPU it can find on the system. However, there has been some progress lately upstream so we might be able to support normal one GPU per one task in the future. -w |
Send message Joined: 2 May 11 Posts: 8 Credit: 98,906,368 RAC: 0 |
Isn't there any way to let moo use only 1gpu in 1BoincManager? I have 2GPU's and they get warm. That is very good. I look forward to it. |