Just a quick note to report that it appears that Milkyway WUs don't appear to appreciate being suspended....

Earlier this evening BOINC on my host suspended WU #1883917 in order to run it's weekly benchmarks, said WU immediately errored out.

Here's the appropriate extract from BOINC's log:

04/01/2008 18:46:03||Running CPU benchmarks
04/01/2008 18:46:03||Suspending computation - running CPU benchmarks
04/01/2008 18:46:13|Milkyway@home|Deferring communication for 1 min 0 sec
04/01/2008 18:46:13|Milkyway@home|Reason: Unrecoverable error for result gs_90_1199516100_135551_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003))
04/01/2008 18:46:13|Milkyway@home|Computation for task gs_90_1199516100_135551_0 finished
04/01/2008 18:46:13|Milkyway@home|Output file gs_90_1199516100_135551_0_0 for task gs_90_1199516100_135551_0 absent

Not a big problem for me, but I just thought you should know.


TTFN - Pete.

---

Just a quick note to report that it appears that Milkyway WUs don't appear to appreciate being suspended....

Some still crash when BOINC is snoozed and one is actively running

---

me@rescam.org

Just a quick note to report that it appears that Milkyway WUs don't appear to appreciate being suspended....

Some still crash when BOINC is snoozed and one is actively running

Yeah we've seen this a bit, still trying to figure out why.

I had this and boinc wasn't snoozing:

17/01/2008 08:11:08|World Community Grid|Restarting task ll784_00023_5 using hpf2 version 518
17/01/2008 09:25:10|Einstein@Home|Restarting task h1_0723.55_S5R2__159_S5R3a_0 using einstein_S5R3 version 415
17/01/2008 10:25:19|Milkyway@home|Starting gs_111_1200553934_69987_0
17/01/2008 10:25:19|Milkyway@home|Starting task gs_111_1200553934_69987_0 using astronomy version 113
17/01/2008 11:09:43|Milkyway@home|Computation for task gs_111_1200553934_69987_0 finished
17/01/2008 11:09:43|Milkyway@home|Output file gs_111_1200553934_69987_0_0 for task gs_111_1200553934_69987_0 absent
17/01/2008 11:09:43|sudoku|Restarting task B0728324062_12__alpha9_1 using sudoku version 539
17/01/2008 11:09:54|Milkyway@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
17/01/2008 11:10:00|Milkyway@home|Scheduler request succeeded: got 0 new tasks

BOINC was started at 08:10:59

Result output:

<![CDATA[
<message>
One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003)
</message>

I had the dreaded windows pop up tonight. The MS error report was:

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="astronomy_1.13_windows_intelx86.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="astronomy_1.13_windows_intelx86.exe" SIZE="1007616" CHECKSUM="0xA668A8A" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFBD5A" LINKER_VERSION="0x0" LINK_DATE="12/13/2007 00:45:16" UPTO_LINK_DATE="12/13/2007 00:45:16" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="984576" CHECKSUM="0xF0B331F6" BIN_FILE_VERSION="5.1.2600.3119" BIN_PRODUCT_VERSION="5.1.2600.3119" PRODUCT_VERSION="5.1.2600.3119" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.3119 (xpsp_sp2_gdr.070416-1301)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF9293" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.3119" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3119" LINK_DATE="04/16/2007 15:52:53" UPTO_LINK_DATE="04/16/2007 15:52:53" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

Best of luck with your search, Dave.

Another couple of oddities to report.

Firstly, WU #2755228 ended with a "Compute Error" on my host, though the next cruncher completed it without issue.

Secondly, WU #1545214 is causing problems for every host it's been assigned to. For most of us it's showing as a "No reply".

I notice it's name has a corrupted character in it, which might have something to do with it.


TTFN - Pete.

---

I have had a few of those that error for everybody. They really do need to be pulled out.

I have had a few of those that error for everybody. They really do need to be pulled out.

i'll try and remove them from the database - hopefully that wont cause other problems.