I have also an error on this béta-test.

Journal des résultats

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>BETA_CMD2_0001-1RKC_B.clustersOccur-2GYT_A.clustersOccur_0_0_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>BETA_CMD2_0001-1RKC_B.clustersOccur-2GYT_A.clustersOccur_0_0_1</file_name>
<error_code>-131</error_code>
</file_xfer_error>

</message>
]]>

I've got one beta unit that errored out with 131, and a 2nd still running. This 2nd one is interesting, because it seems one of my wingmen has errorred on a 131, while another landed successfully to Pending Validation.

BETA_ CMD2_ 0001-PP1BA.clustersOccur-TPM1A.clustersOccur_ 0_ 3-- In Progress 17-4-09 02:58:46 18-4-09 02:44:22 0.00 0.0 / 0.0
BETA_ CMD2_ 0001-PP1BA.clustersOccur-TPM1A.clustersOccur_ 0_ 2-- Pending Validation 15-4-09 16:04:21 16-4-09 18:07:42 9.40 157.8 / 0.0
BETA_ CMD2_ 0001-PP1BA.clustersOccur-TPM1A.clustersOccur_ 0_ 1-- In Progress 15-4-09 16:04:03 18-4-09 16:04:03 0.00 0.0 / 0.0
BETA_ CMD2_ 0001-PP1BA.clustersOccur-TPM1A.clustersOccur_ 0_ 0-- Error 15-4-09 16:03:59 17-4-09 02:58:37 17.59 110.0 / 0.0

I'll keep it running to see what happens for me.

Question on the side: Is the time spend on these workunits that error out counted towards our beta badges, or are they completely lost? Reason I ask is I don't mind loosing the points (that's the risk of joining in the Beta program, which is optional) but it would be nice to get a Beta badge some day (which is hard enough for a small cruncher like me)

I fully support this statement. Also an errored WU is valuable for the development and improvement of projects. So it would be fair to count errored units.

Pardon me but if you cannot find the cause of this problem and fix it I wonder if it is worth at all to send a new beta round: Unless you tell us I can hardly imagine what you can learn from a job which produces so huge result files when you are only getting the same small terse Result Log for everybody. It does not even contain the file sizes and limits that we see in the message log.

I have finally got one repair beta this morning with the same outcome after 7+ hours of runtime:

Computation for task BETA_CMD2_0001-1RKC_A.clustersOccur-1RKC_B.clustersOccur_0_5 finished
Output file BETA_CMD2_0001-1RKC_A.clustersOccur-1RKC_B.clustersOccur_0_5_0 for task BETA_CMD2_0001-1RKC_A.clustersOccur-1RKC_B.clustersOccur_0_5 exceeds size limit.
File size: 98723225.000000 bytes. Limit: 13902608.000000 bytes
Output file BETA_CMD2_0001-1RKC_A.clustersOccur-1RKC_B.clustersOccur_0_5_1 for task BETA_CMD2_0001-1RKC_A.clustersOccur-1RKC_B.clustersOccur_0_5 exceeds size limit.
File size: 6854625.000000 bytes. Limit: 5000000.000000 bytes

If it can help you, my "Write to disk" limit is currently set at 60 seconds.

Please enlighten us. Jean.

@Uplinger/knreed,

With 2 beta's parallel it's hard to tell from the project page if the validation has run, but I've still got 2 with quorum complete, now also init distro complete, all 3 copies showing Pending Validation, one since the 15th. A flag needing flack?

BETA_ CMD2_ 0001-1RKC_ A.clustersOccur-2O72_ A.clustersOccur_ 0_ 2-- Pending Validation 4/15/09 15:24:21 4/15/09 18:40:57 2.94 30.9 / 0.0
BETA_ CMD2_ 0001-1RKC_ A.clustersOccur-2O72_ A.clustersOccur_ 0_ 0-- Pending Validation 4/15/09 15:24:16 4/15/09 23:43:33 2.08 31.3 / 0.0
BETA_ CMD2_ 0001-1RKC_ A.clustersOccur-2O72_ A.clustersOccur_ 0_ 1-- Pending Validation 4/15/09 15:23:57 4/15/09 23:27:57 2.35 31.8 / 0.0