Linux is not my primary platform, but a quick look, on request, at:

15-Mar-2009 02:23:27 [SETI@home] [error] No app version for result: i686-pc-linux-gnu 0

I notice the '0' is weird.

it is possible that the app_info entry for 64 bit linux, running 32 bit boinc may need a platform line in the app_info entry such as:

<platform>i686-pc-linux-gnu</platform>
underneath the <version_num> line, or 64 bit equivalent (whatever that is).

Maybe 32 bit Boinc has detected 64 bit platform? cc_config.xml might then also need an <alt_platform> specified when mixing bitness of OS and Boinc.

Those things wouldn't salvage any work in progress that was marked with the non-existant platform+app_version, but might ensure any new work was marked with the correct version.

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Well, lets start with the easiest thing to change, which is "updating" boinc to the 64bit platform

25-Mar-2009 20:55:35 [---] Platform changed from i686-pc-linux-gnu to x86_64-pc-linux-gnu

The rest of jason_gee's suggestions are a bit over my comprehension. Won't know if it makes any difference until they start sending out work again.

---

I returned to your app_info.xml file and am wondering about something.

<name>astropulse-5.0.i686-pc-linux-gnu</name>
<file_name>astropulse-5.0.i686-pc-linux-gnu</file_name>

<name>astropulse-5.03.x86_64-pc-linux-gnu</name>
<file_name>astropulse-5.03.x86_64-pc-linux-gnu</file_name>

When you check the binary names in the Setiathome.berkeley.edu subdirectory, do they have dashes or underscores? Usually in BOINC-land one uses underscores in the application names, but I am not sure if this is used in Linux as well.

So can you check if the binary is actually called astropulse-5.0.i686-pc-linux-gnu and not astropulse_5.0.i686_pc_linux_gnu ??

---

The default app is named astropulse_5.00_i686-pc-linux-gnu, so cruncher left the name the same.

---

The three binaries that were in place in
/home/boinc/projects/setiathome.berkeley.edu/

AK_V8_linux64_ssse3
astropulse-5.03.x86_64-pc-linux-gnu
astropulse-5.0.i686-pc-linux-gnu

The file names matched the contents of app_info.xml

and now, I have just this one

astropulse-5.03.x86_64-pc-linux-gnu

I have not changed the file names

---

Just an update. There have been no errors since "upgrading" BOINC from i686-pc-linux-gnu to x86_64-pc-linux-gnu.

I am managing one core2 machine and eight quad core machines. If the problem stays away, I will attempt to bring back the "transitional" app_info.xml for combined MB, astropulse v5.0 and astropulse5.03 to see if the problem returns.

---