<core_client_version>5.10.28</core_client_version>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>/stars-79.txt</file_name>
  <error_code>-119</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>

Probably a WU configuration problem, the filename starts with a slash

<core_client_version>5.10.28</core_client_version>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>/stars-79.txt</file_name>
  <error_code>-119</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>

Probably a WU configuration problem, the filename starts with a slash

All the sticky datafiles start with a slash recently, not had a prob with Linux or XP with that.

[edit] Hmm, mind you I'm using BOINC 6x [/edit]

The second boxes that received those WUs didn't have problems. Maybe my BOINC just had a timeout, the MW web site is quite sluggish. Several downloads did work, but several in a row failed, that's why I assumed it might be the configuration for a certain set of results.

<core_client_version>5.10.28</core_client_version>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>/stars-79.txt</file_name>
  <error_code>-119</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>

Probably a WU configuration problem, the filename starts with a slash

All the sticky datafiles start with a slash recently, not had a prob with Linux or XP with that.

[edit] Hmm, mind you I'm using BOINC 6x [/edit]

I'm seeing a sudden surge of these today:

2/11/2009 11:48:24 AM|Milkyway@home|[error] MD5 check failed for /stars-79.txt
2/11/2009 11:48:24 AM|Milkyway@home|[error] expected c0053b930967ae032adc2b8f23015a93, got 61a14313a3f0244e7f7be2df1645d5d8
2/11/2009 11:48:24 AM|Milkyway@home|[error] Checksum or signature error for /stars-79.txt

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>stars-79.txt</file_name>
<error_code>-200</error_code>
</file_xfer_error>

</message>
]]>


<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>stars-82-v2.txt</file_name>
<error_code>-200</error_code>
</file_xfer_error>

</message>
]]>

but only on my vista 64. when these all err out, the scheduler resets to 24 hours before reconnect.

<core_client_version>5.10.28</core_client_version>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>/stars-79.txt</file_name>
  <error_code>-119</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>

Probably a WU configuration problem, the filename starts with a slash

All the sticky datafiles start with a slash recently, not had a prob with Linux or XP with that.

[edit] Hmm, mind you I'm using BOINC 6x [/edit]

I'm seeing a sudden surge of these today:

2/11/2009 11:48:24 AM|Milkyway@home|[error] MD5 check failed for /stars-79.txt
2/11/2009 11:48:24 AM|Milkyway@home|[error] expected c0053b930967ae032adc2b8f23015a93, got 61a14313a3f0244e7f7be2df1645d5d8
2/11/2009 11:48:24 AM|Milkyway@home|[error] Checksum or signature error for /stars-79.txt

6.4.5

WU download error: couldn't get input files:

stars-79.txt
-200



]]>


6.4.5

WU download error: couldn't get input files:

stars-82-v2.txt
-200



]]>

but only on my vista 64. when these all err out, the scheduler resets to 24 hours before reconnect.

What might have happened is that you didn't complete downloading one of the star files. You could try deleting it and making boinc re-download it. I think a project reset should do that.

---

What might have happened is that you didn't complete downloading one of the star files. You could try deleting it and making boinc re-download it. I think a project reset should do that.

I did a reset and have processed 100 wu's without errors now, and everything looks like it's downloading correctly.

thanks, Travis.

What might have happened is that you didn't complete downloading one of the star files. You could try deleting it and making boinc re-download it. I think a project reset should do that.

I did a reset and have processed 100 wu's without errors now, and everything looks like it's downloading correctly.

thanks, Travis.

it happened again about 8 hours later. all the wu's erred and boinc rescheduled for 24 hours later, so it didn't update.

this time i completely detached and rejoined. i'll let you know how that goes.

it happened again about 8 hours later. all the wu's erred and boinc rescheduled for 24 hours later, so it didn't update.

The same here when I was at work... 6 hours of power bill wasted without work...

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

th detach didn't work either. it all locked up about 3 hours later. but once i did an update after getting home, everything starts working again. Could it be we're exhausting the star files on our pc's and it doesn't know to go out and get new star files?

Looks like there are two error types, including those discussed in this thread

An example of the MD5 checksum error is here from BOINC messages tab -


12/02/2009 23:44:35|Milkyway@home|[error] MD5 check failed for /stars-79.txt
12/02/2009 23:44:35|Milkyway@home|[error] expected c0053b930967ae032adc2b8f23015a93, got 61a14313a3f0244e7f7be2df1645d5d8
12/02/2009 23:44:35|Milkyway@home|[error] Checksum or signature error for /stars-79.txt

This is much less, as an error, than the ones discussed in the other thrad.

Looks like there are two error types, including those discussed in this thread

An example of the MD5 checksum error is here from BOINC messages tab -


12/02/2009 23:44:35|Milkyway@home|[error] MD5 check failed for /stars-79.txt
12/02/2009 23:44:35|Milkyway@home|[error] expected c0053b930967ae032adc2b8f23015a93, got 61a14313a3f0244e7f7be2df1645d5d8
12/02/2009 23:44:35|Milkyway@home|[error] Checksum or signature error for /stars-79.txt

This is much less, as an error, than the ones discussed in the other thrad.

i've looked through that thread earlier. and i'm starting to see the compute errors too. after i submit an update i'm seeing these errors now:

2/12/2009 8:29:27 PM|Milkyway@home|[error] garbage_collect(); still have active task for acked result nm_s82_r9_755819_1234487764_0; state 9
2/12/2009 8:29:27 PM|Milkyway@home|[error] garbage_collect(); still have active task for acked result nm_s82_r9_755820_1234487764_0; state 9
2/12/2009 8:29:27 PM|Milkyway@home|[error] garbage_collect(); still have active task for acked result nm_s82_r9_755826_1234487764_0; state 9
2/12/2009 8:29:27 PM|Milkyway@home|[error] garbage_collect(); still have active task for acked result nm_s82_r9_755802_1234487763_0; state 9

Got this just now for 82_r5's:

2/13/2009 6:23:45 PM|Milkyway@home|[error] MD5 check failed for /stars-82-v2.txt
2/13/2009 6:23:45 PM|Milkyway@home|[error] expected 49c31e6d724772838c734817b7ac113e, got 798817981b84182b99faf9c1cb6fe75e
2/13/2009 6:23:45 PM|Milkyway@home|[error] Checksum or signature error for /stars-82-v2.txt

for these units:
2/13/2009 6:23:40 PM|Milkyway@home|Started download of nm_s82_r5_search_parameters_104308_1234308080
2/13/2009 6:23:41 PM|Milkyway@home|Started download of nm_s82_r5_search_parameters_104312_1234308080
2/13/2009 6:23:45 PM|Milkyway@home|Started download of nm_s82_r5_search_parameters_104315_1234308080
2/13/2009 6:23:47 PM|Milkyway@home|Started download of nm_s82_r5_search_parameters_104317_1234308080

---

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