I'm running Ubuntu. I don't know if that's relevant. The result messages for my completed tasks for my 686 are showing nothing but XML error messages. As an example, here is the message for one of my completed tasks followed by the message from the other computer running the same task.

stderr out

<core_client_version>6.2.12</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233870215.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233870215.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
ar=0.008848 NumCfft=73003 NumGauss= 0 NumPulse= 200229972552 NumTriplet= 14377034989568
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233870215.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233870215.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
ar=0.008848 NumCfft=73003 NumGauss= 0 NumPulse= 200229972552 NumTriplet= 14377034989568

</stderr_txt>
]]>



stderr out

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233006214.000000
Skipping: /computation_deadline
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1233006214.000000
Skipping: /computation_deadline
Windows optimized S@H Enhanced application by Alex Kan
Version info: SSE4.1 (Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSE4.1 Win64 Build 42 , Ported by : Jason G, Raistmer, JDWhale

CPUID: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz
Speed: 4 x 2999 MHz
Cache: L1=64K L2=3072K
Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1

Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 0.008848

Flopcounter: 19390760628550.227000

Spike count: 1
Pulse count: 1
Triplet count: 1
Gaussian count: 0
called boinc_finish

</stderr_txt>
]]>


This is for SETI@home. I have a similar message for milkyway@home:

stderr out

<core_client_version>6.2.12</core_client_version>
<![CDATA[
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1232257618.136000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct

</stderr_txt>
]]>


Am I returning unusable information that is somehow marked valid? Perhaps the information is valid but just the log of it is in error? Is there something in a config file I should be fixing or checking?

There's is nothing wrong with your setup. All that those messages relay is that the science application was not built against the BOINC 6 API, so it comes across options it never heard about.

It won't interfere in the running of tasks. Ask the project when they plan to update their applications.

---