After a detach/reattach everything seemed to work fine. using 3 coes of PII-955

But when I put my App info file back in the directory it instantly started erroring out again.

after removing app_info file it works correctly again.

can someone please tell me what is wrong with my app_info below:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_0.62_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>62</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>ati14ati</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<cmdline>--gpu-target-frequency 60
--gpu-polling-mode 1</cmdline>
<file_ref>
<file_name>milkyway_0.62_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.40_windows_x86_64__mt.exe</name>
<executable/>
</file_info>
<file_info>
<name>libgomp_64-1.dll</name>
<executable/>
</file_info>
<file_info>
<name>pthreadGC2_64.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>40</version_num>
<plan_class>mt</plan_class>
<cmdline>--nthreads=2</cmdline>
<file_ref>
<file_name>milkyway_nbody_0.40_windows_x86_64__mt.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libgomp_64-1.dll</file_name>
</file_ref>
<file_ref>
<file_name>pthreadGC2_64.dll</file_name>
</file_ref>
</app_version>
</app_info>

I am looking at two servers that will not calculate an n-body correctly at all.
I have reset the project on each (twice), and currently am running with no XML file for these.

They all error out immediately with an exit status 128

I have tried the several versions on the XML file presented here, but to no avail.

The version I am using is the one automatically downloaded on the resets, for a 64-bit XP server --
milkyway_nbody_0.40_windows_x86_64__mt

and the two associated dlls are thee as well.

I'm running Ubuntu 10.10 and am also having a problem with every type of WU now. Based on one of the postings, I just did a detach through BoincStats, shut down BOINC Manager, and then did a "service boinc-client restart" and then a re-attach through BoincStats. No app_info.xml.

I see where the n-body Wu is using all 6 CPU's! and finished it off in about 4 minutes. Can that possibly be right?!

I'm going to check the WU record but I'm not confident that it's going to be a good WU.

Regards,
Steve

I'm amazed. That n-Body WU just got posted and has already been validated!! Hopefully, the whole detach/re-attach process will help with the cuda .54 units that started going bad as well.

Regards,
Steve

all my n-body problems are failing on my new box.

2 n-body WUs errored out within a few seconds. Also getting a Windows error message that the program has stopped working.

---

I am getting a maximum time exceeded error on my N-body work units after running for 3 seconds. I will try resetting the project to see if that will help. Some have suggested that using an app_info.xml is causing this, but I have not ever worked with any app_info.xml file.

Well, Unfortunately, all MW WU's are now failing again on all machines. No app_info.xml. Running Ubuntu.

Regards,
Steve

I am getting a maximum time exceeded error on my N-body work units after running for 3 seconds. I will try resetting the project to see if that will help. Some have suggested that using an app_info.xml is causing this, but I have not ever worked with any app_info.xml file.

Oops! I accidentally forgot to do the reset when I allowed more tasks in.

Got one task (de_nbody_orphan_test_2model4), it starts out with a run time estimate of 605 hours and quickly drops. Looks like the estimate could be lowered a bit.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

It ran for two hours, finished & validated. I got 0 credits for it. Why no credits?

Task 50938244
Name de_nbody_orphan_test_2model_4_165552_1308226719_0
Workunit 35249745
Created 16 Jun 2011 | 12:18:44 UTC
Sent 16 Jun 2011 | 12:35:22 UTC
Received 16 Jun 2011 | 14:54:31 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 1500
Report deadline 28 Jun 2011 | 12:35:22 UTC
Run time 0.00
CPU time 7,563.48
Validate state Valid
Credit 0.00
Application version MilkyWay@Home N-Body Simulation v0.40 (mt)


Stderr output
<core_client_version>5.10.45</core_client_version>
<![CDATA[
<stderr_txt>
<search_application>milkywayathome nbody 0.40 Windows x86 double OpenMP Crlibm</search_application>
10:51:50: Making final checkpoint
10:51:50: Simulation complete
<search_likelihood>-405.597183455446</search_likelihood>
10:51:50 (3140): called boinc_finish

</stderr_txt>
]]>

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.